Scrum Glossary Flashcards
Burn down chart
Measures amount of work in a backlog, by calculating the amount of work to do versus the remaining time.
Burn up chart
Measures the amount of work completed, by calculating the amount of work done versus the remaining time.
Coherence
Quality of relationship between Product Backlog Items.
Daily Scrum
15-minute Scrum event held every day to plan work and inspect and adapt progress in the Sprint
Definition of Done
Describes the state a Product Backlog Item must meet in order to be considered a Done Increment.
Developer
A member of a Scrum team that creates a usable Increment within a Sprint.
Emergence
Process of new knowledge coming into existence or prominence.
Empiricism
Philosophy behind Scientific method. In Scrum defines that solving complex problems is done by using an exploratory process and not predetermined plans.
Engineering Standards
Shared set of development standards that Developers must apply.
Forecast
The selection of Product Backlog Items that are deemed feasible to complete in the Sprint.
Increment
Scrum artifact defining complete valuable work produced by Developers in a Sprint
Product Backlog
Scrum artifact managed by a Product Owner that includes the work that needs to be done to create, maintain or sustain a product.
Product Backlog Refinement
Activity where Product Owners and Developers discuss and break down the Product Backlog.
Product Owner
A member of a Scrum Team that is responsible for maximizing value of a product, primarily by managing and communicating business and functional expectations to Developers.
Product Goal
Targeted future state of the Product.
Ready
Shared definition regarding the level of detail in PBIs required to introduce them in a Sprint.
Scrum
Leightweight framework for solving complex problems.
Scrum Board
A board for the Scrum Team to visualize information, namely the Sprint Backlog.
Scrum Guide
A definition that consists of Scrum’s accountabilities, events, artifacts, and rules.
Scrum Master
A member of a Scrum Team that guides and assists the team to properly understand and use Scrum.
Scrum Team
Self-managing team consisting of 1 Product Owner, 1 Scrum Master and 1 or more Developers, with a size no bigger than 1o people.
Scrum Values
5 fundamental qualities in Scrum: Commitment, focus, openness , respect and courage.
Self-managing
The Scrum Team has the skills and autonomy to decide internally who does what, when and how.
Sprint
A Scrum event timeboxed to a maximum of 1-month where the Scrum Team commits to delivering an Increment. It contains all other Scrum events.
Sprint Backlog
A Scrum Artifact that includes the development work necessary to achieve a Sprint Goal, including a forecast of functionality and the work needed to deliver it.
Sprint Goal
A short description of the purpose of a Sprint, what should be accomplished within it.
Sprint Planning
Scrum Event of no more than 8h (for 1-month Sprints) that starts the Sprint. The Scrum Team inspects the Product Backlog Item and creates a plan to turn the most valuables ones into an Increment within the Sprint.
Sprint Retrospective
Scrum Event of no more than 3h that ends the Sprint. The Scrum Team inspects the past Sprint and plans improvements for the next Sprints.
Sprint Review
Scrum Event of no more than 4h, where the Scrum Team and Developers inspect the Increment created, assessing its impact on the Product Backlog.
Stakeholder
Person external to the Scrum Team with interest and knowledge required for the product.
Technical Debt
Unpredictable overhead of maintaining a Product due to design decisions which increase the cost of ownership.
Scrum Pillars
Transparency, inspection and adaptation.
Velocity
Indication of the amount of Product Backlog Items turned into an Increment over the course of a Sprint.
