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

Sprint Retrospective

General information

PreviousSprint ReviewNextProcess Control

Last updated 1 year ago

  1. Goals

The Sprint Retrospective's goal is to develop strategies for raising quality and effectiveness. The Scrum Team evaluates the performance of the previous Sprint in terms of people, interactions, procedures, tools, and their definition of done. The Scrum Team talks about what worked well during the Sprint, what did not work well, and how problems were solved (or not). The most beneficial changes are chosen by the Scrum Team to increase efficiency. They might even be implemented into the next sprint's backlog. The Sprint comes to an end with the Sprint Retrospective. For a Sprint of one month, it is timeboxed to a maximum of three hours.

  1. Scope

Working instruction covers enterprise application employees in Europe.

  1. Responsibility

  • Scrum team: Participates in the meeting.

  • Manager: He can also be involved in the meeting.

(scrum.org,n.d.)

Steps in Sprint Retrospective

  1. Reflect on the previous sprint: Take time to reflect on the past sprint, including what worked well and what did not.

  2. Identify areas for improvement: Identify areas where the team can improve and make changes to ensure future sprints run more smoothly. The rest of the Scrum Team is encouraged by the Scrum Master to improve their procedures and methods in order to make the upcoming Sprint more efficient and enjoyable. The Scrum Team makes plans to raise product quality during each Sprint Retrospective by enhancing work processes or, if necessary and not in conflict of product or organizational standards, changing the definition of "Done."

  3. Brainstorm solutions: Brainstorm solutions to the problems identified during the reflection phase. The Scrum Master can assist in generating improvement idea brainstorming if the team is very vocal.

  4. Review progress: Review progress from previous sprint retrospectives to ensure that actions have been taken and improvements have been made. You can improve the next sprint using the patterns you have found. The patterns that need to be improved most should be decided by the team. You can use Microsoft Teams board to review the progress during the sprint. Everybody can explain his viewpoint and he can propose solutions for the next sprint.