6.1.1 Inputs to Activity Definition
.1 Work breakdown structure. The work breakdown structure is the primary input to
activity definition (see Section 5.3.3.1 for a more detailed discussion of the WBS).
.2 Scope statement. The project justification and the project objectives contained in
the scope statement must be considered explicitly during activity definition (see Sec-
tion 5.2.3.1 for a more detailed discussion of the scope statement).
.3 Historical information. Historical information (what activities were actually required
on previous, similar projects) should be considered in defining project activities.
.4 Constraints. Constraints are factors that will limit the project management team’s
options.
.5 Assumptions. Assumptions are factors that, for planning purposes, will be consid-
ered to be true, real, or certain. Assumptions generally involve a degree of risk and
will normally be an output of risk identification (described in Section 11.1).
6.1.2 Tools and Techniques for Activity Definition
.1 Decomposition. Decomposition involves subdividing project elements into smaller,
more manageable components in order to provide better management control. De-
composition is described in more detail in Section 5.3.2.2. The major difference be-
tween decomposition here and in Scope Definition is that the final outputs here are
described as activities (action steps) rather than as deliverables (tangible items). In
some application areas, the WBS and the activity list are developed concurrently.
.2 Templates. An activity list (described in Section 6.1.3.1), or a portion of an activity
list from a previous project, is often usable as a template for a new project. In addi-
tion, the activity list for a WBS element from the current project may be usable as a
template for other, similar WBS elements.
6.1.3 Outputs from Activity Definition
.1 Activity list. The activity list must include all activities which will be performed on the
project. It should be organized as an extension to the WBS to help ensure that it is com-
plete and that it does not include any activities which are not required as part of the pro-
ject scope. As with the WBS, the activity list should include descriptions of each activity
to ensure that the project team members will understand how the work is to be done.
.2 Supporting detail. Supporting detail for the activity list should be documented and
organized as needed to facilitate its use by other project management processes. Sup-
porting detail should always include documentation of all identified assumptions and
constraints. The amount of additional detail varies by application area