Chapter 5 Flashcards
Define scope. Why is it important?
Scope is a set definition of the boundaries and deliverables of a project. Scope is important because it limits the work on the project to only what needs to be done, and prevents waste.
What is the concept of the triple constraint?
The triple constraint refers to the balancing act that must be performed between budget, schedule, and scope. A good manager must balance between these things in order for a project to be “realistic” in its ambition.
List the six scope management processes.
The six scope management processes are:
- Scope plan management
- Collect requirements
- Define scope
- Create the work breakdown structure
- Validate scope
- Control scope
What is done within the scope plan management process?
The scope plan management process is the process of defining how scope will be defined and verified (as in, who will verify it, and how).
What is requirements collection, in regards to scope?
Requirements collection is the process of working with customers and other stakeholders to determine what they need from the project, recording it, and using those requirements to determine scope.
What is the scope definition process, in regards to scope management?
Scope definition is the formalized process of defining a project’s scope in-detail. There are several things to be defined:
- Scope boundary: the scope boundary is the outer limits of scope, the yes/no line.
- Statement of work (SoW): the statement of work is a “narrative” description of the thing being developed, tying the business need with the requirements.
- Scope statement: a scope statement is a detailed document showing the project sponsor’s expectations.
What is the difference between project-oriented and product-oriented deliverables?
Project-oriented deliverables, like the name would suggest, are ones that support the project and its management processes. Product-oriented deliverables focus on the features and functionality of the in-development product, generally using use cases.
What is scope validation?
Scope validation is a part of scope management, in which the defined scope is formally accepted by the stakeholders. To do this, the MOV must be confirmed to match the scope, deliverables and milestones must be recorded, and stakeholders must formally accept the scope.
In regards to scope management, what does it mean to control scope?
Controlling scope is an ongoing process of monitoring change requests to ensure that they do not violate the scope borders that have already been set down.
What is “scope grope”?
Scope grope is a term used to describe the relative inability of many teams to figure out the scope of their project.
What is a work breakdown structure?
A work-breakdown structure is a tool (more like a framework) use to develop a project plan and link it to that project’s scope, as well as its budget. A work breakdown structure can be, itself, broken down into work packages (this is why breakdown is in the title).
What are work packages?
Work packages are the sub-components of a work-breakdown structure. Each work package is a “manageable” division of a component of the work itself, broken out into a set of deliverables and milestones.
What is a deliverable? What is a milestone? How are they related?
A deliverable is a thing that is to be provided/delivered as part of a project. A milestone is an event or achievement that signals or could act as evidence of the completion of a deliverable. Also, that a phase has ended. Basically, a way of looking at deliverables through the lens of time.
What is a crux?
A crux is a form of milestone, but one that references the testing of a key component of a project to see if it’s viable (things like ideas, technology, methods, etc).
What is scope leap?
Scope leap is when a project’s scope is extremely altered, by adding some functionality that is all-but entirely unrelated to the original scope or focus.
