These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and toolsIndividuals and interactions over processes and tools Working software over comprehensive documentationWorking software over comprehensive documentation Customer collaboration over contract negotiationCustomer collaboration over contract negotiation Responding to change over following a planResponding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” - Kent Beck et al, 2001

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Why “Agility”? In the modern economy, it is often difficult or impossible to predict how computer-based system (e.g., a web-based application) will evolve as time passes In the modern economy, it is often difficult or impossible to predict how computer-based system (e.g., a web-based application) will evolve as time passes Market conditions change rapidly Market conditions change rapidly End-user needs evolve End-user needs evolve New competitive threats emerge without warning New competitive threats emerge without warning In many situations, we no longer are able to define requirements fully before the project begins. Software engineers must be agile enough to respond to a fluid business environment In many situations, we no longer are able to define requirements fully before the project begins. Software engineers must be agile enough to respond to a fluid business environment

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, What is “Agility”? Effective (rapid and adaptive) response to change Effective (rapid and adaptive) response to change Effective communication among all stakeholders Effective communication among all stakeholders Drawing the customer onto the team Drawing the customer onto the team Organizing a team so that it is in control of the work performed Organizing a team so that it is in control of the work performed Yielding … Rapid, incremental delivery of software Rapid, incremental delivery of software

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, An Agile Process Is driven by customer descriptions of what is required (scenarios) Is driven by customer descriptions of what is required (scenarios) Recognizes that plans are short-lived Recognizes that plans are short-lived Develops software iteratively with a heavy emphasis on construction activities Develops software iteratively with a heavy emphasis on construction activities Delivers multiple ‘software increments’ Delivers multiple ‘software increments’ Adapts as changes occur Adapts as changes occur

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Extreme Programming (XP) The most widely used agile process, originally proposed by Kent Beck The most widely used agile process, originally proposed by Kent Beck XP Planning XP Planning Begins with the creation of “user stories” Begins with the creation of “user stories” Agile team assesses each story and assigns a cost Agile team assesses each story and assigns a cost Stories are grouped to for a deliverable increment Stories are grouped to for a deliverable increment A commitment is made on delivery date A commitment is made on delivery date After the first increment “project velocity” is used to help define subsequent delivery dates for other increments After the first increment “project velocity” is used to help define subsequent delivery dates for other increments

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Extreme Programming (XP) XP Design XP Design Follows the KIS (Keep It Simple) principle Follows the KIS (Keep It Simple) principle Encourage the use of CRC cards Encourage the use of CRC cards For difficult design problems, suggests the creation of “spike solutions”—a design prototype For difficult design problems, suggests the creation of “spike solutions”—a design prototype Encourages “refactoring”—an iterative refinement of the internal program design Encourages “refactoring”—an iterative refinement of the internal program design XP Coding XP Coding Recommends the construction of a unit test for a story before coding commences Recommends the construction of a unit test for a story before coding commences Encourages “pair programming” Encourages “pair programming”

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Extreme Programming (XP) XP Testing XP Testing All unit tests are executed daily All unit tests are executed daily “Acceptance tests” are defined by the customer and executed to assess customer visible functionality “Acceptance tests” are defined by the customer and executed to assess customer visible functionality

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Extreme Programming (XP)

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Adaptive Software Development Originally proposed by Jim Highsmith Originally proposed by Jim Highsmith ASD — distinguishing features ASD — distinguishing features Mission-driven planning Mission-driven planning Component-based focus Component-based focus Uses “time-boxing” Uses “time-boxing” Explicit consideration of risks Explicit consideration of risks Emphasizes collaboration for requirements gathering Emphasizes collaboration for requirements gathering Emphasizes “learning” throughout the process Emphasizes “learning” throughout the process

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Adaptive Software Development Software increment adjustments for subsequent cycles speculation collaboration learning Adaptive cycle planning mission statement project constraints basic requirements Time-boxed release plan Requirements gathering Joint Application Development mini-specs Components implemented/tested focus groups for feedback formal technical reviews Postmortems Release

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Collaboration Effective collaboration with your customer will only occur if you jettison any “us and them” attitudes Effective collaboration with your customer will only occur if you jettison any “us and them” attitudes A matter of trust A matter of trust Criticize without animosity Criticize without animosity Assist without resentment Assist without resentment Work as hard or harder as they do Work as hard or harder as they do Have the skill set to contribute to the work at hand Have the skill set to contribute to the work at hand Communicate problems or concerns in a way that leads to effective action Communicate problems or concerns in a way that leads to effective action

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Agile philosophy The importance of self-organizing teams that have control over the work they perform Communication and collaboration between team members and between practitioners and their customers A recognition that change represents an opportunity An emphasis on rapid delivery of software that satisfies the customer