Scrum Glossary Flashcards
shows the amount of work which is thought to remain in a backlog
Burn-down Chart
shows the amount of work which has been completed
Burn-up Chart
The quality of the relationship between certain Product Backlog items which may make them worthy of consideration as a whole
Coherent/Coherence
Scrum Event that is a 15-minute time-boxed event held each day for the Developers
Daily Scrum
a formal description of the state of the Increment when it meets the quality measures required for the product
Definition of Done
any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each Sprint regardless of technical, functional or other specialty
Developer
the process of the coming into existence or prominence of new facts or new knowledge of a fact, or knowledge of a fact becoming visible unexpectedly
Emergence
process control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation
Empiricism
a shared set of development and technology standards that Developers apply to create releasable Increments of software
Engineering standards
the selection of items from the Product Backlog Developers deems feasible for implementation in a Sprint
Forecast (of functionality)
Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint
Increment
A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product
Product Backlog
the activity in a Sprint through which the Product Owner and the Developers add granularity to the Product Backlog
Product Backlog refinement
Role in Scrum accountable for maximizing the value of a product
Product Owner
describes a future state of the product which can serve as a target for the Scrum Team to plan against
Product Goal