Project Scope Management Flashcards
1
Q
ITTOs: Plan Scope Management
A
Inputs:
- Project Charter
- Project Management Plan (Quality management plan, project life cycle, development approach)
- EEFs
- OPAs
Tools&Techniques:
- Expert judgement
- Data analysis
- Meetings
Outputs:
- Scope management Plan
- Requirements Management Plan
2
Q
Scope management plan
A
- Defines how scope will be defined, developed, monitored, controlled and validated
- Project Charter is the key input
- Historical information from prior projects and EEFs will drive this as well
- Is NOT the project scope statement
3
Q
Requirements Management Plan
A
- How will you plan, track and report requirements activities
- Configuration management activities
- Requirements prioritization process
- ## Metrics that will be used
4
Q
Requirements Traceability Matrix
A
- Table that outlines the requirements, assumptions, status, details
- Can also link the requirements to WBS
5
Q
Project Scope vs. Product Scope
A
- Product scope = features and functions of the product we are delivering
- Project scope = work to be completed in order to satisfy the project objectives
- Product scope drives the project scope (symbiotic)
6
Q
Product Scope
A
- Characteristics of customers’ deliverables
- Product backlog is adaptive
- Derived from collected requirements
- Will be validated at the end of the project to confirm that the scope was met
7
Q
Tailoring Scope Management Processes
A
- Determine how much knowledge and requirements management is needed
- What level of validation and control is needed
- Development approach (scrum vs. agile)
- How specific or stable are the requirements? how much flexibility is there?
- Governance
8
Q
Business Analyst
A
- Gathers and defines requirements
- Ensures that the requirements are met
- Identify problems
- Define the business needs
- Recommend viable solutions for needs
- Works collaboratively with the PM or can be the same persion
9
Q
Scope Management in Adaptive Environments
A
- Scope is not fully defined at the start
- Scope is refined over the life of the project
- Requirements can emerge throughout the project
- Time and cost are fixed but scope can vary
10
Q
Grooming the Backlog/Backlog Refinement
A
- Product owner owns the backlog
- Product owner prioritizes the backlog items and adds new ones before the next sprint or iteration
11
Q
ITTOs: Collect Requirements
A
Input:
- Project Charter
- Project management plan
- Project Documents
- Business case
- Agreements
- EEFs
- OPAs
T&T:
- Expert judgement
- Data gathering (interviewing stakeholders, focus groups, questionnaires and surveys, bechmarking)
- Data Analysis
- Decision making
- Data representation
- Context Diagram
- Prototypes
Outputs:
- Requirements documentation
- Requirements traceability matrix
12
Q
Benchmarking the Requirements
A
- Comparing two or more system, businesses and approaches
- Set an external basis for performance
13
Q
User stories
A
- Items in the product backlogs
- Defines the role (who benefits from the feature), goal (what the stakeholders aim to accomplish), motivation (benefit to the stakeholder)
14
Q
Business Requirements
A
- High level needs of the organization
15
Q
Solution Requirements
A
- Features, functions and characteristics of the product or service
- Functional - behaviors of the product (ex. amount of torque)
- Nonfunctional - environmental conditions or qualities (ex. how much it hurts your hand when you turn it)
