Jump ahead to any of the sections below:Īgile retrospective workflows and techniques This guide will primarily focus on agile retrospectives through the lens of scrum, but any team can apply these practices to retrospective meetings.
The details will vary but the purpose is the same - to reflect on past work and potential improvements. Regardless of your chosen agile methodology, most agile teams approach retrospective meetings in a similar way. In scrum, agile retrospectives include the entire scrum team (comprised of a scrum master, product owner, and developers) and often product managers as well. Retrospective meetings originated as one of the official scrum ceremonies. Plan your next agile retrospective with Aha! Develop - try it free.Īgile retrospectives (also called scrum or sprint retrospectives) are closely tied to scrum methodology. The same goes for your successes - acknowledging what went well and is worth repeating can be just as impactful. Have you ever worked hard on something only to realize later that you should have done it differently? It is not always a good feeling, but the solutions you uncover in hindsight can be valuable input for your next try.
#Retrospect defintion how to#
During the retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better.Įven if you are not on a development team, you can probably relate to the concept of retrospection. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). An agile retrospective is an opportunity for agile development teams to reflect on past work together and identify ways to improve.
0 kommentar(er)
