Documentation
SolutionDeveloperComplianceProjects
  • Introduction
  • Gitbook Guidelines
  • PRELIMINARY ANALYSIS
    • Project Initiation
    • Business Goals
    • Information Analysis
    • Solutions Evaluation
    • Risk Assessment
  • APPLICATION DEVELOPMENT
    • Scrum Framework
      • Scrum Values
      • Scrum Roles
      • Scrum Compliance
    • User Requirements
    • Product Backlog
      • User Story
      • Story Mapping
      • Grooming
      • Roadmap
      • Best Practice
    • Sprint Planning
      • Planning Inputs
      • Task Definition
      • Task Sizing
      • Sprint Backlog
      • Best Practice
    • Sprint Execution
    • Sprint Review
    • Sprint Retrospective
    • Process Control
      • Sprint Burn-Up
      • Sprint Burn-Down
      • Sprint Velocity
      • Source Control
    • Risk Assessment
      • Data Privacy & Security
      • Postpone the release
      • Lack of participation or engagement
      • Incomplete backlog items
      • Project Scope Creep
      • Third-Party Dependency
      • Integration Issue
      • Outdated Technology
      • Budget & Time Constraints
      • Inadequate Testing
    • User Acceptance
    • Release and delivery plan
    • Literature
  • SERVICE MANAGEMENT
    • Service Lifecycle
    • Receiving Ticket
    • Ticket Management
      • Maintain Attributes
      • Ticket Assignment
    • Troubleshooting
    • Escalation
    • Monitoring
    • Evaluation
    • Risk Assessment
      • Support and Maintenance
      • Insufficient information
      • Misinterpretation of attributes
      • Insufficient Testing
      • Delayed deadline
      • Lack of continuous improvement
      • Lack of Stakeholder involvement
  • REVIEW & IMPROVEMENT
    • Dashboard Analysis
Powered by GitBook
On this page
  • What is a sprint burn-down chart?
  • Who are involved in a sprint burn-down chart?
  1. APPLICATION DEVELOPMENT
  2. Process Control

Sprint Burn-Down

PreviousSprint Burn-UpNextSprint Velocity

Last updated 1 year ago

What is a sprint burn-down chart?

The predicted effort-hours remaining for a specific amount of time during a Sprint are shown graphically as a burn-down during a sprint. The sprint burn-down chart, as shown below, is created by plotting the total effort-hours left for each unfinished work on a particular day on a graph. This chart is important for expressing progress. To show the total projected work still needed to finish all the jobs, the chart should be updated daily.

Who are involved in a sprint burn-down chart?

  • Developers (the team)

  • Product Owner and

  • Scrum Master