Scope Mgmt Flashcards
Scope mgmt
Help understand requirements, define, breakdown, and control the scope of the project and verify product was completed correctly
Product scope
Everything that must be completed in order to meet product requirements
Project scope
Everything in the entire project plan
Ex: lessons learned
Scope mgmt philosophy
1) the project mgr should always be in control of the scope by thoroughly defining it and managing the processes
2) changes to the scope should be handled in a controlled and structured way
Scope mgmt goals
Define the need, set stakeholder expectations, deliver expectations, manage changes, minimize surprises so product will gain approval
Scope management processes
Initiating - none
Planning - plan scope mgmt, collect requirements, define scope, create wbs
Executing - none
Monitoring and controlling- validate scope, control scope
Closing - none
Plan scope mgmt output
Scope mgmt plan, requirements mgmt plan
Collect requirements output
Requirements documentation, requirements traceability matrix
Define scope output
Project scope statement
Create wbs output
Scope baseline
Validate scope output
Accepted deliverables
Control scope output
Scope change requests, work performance information
Plan scope mgmt
Looks at the five other processes and plans the overall approach
Schedule, budget, quality, risk factors and resource planning all tie back to it
Scope mgmt plan
Describes how scope documents will be prepared and his five remaining processes will be carried out
Requirements mgmt plan
Defines what activities the team will perform to gather and manage project requirements
Not a list of actual work requirements, just how they will be managed
Collect requirements
What is needed to satisfy stakeholders and documenting it
Product and project scope
Needs project charter and identify stakeholders complete
Collect requirements tools - data gathering
Brainstorming, interviews, focus groups, questionnaires, benchmarking
Collect requirements- decision making
Voting, multicriteria decision analysis (C&e matrix)
Affinity diagram
Takes ideas from brainstorming and organizes into logical groups
Mind mapping
Diagraming India’s into a graphical format
Collect requirements- data representation
Mind mapping, affinity diagrams
Nominal group
Ideas are brainstormed and then voted on and sorted by priority
Observation and conversation
Job shadowing
Facilitation
Workshop, get everyone together and gather req
Collect requirements- interpersonal team skills
Nominal group, observation and conversation, facilitating
Context diagram
Use case
Requirements documentation
Root business problem, source, way requirements addresses problem, business process interaction, measurements, compliance, constraints/assumptions, impact on other requirements
Requirements traceability matrix
Identifies source of requirement and can include status and owner
Define scope
Where project req are more thoroughly understood and documented
Occurs after collect req
Product analysis
Intent on improving teams understanding of a product and thus requirements
Product breakdown, req analysis, sys analysis, sys eng, value analysis, value eng
Project scope statement
Document used to level set stakeholders
Goals, product description, req, constraints/assumptions, identified risks
Product scope statement, deliverables, acceptance criteria, project exclusions
Create wbs
Main output is actually scope baseline
Decomposition
Process of breaking down project deliverables into progressively smaller units
Small enough to associate time and cost to one person
Scope baseline
Combo of project scope statement, wbs, wbs dictionary, work packages and planning packages
WBS
Work breakdown structure
Detailed, top down, graphical/hierarchical chart
Name, number, cost, time
Work package
Lowest level of wbs
Planning package
Not enough info to create wbs, too large
Control account
Cost account - scope, time, cost measured
Wbs dictionary
Details of wbs work packages
Name, number, cost, time, description, due dates, who
Validate scope
Ensuring hat product/service/result matches the documented scope
Inspecting verified deliverables into outputs of accepted deliverables
Concerned with completeness
Validate scope tool
Inspection
Control scope
Maintaining control of project by preventing scope changes from overwhelming the project and properly handling them
Customer isn’t always right but is the most important stakeholder - disputes should favor them
Performed once baseline is created
