Delivery Flashcards
(51 cards)
Requirement
A condition or capability that is necessary to be present in a product, service or result to satisfy a business need.
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.
Definition of Done (DoD)
A checklist of all the criteria required to be met so that a deliverable can be considered ready for customer use.
Quality
The degree to which a set of inherent characteristics fulfills requirements.
Cost of Quality (COQ)
All costs incurred over the life of the product by investment in preventing nonconformance to requirements, appraisal of the product or service for conformance to requirements, and failure to meet requirements.
What can a business case document provide?
A business case document often provides the business justification and a projection of anticipated business value from a project.
What do business documents demonstrate?
Business documents demonstrate how the project outcomes align with the organization’s business objectives.
Where are high-level deliverables identified?
In the business need docs; may range from detailed, baselined plans or high-level roadmaps that provide an overview of the project life cycle, major releases, key deliverables, reviews and other top-level information.
Deliverable
The interim or final product, service, or results from a project; deliverables reflect the stakeholder requirements, scope, and quality, along with the long-term impacts to profit, people, and the planet.
Requirement
a condition or capability that is necessary to be present in a product, service, or result to satisfy a business need.
How to elicit success criteria?
Interview stakeholders
analyze data
observe processes
review defect logs
In agile projects, when is backlog created?
In the ‘kick off’ meeting.
Well-documented requirements meet what criteria?
Clear
Concise
Verifiable
Consistent
Complete
Traceable
Scope
The sum of the products, services, and results to be provided as a project.
Scope Statement
Identifies the major deliverables associated with the project and the acceptance criteria for each deliverable.
Epics
Logical containers for a large user story that is too big to complete within an iteration.
Feature
A set of related requirements typically described as a short phrase or function, which represent specific behaviors of a product. Each feature will have multiple user stories.
User Story
A brief description of an outcome for a specific user; clear and concise representation of a requirement written from the end user’s perspective.
Where can Acceptance or Completion Criteria be found?
In a Scope Statement
Acceptance or Completion Criteria
Criteria required to be met before the customer accepts the deliverable or before the project is considered complete.
Where can Technical Performance Measures be found?
In a separate specifications document OR as an extension to the WBS known as the WBS dictionary.
Scope Creep
When additional scope or requirements are accepted without adjusting the corresponding schedule, budget, or resource needs. (projects that operate in a more stable environment)
Done Drift
When a ‘good enough for release’ or ‘done’ goal may be subject to change. (projects that operate in uncertain and rapidly changing environments)
How is scope creep combatted?
Using change control systems. Changes present to and approved by the project governance body, product owner, or executive sponsor.
