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 :)
“Hey Dev, stop for a Sec… it’s not all about Ops!” Admit it! Ever since you adopted DevOps, things are spinning way faster than you thought they would. Tools are taking care of the CI/CD process, an APM platform gives you insights into issues in production, and you are fully focused on your code. Having…
Quick analysis of the Cambridge Analytica scandal currently facing Facebook.
Office 2019 will only work on Windows 10 + what’s the difference between an MSI and Click To Run? | Adam Cogan
Office 2019 will only work on Windows 10. We also cover Windows installer technologies; what’s the difference between an MSI and Click To Run?
This is not the same container 101 talk you’ve seen a dozen times. The point of this talk is how to ship a container to production, once you’ve built it. We’ll containerize a .net core app, debug locally, set up continuous deployment, set up a container cluster and deploy to it.
Every year, each SSW office gets together to share fun, laughter and discuss their best work moments of last year. It’s a great time to share ideas and connect with all the families, that support us behind the scenes and help us be so awesome.
SSW TV was proud to sponsor this years’ DDD event in Brisbane. In this session Jeremy Cade walks us through Windows Server Containers what you need to know as an ASP.NET Developer. From the description: The game has changed: Containers, once the the sole dominion of Linux have made their way into the Microsoft stack.…
ASP.NET Core is a whole new world for ASP.NET developers because it opens the door to cross-platform development. However, it comes with a hefty price. Not only does it takes some time before you get your head around it, even deployment is now quite different. So how can you bring ASP.NET Core application and DevOps…
In this video, learn how to: Set up Typescript for Visual Studio in Angular2 Override Visual Studio’s inbuilt Node and Gulp versions to use your project or global versions How to launch Angular 2 on a blank default ASP.NET Core application How to set up ASP.NET Core to use index,html and static files