Identify desired functionality
From the system requirements specification and/or the use case model, functionality is selected for inclusion in the system
design. |
Identify key risks
Risks are a source of danger to the project. Risk mitigation activities are work activities that have the express purpose
of mitigating identified risks. The risk mitigation activities must be identified and scheduled. |
Plan the set of prototypes
For each prototype, identify its mission and use estimation techniques to determine the calendar time and effort. The
delivery of each prototype forms a primary project milestone. |
Construct detailed prototype plans
For each prototype, specify the work activities and efforts required:
-
Estimate the effort for each sub-phase in the microcycle
-
For hard date or fixed duration tasks, use that data
-
Identify risks to task completion
-
Define first cut staffing
|
Evaluate schedule
Schedules can be evaluated by using alternative estimation schemes, such as COCOMO or Use Case Points. You can also compare
the schedule to schedules for previously completed projects of similar scope. |
Rework schedule until it is acceptable
Schedules are an optimization of time, effort, and manpower. At most, two of these can be specified and the third
computed from the others. Schedules can be adjusted by the following actions:
-
adding or removing functionality
-
changing the order of the delivery of functionality
-
making buy vs. build decisions
-
adding or subtracting personnel resources
-
outsourcing or subcontracting functionality
Note that arbitrarily changing the estimates without changing the actual work activity is not in the list.
|
|