Lesson 6

Project Scope Management

6 Main Processes

1. Plan scope management
2. Collect requirements
3. Define scope
4. Create WBS
5. Verify/ validate Scope
6. Control Scope

Collect and Document Requirements

1. Interviewing stake-holders 1-on-1
2. holding focus groups
3. questionaires and surveys
4. observation
5. prototyping
6. benchmarking

• review project charter
• review stakeholder register

Define Scope

1. expert judgement
2. product analysis
3. alternatives identification
4. decision-making skills

Tips

1. be very specific
2. document should be good length
3. identify all risk or uncertainities
4. create a draft

Well composed project scope statement

1. Justification
2. product description
3. acceptance criteria
4. deliverable
5. exclusions
6. constraints
7. assumptions
8. cost estimates

scope creep (happen) = additional features, functions, requirements are added beyone agreement scope with no consideration to impacts on time, cost and resources to stakeholders/customers approval

Reasons for Scope creep

1. Unclear scope definition
2. poor management of scope and requirements
3. not following the change management
4. inconsistent collection of project requirements
5. lack of sponsorship or stakeholder involved
6. longer duration of a project