Scope Management Flashcards
Inverted Triangle Model
Time and cost is fixed, scope is varied
Triple Constraints Triangle Model
Scope is fixed, time and cost are varied
Grooming the Backlog
Product owner owns the backlog items, backlog refinement is the prioritization of backlog items
Scrum Artifact
Product backlog is the source for all product requirements, product owner sorts and prioritizes backlog items, development team works on most important items based on prioritized items in the product backlog
Collecting Project Requirements
Process of determining, documenting, and managing requirements
Project Requirements
Help define product and project scope
Benchmarking
Comparing two or more system, businesses, approaches. Set an external basis for performance, and comparing organizations for requirements.
Multicriteria Analysis
Systematic approach of determining, ranking, and eliminating project criteria. Performance metrics, risks, requirements
Affinity Diagram
Creativity technique used to identify solutions - groups ideas into clusters, each of which can be broken down again to analyze each subset
Mind Mapping
Brainstorm ideas, consolidate ideas, helps generate new ideas
Nominal Group Technique
- generate ideas and then vote on and rank ideas based on usefulness 2. each participant brainstorms the problem or opportunity with their ideas 3. The facilitator will add all ideas each person has created to a white board 4. ideas are discussed for clarify and understanding 5. privately vote on each idea from 1 to a high score of 5. rounds of voting and discussion take place to find a consensus on highest-scoring ideas
Facilitated Workshop
Joint application design - software development; SMEs and dev team meet to gather requirements
Agile Requirements Gathering
User stories define:
Role (who) - who benefits from the feature
Goal (what) - what the stakeholder aims to accomplish
Motivation (why) - benefit to the stakeholder
Context Diagram
Takes a requirement and puts it into context to how people interact with the item/product
Business Requirements
Higher level needs of the organization
Stakeholder Requirements
Needs of a stakeholder or stakeholder group
Solution Requirements
Features, functions, and characteristics of the product, service
Functional Requirements
Describe the behaviors of a product
Nonfunctional Requirements
Describe the environmental conditions or qualities
Transition Requirements
From the current state to the future state (operational)
Project Requirements
Actions, processes, or other conditions
Quality Requirements
Validate the successful completion of a project deliverable or fulfillment
Requirements Traceability Matrix
Based on requirements collection. A table that allows you to trace requirements across the project from entry, executing, into operations to track several characteristics
Defining the Project Scope Statement
Developing a detailed description of the project and product, describes the product, service, or result and establishes boundaries and acceptance criteria
Scope Baseline
Project scope statement, Project WBS, Project WBS dictionary
Work Breakdown Structure
Decomposition of project scope and subdivides the project work, deliverables oriented, visualizes the project, defines what’s in scope, serves as a deterrent to change
WBS Dictionary
Describes each item that we’re creating. Taking each deliverable and defining it.
Four Inputs for WBS Creation
Project Management Plan, Project documents, Enterprise environmental factors, Organizational process assets
Control accounts
Markers in the WBS that serve as a point of reconciliation for the project’s costs, schedule, and scope achievement in the project.
The WBS Dictionary should provide these things for each work package:
- A code of account identifier
- A description of what the element is
- Who is responsible for the WBS element
- Associated activities for the WBS element
- Required resources (such as people, equipment, and materials)
- The cost for the WBS element
- Quality and acceptance criteria
- Technical information when needed
- Vendors and associated contract information
Validate Scope
Inspection driven process - customer inspects project work to ensure phase and project completion. Reviews, audits, or walkthrough of what’s been created to get customer to accept the project as completed
Controlling Project Scope
Monitoring the status of the project and product scope, maintaining the scope baseline integrity to keep the project in scope
Variance Analysis
What was delivered vs what was expected, magnitude of variation, corrective or preventative action
Trend Analysis
Predict what is going to happen based on past experiences, project performance over time, are we improving or deteriorating
Provides details about how the project scope may be changed
Scope Management Plan
