Software Development: Iterative & Evolutionary
- Jan 9, 2004
- Sample Chapter is provided courtesy of Addison-Wesley Professional
- Iterative Development
- Risk-Driven and Client-Driven Iterative Planning
- Timeboxed Iterative Development
- During the Iteration, No Changes from External Stakeholders
- Evolutionary and Adaptive Development
- Evolutionary Requirements Analysis
- Early "Top Ten" High-Level Requirements and Skillful Analysis
- Evolutionary and Adaptive Planning
- Incremental Delivery
- Evolutionary Delivery
- The Most Common Mistake?
- Specific Iterative & Evolutionary Methods
- What's Next?
- Recommended Readings
- Applying UML and Patterns: Mapping Designs to Code
- Applying UML and Patterns: UML Class Diagrams
- Top Ten Organizational Impediments to Large-Scale Agile Adoption
- Scaling Lean & Agile Development: Feature Teams
- UML Interaction Diagrams
- Object-Oriented Analysis and Design
- Software Development: Iterative & Evolutionary
Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum
Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum, Adobe Reader
Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum, Adobe Reader
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd Edition
Agile and Iterative Development: A Manager's Guide
Sorry, this author hasn't posted any blogs.
This chapter is from the book
Agile and Iterative Development: A Manager's Guide
Evolutionary Delivery
Evolutionary delivery is a refinement of the practice of incremental delivery in which there is a vigorous attempt to capture feedback regarding the installed product, and use this to guide the next delivery. Naturally, the evolutionary goal is to best meet some difficult-to-predict need, such as the most frequently requested new features. Uniquely, the Evo method promotes—when possible—very short evolutionary delivery cycles of one or two weeks, so that each iteration delivers something useful to stakeholders.
To contrast "pure" incremental delivery with evolutionary delivery, in the former a plan is defined of several future deliveries—feedback is not driving the delivery plan. In evolutionary delivery, there is no plan (or at least no fixed plan) of future deliveries; each is dynamically created based on emerging information. In practice, a marriage of some future prediction and feedback is obvious and common, and the two terms are used interchangeably.
Account Sign In
View your cart