Scrum Glossary: Burn-down, Burn-up Charts, Coherence

• This glossary provides an overview of Scrum-related terms, some of which are not mandatory but commonly used.
• Refer to the Scrum Guide™ and the Professional Scrum Developer glossary for more information.

Burn-down Chart

• A burn-down chart visually represents the remaining work in a backlog.
• Time is plotted on the horizontal axis, while the amount of work remaining is on the vertical axis.
• The plotline typically descends as work is completed.
• Work can be measured using user story points or task hours.
• It can be used to communicate remaining work in both Sprint and Product Backlogs.

Burn-up Chart

• A burn-up chart shows the amount of work completed over time.
• Time is on the horizontal axis, and work completed is on the vertical axis.
• The plot line rises as work progresses.
• The amount of work can be assessed using story points or task hours.
• The total scope can be plotted as a line, which the burn-up line is expected to approach.

Coherence

• Coherence refers to the relationship between Product Backlog items that makes them valuable to consider as a whole.

Daily Scrum

• The Daily Scrum is a 15-minute, time-boxed event held daily.
• It is attended by the Developers to plan work for the next 24 hours.
• It optimizes team collaboration and performance.
• It happens at the same time and place each day to reduce complexity.

Definition of Done

• Definition of Done is a formal description of the state of the Increment when it meets required quality measures.
• The Increment is created when a Product Backlog item meets the Definition of Done.
• It creates transparency by ensuring a shared understanding of completed work.
• Items not meeting the Definition of Done cannot be released or presented at the Sprint Review.

Developer

• A Developer is any member of the Scrum Team committed to creating a usable Increment each Sprint.
• Regardless of technical, functional, or other specialty.

Emergence

• Emergence is the process of new facts or knowledge becoming visible unexpectedly.

Empiricism

• Empiricism is the philosophy that knowledge originates from experience and observations.
• It is a cornerstone of the scientific method.
• In Scrum, it means solving complex problems through exploration rather than predetermined plans.

Engineering Standards

• Engineering standards are shared development and technology standards that Developers apply to create releasable Increments.

Forecast (of Functionality)

• A forecast is the selection of items from the Product Backlog that Developers deem feasible for implementation in a Sprint.

Increment

• The Increment is the complete and valuable work produced by Developers during a Sprint.
• The sum of all Increments forms a product.

Product Backlog

• A Product Backlog is an ordered list of work needed to create, maintain, and sustain a product.
• It is managed by the Product Owner.

Product Backlog Refinement

• Product Backlog refinement occurs during a Sprint.
• The Product Owner and Developers add granularity to the Product Backlog.

Product Owner

• The Product Owner maximizes the value of a product by managing and expressing business and functional expectations.

Product Goal

• The Product Goal describes a future state of the product to plan against.
• It resides in the Product Backlog.
• The rest of the Product Backlog emerges to define "what" will fulfill the Product Goal.

Ready

• Ready is a shared understanding between the Product Owner and Developers on the level of description for Product Backlog items at Sprint Planning.

Refinement

• See Product Backlog Refinement

Scrum

• Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

Scrum Board

• A Scrum Board is a physical board used to visualize information for the Scrum Team, often to manage the Sprint Backlog.
• Scrum boards are an optional implementation to make information visible.

Scrum Guide™

• The Scrum Guide™ defines Scrum, including accountabilities, events, artifacts, and the rules that bind them together.
• It is written and provided by Ken Schwaber and Jeff Sutherland.

Scrum Master

• A Scrum Master guides, coaches, teaches, and assists the Scrum Team and its environment in understanding and using Scrum.

Scrum Team

• A Scrum Team is a self-managing team consisting of a Scrum Master, Product Owner, and Developers.

Scrum Values

• Scrum Values underpin the Scrum framework: commitment, focus, openness, respect, and courage.

Self-Managing

• Self-managing Scrum Teams decide internally who does what, when, and how.

Sprint

• A time-boxed event (one month or less) that contains other Scrum events and activities.
• Sprints are done consecutively.

Sprint Backlog

• The Sprint Backlog provides an overview of the development work to achieve the Sprint Goal.
• It includes a forecast of functionality and the work needed to deliver it, and is managed by the Developers.

Sprint Goal

• The Sprint Goal is a short expression of the purpose of a Sprint.
• Functionality might be adjusted during the Sprint to achieve the Sprint Goal.

Sprint Planning

• Sprint Planning is a time-boxed event (8 hours or less) to start a Sprint.
• The Scrum Team inspects the Product Backlog and designs work into the Sprint Backlog.

Sprint Retrospective

• Sprint Retrospective is a time-boxed event (3 hours or less) to end a Sprint.
• The Scrum Team inspects the past Sprint and plans for improvements.

Sprint Review

• The Sprint Review is a time-boxed event (4 hours or less) to conclude the development work of a Sprint.
• The Scrum Team and stakeholders inspect the Increment, assess progress toward the Product Goal, and update the Product Backlog.

Stakeholder

• A Stakeholder is a person external to the Scrum Team with interest and knowledge of the product.
• They are represented by the Product Owner and engaged at Sprint Review.

Technical Debt

• Technical Debt is the unpredictable overhead of maintaining the product, often from less than ideal design decisions.
• It may exist unintentionally or be introduced purposefully.

Values

• The Scrum pillars of transparency, inspection, and adaptation come to life and build trust when the Scrum Team embodies commitment, courage, focus, openness, and respect.

Velocity

• Velocity indicates the amount of Product Backlog turned into an Increment during a Sprint.
• It is tracked by the Developers for use within the Scrum Team.