We’ve converted the ‘The Sprint Retrospective’ definition from the 2013 Scrum Guide into cartoon form to illustrate how The Sprint Retrospective works in scrum process.
The Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.
This is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time -box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.
The purpose of the Sprint Retrospective is to:
– Inspect how the last Sprint went with regards to people, relationships, process, and tools;
– Identify and order the major items that went well and potential improvements; and,
– Create a plan for implementing improvements to the way the Scrum Team does its work.
The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of “Done” as appropriate.
By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself. Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
Take the Quiz!
About the speakers
Mr Scrum Master
Hello! I'm the Scrum Master, it's nice to be featured here on SSW TV :)
Power Automate lets power users automate away repeatable manual processes. They can go from zero to hero in under a day!
It’s important for all your SharePoint Sites to be as consistent as possible.
In the days of classic SharePoint, subsites were a popular way of organising your intranet. Modern SharePoint architecture leans toward a flatter hierarchy, where sub-sites are generally not recommended.
Not finding stuff you have permissions to is super frustrating. So this one has always confused us…. Do you consider it a bug?
Having inconsistent resource names across projects creates all sorts of pain:
– Struggling to identify resources
– Unsure what to label new resources.
– Risk of duplicating resources
In this talk, Jason Taylor will demonstrate an approach using permission-based authorization to overcome these limitations by building a flexible approach to managing roles and permissions from within your system. This will improve the maintainability and visibility of access control across your system. Putting the power into the hands of application users and administrators, rather than developers.
On the 4th of February we welcomed everyone back to the office with a fantastic lunch! 🥗
It has been a roller coaster 12 months with restrictions, so it was amazing to see everyone back in the office working side by side again 👏
Join Adam as he delivers the latest Tech News during our March User Group.
Our development team spent a few months working really hard on this new product, and Chief Architect Adam Cogan is officially launching it today.
Do you know the security best practices for both end-users and SysAdmins?
Join Adam for the 10 tips CEOs must know for both end-users and SysAdmins.
Learn from Patrick how valuable Ocelot is and see the ins and outs of building an API gateway and protect the services using Azure VNet.