Study sets, textbooks, questions
Upgrade to remove ads
2B - Plan And Manage Scope
Terms in this set (46)
Scope Management Plan
Component of the project or program management plan that describes how the project scope will be defined, developed, monitored, controlled, and validated.
The features and functions that characterize a product, service, or result
The agreed-upon conditions or capabilities of a product, service, or outcome that the project is designed to satisfy
A technique used to gain project requirements from current documentation evaluation
An elicitation technique that brings together pre-qualified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result.
Written sets of questions designed to quickly accumulate information from a large number of respondents
A comparison of actual or planned products, processes and practices to those of comparable organizations to identify best practices, generate ideas for imporvement, and provide a basis for measuring performance
A formal or informal approach to elicit information from stakeholders by talking with them directly.
Agreement by everyone in the group on a single course of action
50% of the group's ideas
Decisions made by the largest block in a group, even if a majority is not achieved.
One person makes the decision.
A technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understand and to generate new ideas
A technique that allows large numbers of ideas to be classified into groups for review and analysis
Observations / Job Shadowing
A technique used to gain knowledge of a specific job, role, task, or function in order to understand and determine project requirements
An elicitation technique using focus sessions that bring key cross-functional stakeholders together to define product requirements.
Joint Application Design/Development (JAD)
Bring SMEs and the development team together to discuss and improve on the software development process
Quality Function Deployment (QFD)
Workshops that are commonly used in the manufacturing field to determine new product development requirements
A visual depiction of the product scope showing a business system, and how people and other systems (actors) interact with it.
A method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it
A prototyping method that can use visuals or images to illustrate a process or represent a project outcome
A description of how individual requirements meet the business needs for the project
High-level needs of an organization
Needs that come directly from a project stakeholder
Any feature, function, product, service or result of a project
Transition and Readiness Requirements
Temporary capabilities such as data conversion or training needed to transition from current to desired.
Any condition that the outcomes of a project and validated against
Requirements Management Plan
Component of the project or program management plan that describes how requirements will be analyzed, documented and managed
Requirements Traceability Matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
Project Scope Statement
The description of the project scope, major deliverables, assumptions, and constraints.
Work Breakdown Structure (WBS)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed
a document that provides detailed deliverable, activity, and schedule information about each component in the WBS
A technique used for dividing and subdividing the project scope and project deliverables into smaller, more manageable parts.
A management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement
a WBS component below the control account with known work content but without detailed schedule activities
Code of Accounts
A numbering system used to uniquely identify each component of the WBS
The approved version of the scope statement, WBS, and WBS dictionary
User Story Template
As a <role played>, I want to <goal> so that <reason>.
Definition of Done
An agreed upon list of the activities deemed necessary to get a product increment, usually represented by a user story, to a done state by the end of a sprint.
Definition of Ready
A team's checklist for a user-centric requirement that has all the information the team needs to be able to begin working on it
A set of conditions that is required to be met before deliverables are accepted.
The process of formalizing acceptance of the completed project deliverables
At or near the conclusion of the timeboxed iteration, the project team shared and demonstrates all the work produced during the iteration with the business and other stakeholders
A technique for determining the cause and degree of difference between the baseline and actual performance.
An analytical technique that uses mathematical models to forecast future outcomes based on historical results.
Other sets by this creator
2 - Plan and Manage Quality of Deliverables
2 - Plan and Manage Budget and Resources
2D - Plan and Manage Schedule
2A - Determine Appropriate Project Methodology