Page 50 -

2 - PROJECT LIFE CYCLE AND ORGANIZATION

Table 2-3 provides two examples of the relationship between the cadence of project iterations and the cadence
of product increments. Both examples include daily cadence of iterations but different cadences for producing
product increments. Other possibilities exist; for example, the team might produce working increments of software
for internal review and demonstration on weekly integration and test cycles. There are many possibilities for
the relationship between project iterations and product increments when using adaptive software development
methods.

The examples of adaptive software development depicted in Figures 2-5, 2-6, and 2-7 also illustrate a common
attribute of adaptive software development: the customer determines the features to be included and therefore
determines, from the business viewpoint, value-added expenditure (or not) of additional development time, money,
effort, and resources. For the examples in Figures 2-5 and 2-6, the customer can make the determination to
continue (or not) when reviewing deliverable product increments at intervals of 1, 2, or 4 weeks. In Figure 2-7, the
customer can make the determination to continue (or not) on a daily, or perhaps weekly basis.

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