Project Scope Document:
Key Performance Indicators (KPIs): This indicator helps you determine whether the project is on track and progressing as planned.
Scope boundaries:
- Stability of the Scope: An indication of how stable a project is by monitoring the project charter, requirements, and the scope statement.
- Impact of Scope Changes: Adding to the scope may impact the budget.
- Scope Change Process: Documented process for scope changes to keep project organized when changes occur.
- A change request form.
- An analysis of the impact of the request on the scope, budget, schedule, and quality of the project.
- An approval process to accept or reject requests.
- A communication plan to keep stakeholders informed of the status of requests.
- A method to incorporate approved changes into the project plan.
Constraints: Anything that restricts or dictates the action of the project team. The scope may become a constraint that drives changes to time, cost, or quality. Thus, if you have a fixed budget money will be the constraint and if time and money are constraints then quality may suffer.
Assumptions: An action, condition, or event that is believed to be true. Assumptions must be documented and validated.
Detailed Objectives: Describe the overall goal the project hopes to achieve. Objectives should be measurable, verifiable, and often time-bound.
Final Project Acceptance Criteria: Information used to describe how you will determine that the deliverables are complete and that they meet the expectations.
Validate Scope Statement: Keep your team informed so that stakeholders are aware of any changes made to the project so that they can discuss the impact it would have on the project.
Work Breakdown Structure:
Benefits of WBS:
- It is a tool for team building and team communication.
- It allows team members to see the big picture and understand how their part of the project fits in.
- It prevents critical work from being overlooked and help control change.
- It is useful when discussing staffing requirements or budgets.
- It is an excellent tool for communicating with customers and stakeholders.
- It is good for coordinating work efforts and adhering to the project scope.
Levels of WBS:
- The highest level is the project name.
- The next level include: major deliverables, project phases, or subprojects.
- The lowest level is the work package.
- (Levels in a WBS may vary depending on the project.)
Purpose of WBS:
- To make certain that each deliverable is identified and that each sub-deliverable is decomposed from there.
Planning processes:
- Recruit knowledgeable resources.
- Work through two items before proceeding to the next level.
- Each item in a lower level is a component of the level above.
- Define the work package level.
- Do not create a to-do list.
- Use appropriate number of levels.
WBS Dictionary:
- It describes each of the deliverables and their components and includes a code of accounts identifier, estimates, resources, criteria for acceptance, and other information that helps explain the deliverables.
TestMoz:
Click here to take a test on this chapter.