Multiple Release Custom Page 8 of 18 Phase 3: Planning
Collect Requirements – a process identifying how requirements will be further defined.
Identify the requirements definition methodology, tools, techniques, and documentation to be
utilized and the planned processes to ensure that requirements are defined to be complete,
concise, consistent, and unambiguous. This section should clearly demonstrate how the Planning
Team will define and validate requirements for all requirement types specified in the Functional
Requirements Document template.
Verify Scope – a process defining how various products/deliverables will be periodically
verified and formally accepted. This section of the Scope Management Plan should describe:
• Process to obtain project stakeholders’ formal acceptance of the completed project scope and
associated deliverables. This process typically involves verifying that deliverables meet
acceptance criteria.
• Processes to verify periodically the project scope. This includes reviewing deliverables to
ensure that each is completed satisfactorily.
• Processes for inspecting, measuring, and testing the contractual deliverable to verify it meets
the established acceptance criteria.
Control Scope – procedures for handling project change requests.
• Procedures to ensure all potential project scope changes are vetted properly through the
established Change Control process. With the Procurement Officer, define procurement-
related change control measures, i.e., change order processes.
4.4.6 Refine WBS, Develop the Baseline Schedule and Develop the Schedule Management
Plan.
The Project Manager, with input from the key project stakeholders and the initialWBS, refines
the WBS into further detail, develops the baseline schedule and defines the Schedule
Management Plan. The initial WBS, developed during the Concept Development Phase, will be
progressively elaborated to define specific work activities, activities sequence, estimate
resources, and estimate duration that will need to complete the project. The refined WBS will be
used to develop an initial, baseline schedule. The Schedule Management Plan establishes the
specific procedures for how the project schedule will be managed and controlled and is as
detailed as necessary to control the schedule through the life cycle based on the size, risk profile,
and complexity of the project. If the Planning Team intends to implement the project through
multiple releases, the Schedule Management Plan should address the processes to manage the
schedule through multiple iterations of design, development, integration, testing, and
implementation.
The Project Manager should consider the six schedule management processes described below in
the development of the schedule baseline and the Schedule Management Plan. The development
of the schedule baseline will involve activity definition, activity sequencing, activity resource
estimation, and activity duration estimation. The Schedule Management Plan should be focused
on the methods for controlling the schedule.
Define Activities – identification of the specific work activities that need to be performed to
complete the project. Although preliminary activity definition begins in the Concept
Development Phase, this definition is further refined during the Planning Phase to ensure that all