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
  1. APPLICATION DEVELOPMENT

Process Control

Senior management, stakeholders, and the Scrum team all need to be aware of the current status of the work at all times. In Scrum, each Daily Scrum and each Sprint Review serve as a means of tracking work, progress, and outcomes. With the Daily Scrum, Taskboard, and Burndown Charts, the Scrum team's tools for tracking project progress at the sprint level are particularly successful. This enables the team to spot issues before they become serious, moving and handling, and resolve them while they are still basic. The developer-created reports outline which user stories have been completed and if development is proceeding according to schedule.

The following “reports” are often used in Scrum. Here in order of importance:

  1. Taskboard

  2. Sprint Burndown Chart

  3. Release Burnup Chart

  4. Velocity Chart

PreviousSprint RetrospectiveNextSprint Burn-Up

Last updated 2 years ago