Page 49 -

2 - PROJECT LIFE CYCLE AND ORGANIZATION

Team Hears Team Discusses
Customer Options with
Story Customer 2

Customer Daily Team Writes
Iterations Test Cases

Team Team Adds
Demonstrates Code for New
Capabilities Features, Tests,
Potential and Refactors
Product
Delivery

Figure 2-7. External Development Cycles for Adaptive Software Development

2.4.2.5 Highly Adaptive Software Development

Figure 2-7 illustrates a highly adaptive software development method that produces daily demonstrations of
working software for a knowledgeable customer who is involved on a continuing, daily basis during development of
the software product. The customer relates a user story or scenario for a desired feature of the software. Software
team members specify product requirements and write test scenarios for implementation of the desired feature or
features. The new feature(s) are added, and the test scenarios are applied.

Some distinctions between the examples illustrated in Figures 2-6 and 2-7 are indicated in Table 2-3 (internal
adaptive life cycle versus external highly adaptive life cycle).

Table 2-3. Typical Practices of Internal Adaptive and External Highly Adaptive Software Projects

Internal Adaptive Life Cycle External Highly Adaptive Life Cycle

Team members “in the loop” Customer “in the loop”
Daily team stand-up meetings and internal demos Daily demos for the customer
Team selects feature or features for the next internal Customer supplies story for the next iteration
iteration
Team accepts or revises added features Customer accepts, request revisions, or rejects added
features
Software increments available for delivery into the user Software increments available for delivery into the user
environment at predetermined intervals, if desired (1, 2, environment at daily intervals, if desired
or 4 weeks)

©2013 Project Management Institute. Software Extension to the PMBOK Guide Fifth Edition 37
®