• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Sidra Agile Software Process
 

Sidra Agile Software Process

on

  • 4,015 views

Agile Software Process

Agile Software Process

Statistics

Views

Total Views
4,015
Views on SlideShare
4,000
Embed Views
15

Actions

Likes
1
Downloads
85
Comments
1

1 Embed 15

http://www.slideshare.net 15

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • :)
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Sidra Agile Software Process Sidra Agile Software Process Presentation Transcript

    • AGILE SOFTWARE PROCESSES
      SOFTWARE ENGINEERING 1
      SIDRA MATLOOB SHEIKH
      BSCS 4 B
    • INTRODUCTION
      WHAT IS AN AGILE PROCESS?
      CHARACTERIZED:
      • Difficult to predict which software requirements will persists or which change
      • For software: design and construction are interleaved. Both activities are used in tandem.
      • Analysis design, construction are not predictable.
    • INTRODUCTION
      There are many specific agile development
      methods most promote:
      • development iterations
      • team work
      • collaboration
      • process adaptability through out the life
      AGILE METHODS:
      Break tasks into small increments with minimal planning
    • ITERATION
      • Short term frames
      • worked on full software development cycle including:
      • Planning
      • Requirement
      • Analysis
      • Design
      • Coding
      • Unit Testing
      • Acceptance Test
    • ITERATION
      • At the end of each iteration customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment and ensuring alignment with customer needs and company goals
    • HISTORY
      • The modern definition of agile software evolved in mid of 1990s , perceived to be typified by a
      • Heavily regulating
      • Regimented
      • Micro managed use of the waterfall model were seen as:
      • Bureaucratic
      • Slow
      • Demeaning
      • Inconsistent
      With a ways that software developers actually perform effective work
    • HISTORY
      • “Light weight methods “
      • In 2001 ,prominent member of community of met at Snowbird ,Utah and Adopted the name “Agile Methods”
      • An adaptive software development process was introduced in a paper by Edmonds 1974
      • Early Agile methods include scrum 1995
      • The crystal year , Extreme Programming 1996
      • ASD, FDD,DSDM 1995
      These typically are referred to as Agile methodologies since Agile Manifesto was published in 2001
    • Principles Behind Agile Process
      • Agile methods are a family of development processes, not a single approach to software development
      • In 2001, 17 prominent figures in the field of agile development came together “ to discuss ways of creating software in a lighter , faster ,more people-centric way“
      • They coined the term Agile Software Development and created the Agile Manifesto, widely regarded as canonical definition of agile development & accompanying agile principles
    • Agile States Are
      • Individual & Interaction over processes and Tools .
      • Working software over comprehensive documentation
      • Customer Collaboration over contract Negotiation
      • Responding to change over a plan
    • Principle Behind Agile Manifesto are:
      • Delivery of useful software
      • Working Software is delivered frequently
      • Working is principle measure of progress
      • Close, daily cooperation between business people and developer
      • Face-to-face conversation is the best form of communication
      • Project are built around motivated individuals , who should be trusted .
      • Continuous attention to technical excellence and good design
      • Simplicity
      • Self organization team
      • Regular adaptation to changing circumstance
    • AGILE HOME GROUND
      • Low criticality
      • Senior developers
      • Requirements changes very often
      • Small number of developers
      • Culture that thrives on chaos
    • PLAN-DRIVEN HOME GROUND
      • High criticality
      • Junior developers
      • Requirement do not change
      • Large number of developers
    • AGILE METHODS
      Some of the well known agile software development
      method:
      • Agile modeling
      • Agile unified process (AUP)
      • Agile data methods
      • DSDM
      • Essential unified process (EssUP)
      • Extreme programming (XP)
      • Feature driven development (FDD)
      • Getting real
      • open unified process (OpenUPP)
      • Scrum
      • Lean software development
    • Agile Practices
      • Test driven development (TDD)
      • Behavior driven development (BDD)
      • Continuous Integration
      • Pair Programming
      • Planning Poker
    • References
      • www.wikipedia.com
      • www.stell_greene.com
      • www.sci.cmu.edu
      • www.spc.ca
    • Thanks