Rita Hot topics Flashcards
(454 cards)
Scope
what is the definition of scope management?
(p 153)
Defining what work is required and then making sure all that work- and only that work-is completed
Scope
what is the difference between product scope and project scope?
(p 154)
product scope refers to the requirements related to the product, service, or result of the project, while project scope involves the work the project team would do to deliver the product of the project
Scope
what is timeboxing?
(p 154)
an agile planning tool using short, fixed periods of time set for the team to complete a selected in prioritize set of activities.
Scope
describe the purpose of a minimal viable product (MVP)
(p 154)
On an agile project, it allows the customer to take delivery of the product and use it while the team continues to build the rest of the product. Also known as the minimal marketable features (MMFs)
Scope
describe what a scope management looks like on a predictive project
(p 156)
- Develop a plan for how to plan, validate and control scope and requirements
- Determine requirements
- Analyze and balance stakeholder needs to determine scope
- Create a WBS to break the scope down to smaller, more manageable pieces. Define each piece in the WBS dictionary
- Obtain validation (signed acceptance) that the complete scope of work is acceptable to the customer or sponsor
- Measure scope performance and adjust as needed.
Scope
describe what scope management looks like on an agile project
(p 157)
- requirements are identified and documented at a sufficient level of detail so they can be prioritized and estimated at a high level
- the product’s features are kept in the list called the product backlog
- the work is broken into product releases
- for each release, the work is completed through iterations
- the work of each iteration (and release ) is defined successively in more detail just before the work for each iteration begins
Scope
how is product scope different for agile projects than it is for plan-driven projects?
(p 157)
product scope is typically more flexible in agile projects.
Scope
what artifacts result from the plan scope management process?
- scope management plan
- requirements management plan
Scope
which is the difference between a product backlog and a product roadmap?
(p 158/159)
a product backlog is a list of the functional and non-functional work identified for the project, while a product roadmap is a visual representation of the product’s main components broken into sequential products releases
Scope
what is the difference between eliciting requirements in a predictive environment versus an adaptive environment?
(p 161/162)
predicting environments: A missed requirement early in the project could mean significant changes and conflict throughout the remainder of a project
adaptive environments: Agile teams initially define requirements at a high level and then progressively refines them, helping to avoid or lessen the effect of change requests
Scope
name several requirements-gathering techniques
(p. 162- 164)
- brainstorming
- interviews
- focus groups
- questionnaires and surveys
- benchmarking
- facilitation
- voting
- multicriteria decision analysis
- nominal group technique
- observation
- prototypes
- affinity diagrams
- mind maps
- context diagrams
Scope
what artifacts should the project manager look at to resolve competing requirements?
(p. 167)
competing requirements can be resolved by accepting those that best comply with the:
1. business case
2. project charter
3. scope statement
4. known project constraints
Scope
what are some ways requirements can be verified?
(p 169)
meetings
prototypes
iteration reviews
Scope
what are acceptance criteria?
(p. 169)
criteria used to ensure the project meets stakeholder requirements
Scope
what does the value of a requirements traceability matrix?
(p 170)
helps link requirements to objectives and/or other requirements to ensure the strategic goals are accomplished
Scope
what is product analysis?
(p. 172)
a method of analyzing the objectives and description of the product as stated by the customer or sponsor
Scope
what is the key artifact of the Define Scope process?
(p 172)
project scope statement
Scope
what are the key items included in a project scope statement?
(p 172)
- product scope
- project scope
- list of product deliverables
- acceptance criteria
Scope
what is not part of the project?
(p 172)
assumptions and constraints.
Scope
when is a work breakdown structure (WBS) created and what is it used for?
(p 173)
created during project planning by the team and used to define or decompose the project the smaller, more manageable pieces
graphically provides a structured vision for a project and helps Ensure that nothing is missed and no deliverables are forgotten
Scope
how are work packages different from from activities?
(p 174)
what packages are deliverables (things), rather than actions (activities)
Work packages are shown in the WBS
activities are shown in an activity list and network diagram
Scope
what is the WBS dictionary?
(p. 177)
documentation providing details needed to build each work package
Scope
what makes up the scope baseline?
(p 178)
- project scope statement
- WBS
- WBS dictionary
Scope
describe scope the composition on an agile project
(p 180)
- high-level requirements are gathered at the beginning of the project
- features are created from large and complex, high-level requirements
- medium-level requirements are broken into smaller stories
- each story needs to be broken further by various types of requirements