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-up chart?
  • Who are involved in structuring a burn-up chart?
  1. APPLICATION DEVELOPMENT
  2. Process Control

Sprint Burn-Up

PreviousProcess ControlNextSprint Burn-Down

Last updated 2 years ago

What is a sprint Burn-up chart?

A burnup chart displays the progress made during each sprint toward the target line, which represents the total amount of work in a release. The graphic's horizontal and vertical dimensions match those of the release burndown chart exactly.

The team displays how much work was accomplished throughout each sprint at its conclusion. After several sprints, a line linking these spots might be used to represent the team's anticipated velocity range. The team should also map out how much scope they want to finish for the release. Throughout the release, it could fluctuate or stay the same. Changes to scope are seen by a change in the scope target line, which is the main benefit of a burnup chart versus a burndown chart.

Who are involved in structuring a burn-up chart?

  • Scrum Team

  • Stakeholders