Activity: Plan by Feature
An initial project-wide activity to produce the development plan. At the end of this process, we should be ready to launch into the construction phase of the project represented by iteration of process 4 and 5.
Extends: Plan by Feature
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Relationships
Parent Activities
Description

An initial project-wide activity to produce the development plan.

The project manager, development manager and the chief programmers plan the order that the features are to be implemented, based on feature dependencies, load across the development team and also on the complexity of the features to be implemented. The main tasks in this process are not a strict sequence. Like many planning activities they are considered together, with refinements made from one or more tasks and then considering the others again. A typical scenario is to consider the development sequence, then consider the assignment of business activities to chief programmers and in doing so, consider which of the key classes (only) are assigned to which developers (remember a chief programmer is also a developer). When this balance is achieved and the development sequence and assignment of business activities to chief programmers is essentially completed, then the class ownership is completed (beyond the key classes thatwere already considered for ownership).

Properties
Event-Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable
Key Considerations

Entry Criteria:

  •  The Build a Features List process has completed.

Exit Criteria:

The result of the process is the development plan consisting of

  • Business activities with completion dates (month and year)
  • Chief programmers assigned to business activities
  • Subject areas with completion dates (month and year) derived from the last completion date of their respective business activities
  • The list of classes and the developers that own them (the class owner list)