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
shared understanding by the Product Owner and the Developers regarding the preferred level of description of Product Backlog items introduced at Sprint Planning
Ready
a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems
Scrum
a physical board to visualize information for and by the Scrum Team
Scrum Board
the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum
Scrum Guide
Role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use of Scrum
Scrum Master
a self-managing team consisting of one Scrum Master, one Product Owner, and Developers
Scrum Team
a set of fundamental values and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage
Scrum Values
This means teams internally decide who does what, when, and how
Self-Managing
Scrum Event that is time-boxed to one month or less, that serves as a container for the other Scrum events and activities
Sprint
Scrum Artifact that provides an overview of the development work to realize a Sprint’s goal, typically a forecast of functionality and the work needed to deliver that functionality
Sprint Backlog
a short expression of the purpose of a Sprint, often a business problem that is addressed
Sprint Goal
Scrum Event that is time-boxed to 8 hours, or less, to start a Sprint
Sprint Planning
Scrum Event that is set to a time-box of 3 hours, or less, to end a Sprint
Sprint Retrospective
Scrum Event that is set to a time-boxed of 4 hours, or less, to conclude the development work of a Sprint
Sprint Review
a person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery
Stakeholder
the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership
Technical Debt
an optional, but often used, indication of the amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Developers for use within the Scrum Team
Velocity
commitment, courage, focus, openness and respect are what?
values
