Delivery Process: Example - Scaled Agile Development with Subphases (Work Product-based)
This is an example process for a team following the Practices for Scaling Agile Development configuration of practices. This example only contains work products.
Extends: Risk-Value Lifecycle Phases
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Description

After each major milestone, the process lists the key work products and their state at that milestone.

Each iteration has three sub phases, the Plan subphase, Execute subphase and Stabilize subphase:

  • Plan subphase sets the stage for the iteration, defining goals and assigning work.
  • Execute subphase completes the work of the iteration.
  • Stabilize subphase is for review, bug-fixing, and approvals.

The key work products for each subphase are called out, as well as their state.

Note that for many work products, such as use cases, and implementation, the states at each subphase relate to the work in scope for the iteration.  The states of work products at major milestones relate to the work product as a whole.

The following is an explanation of some of the states used in this delivery process:

  • "Ready for Review" - means that the work product is complete, but needs to go through final review and approval.
  • "Approved for Iteration" - means that the work product is approved, but only for this iteration (there will be additional approvals).
  • "Stable" - means that the work product is believed to be complete and only minor updates are expected in later phases.
  • "Updated" means that this work product is expected to be updated at this time.

Work product names are often qualified by "in scope" to indicate that only the work specified for the iteration needs to be in the particular state.  Work product names are also sometimes qualified by a completion state such as "outlined" or "detailed" to indicate what aspect of the work product needs to be in a "ready for review" state.

Many work products, such as "test log" and "developer test" are expected to be done as part of bringing the other work products to their goal state.

Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
PlannedYes
Repeatable