This is 5+6 videos of the series:
- Project Scope Management.
- Project Time Management.
Project Scope Management
It’s probably is the most important one of all Areas of Knowledge, because Scope defines the Base against which the other Areas are delivered.
It defines what it’s the project is going to accomplish and then the other Areas of Knowledge >>> defines time to deliver, budget, HR…
- Collect Requirements: what it’s that the business want, starts from Charter and evolve to give us better more complete of the requirements. i.e The Scope.
- Defines Scope: what it’s, is not delivered.
- Create WBS (the definition of Deliverables).
- Verify the Scope (ensuring the acceptance of the scope).
- Control Scope (to ensure all requirement required to complete the project is accomplished).
With Project Charter we begin to collect requirements.
Project Charter >>evolve>> elaborate to have a solid requirements >> solid Scope >> solid Project.
How we collect Requirements?
- Interviews with key business users, workshops, brainstorming sessions…
- All what it take to understand what the business needs.
- It should be at a level appropriate to Planning, no more nor less.
- Then we create Requirements Document.
- Base lined it and get it Approved from all sponsors.
- Requirements tractability Matrix (RTM) that allow us to map/trace those high level requirements to details.
- Identify and define in planning our acceptance and criteria.
Similar to defining requirements, the scope is based on requirements.
- Clear, concise, unambiguous yet flexible.
- Identifies Deliverables.
- Expands on Acceptance Criteria.
- What is not in the Scope.
- Assumptions and Constraints.
- Expanding Deliverables into work packages, take High Level deliverables and break them down into work package.
- Decomposition = the activity of expanding deliverables into work packages.
- WBS dictionary: defines of WBS components and definition of what the component is.
- WBS = Deliverables oriented Hierarchical decomposition of the work.
- Rolling Wave Planning: decompose some deliverbale into our first wave of planning… (Phase Gate again).
- Ensuring Acceptance of Deliverables (does the blue print we present satisfy the expectations?).
- Ensuring that the right work is done and we will get final acceptance (signature).
- Inspection of Results.
- Not Quality Control.
- Ensure no unauthorized work take place (only the scope is done).
- Expecting that Change Happens (Integrated Change Management). (Change Request>Approved>WBS>Authorized Work).
- Variance Analysis of work completed.
Project Time Management
Picks off where Scope Management left.
Takes WBS>further decomposition>Activities.
- Define Activities: completed on the Project.
- Sequence the Activities.
- Identify/Estimate Activity Resources.
- Estimate Activity Duration.
- Develop Schedule.
- Control Schedule.
- A further decompose of Scope WBS into Actual individual activities to be worked on in the project.
- We decompose them to the point where it is Estimable.
- Assigned to Resource.
- Identify Milestone, key points in the project that we should report status to our stakeholders.
- Sometimes milestones = Deliverables.
- Rolling Wave Planning.
Scope WBC > Produce Current Situation review.
Activity Decomposition > we further decompose that down to activities.
- Identifies Predecessor/Successor (Logical relationship between activities).
Types of Sequence:
- Finish to Start.
- Finish to Finish.
- Start to Start.
- Start to Finish.
leads ad legs.
Different types of dependency. Mandatory vs Discretionary vs External.
Identify/Estimate Activity Resources
- Types and Quality of people/material/equipment required to complete the activities.
- Resources Availability (differ due to organization structure).
Estimate Activity Duration
How long it will take to do the activity, in terms of:
- Elapsed time (5 days).
- Actual work effort (35 hours).
- Availability: 8 hours + 50% availability >> 16 hours needed.
- Analogous Estimate.
- PERT (best guess): E = (optimistic + 4 Likely + Pessimistic)/6
- Resources leveling maximizing the utilization of our project.
- Network Analysis.
- Critical Path: identify which tasks determine the end date.
- Use Software, not by hand.
We control through many processes:
- Track Actuals: talk to teams and get the actuals from them
- Reforcast ETC (how much left).
- Reschedule (in Software).
- Variance Analysis (on/ahead/behind schedule).
- Take corrective actions to the critical path tasks.