2. Scope Definition
• Project Scope - The work that needs to be
accomplished to deliver a product, service, or result
with the specified features and functions
• Product Scope - The features and functions that
characterize a product, service, or result
www.projektor.ee/pm/#scope
8. Project Charter*
• Project manager name
• Organization (team)
• Requirements and Business needs
• Description of the end result
• Main deliverables
• Stakeholders influence
• Business case
• Summary milestones (estimated deadline)
• Summary budget (estimated price)
• Assumptions and constrains
www.projektor.ee/pm/#scope
9. Scope Management Plan
• Process how the scope will be defined
• Process how the WBS will be created
• Process how verification will be obtained
• Process how changes will be handled
www.projektor.ee/pm/#scope
11. SMART – Method for Defining Objectives
• Specific
• Measurable
• Assignable
• Realistic
• Time-related
www.projektor.ee/pm/#scope
12. Example Objective
• Project scope is to develop 2D graphical-adventure game for
learning language. Game is in FPV, web based and story
related. Dialogues will be presented in text format.
• Game contains 3 chapters (levels). Each chapter contains 5
scenes (action points). Each scene contains 1-2 dialogues (1-
2 NPC’s).
• Fully operational game is finished in the end of 3 month
project.
• Estimated budget 20 000 EUR
www.projektor.ee/pm/#scope
16. Purpose of the WBS
• Subdivides the project into smaller manageable units –
Work Packages
• Refine the scope, duration, cost and resources
• Basis for further planning
• Basis for responsibility assignments
www.projektor.ee/pm/#scope
17. Decomposition Procedure
1. Define main deliverables
2. Is it possible to estimate cost and duration for
deliverables?
3. If yes then continue with step 5, else step 4
4. Divide deliverables into sub-deliverables. Repeat
step 2
5. Check is the decomposition logical and complete?
6. Coding
www.projektor.ee/pm/#scope
18. Decomposition Procedure
Define level N deliverables
Can you
estimate
deliverable
duration
and cost?
Integrity and logical check
NO
YES
www.projektor.ee/pm/#scope
21. Game
Rules
Resources Objects Events Connections Conditions
Story
Narrative Dialogues
Graphics
Avatar Characters Items Scenes
WBS Example
Game
Graphics
atar Characters Items Scenes UI
Sound
Music Effects Voice over
Code
Core
Main
gameplay
Menu
www.projektor.ee/pm/#scope
27. Project Phases and Processes
Initiation
Planning
Execution Control
Closing
www.projektor.ee/pm/#scope
28. Scope Verification and Control
Information
distribution
Project
execution
Procurement
management
Reporting
Team
development
Schedule
control
Scope
verification
Cost
control
Quality
control
Risk
monitoring
Change
management
Planning
Closing
www.projektor.ee/pm/#scope
29. Scope Verification
Process for obtaining stakeholder’s formal
acceptance to the project scope and
deliverables
www.projektor.ee/pm/#scope
30. Scope Control
Management of scope changes
• Avoiding scope changes
• Identifying scope changes
• Evaluating change requests
• Planning and executing changes
• Communicating changes
• Archiving
www.projektor.ee/pm/#scope
31. Inputs:
- Project scope
statement
- WBS
- Project plan
- Performance reports
- Deliverables
Methods:
- Inspection
- Scope Change
control system
- Variance analysis
- Configuration
management system
Outputs
- Deliverables
- Change requests
- Corrective actions
- Plan updates
Scope Verification and Control
www.projektor.ee/pm/#scope
32. Scope Inspection (Review)
• Measuring
• Examining
• Verifying
Does the project work and deliverables meet
acceptance criteria?
www.projektor.ee/pm/#scope
33. Scope Change Control System
Procedures how the scope can be
changed (documentation, tracking,
approval procedures)
www.projektor.ee/pm/#scope
Piirangud:
Org, struktuur
Standardid
Infrastruktuur
Ressursid
Turutingimused
Riskitundlikus
IS
A - Accepted
Testimine – kuidas kasutajad vastu võtavad?
Levitamine – mitu kasutajat?
Müük – palju raha?
Based on project phases
Project deliverables
Objectives – include measurable success criteria
Scope description – characteristics of the project, product or service (preliminary functionalities)
Requirements – client needs, standards,
Boundaries – what is excluded
Deliverables – product outputs and project documents
Criteria –
Constrains – e.g. predefined budget, deadline
Assumptions – e.g. experts with specific competences
Organization – e.g. team members, stakeholders
Risks –