![]() In the “start” part of this retro, the agile team looks at the actions they’ll take in the next sprint. Sprint planning can benefit from any of the agile retrospective templates below: Team members can choose from retrospective templates to customize their sprint meetings. Scrum teams can apply the four questions above in other retrospective templates or customize a template to conduct their post-mortems. Using retrospective ideas, the team populates the four quadrants of the retro template, producing a visual representation of their post-mortem. Through a process of iteration, the Scrum team brainstorm to come up with real-time solutions to take over to the next sprint. Is the team following processes that don’t deliver clear value?.What outcomes still require further investigation?.What questions still remain unanswered?.Other relevant areas include where the agile team didn’t deliver value, focus areas that require development, and what was confusing about the sprint. In this section, the team should focus on areas that weren’t as effective or did not go as anticipated and what areas need improving. What issues in the previous sprint are confusing?.Which areas specifically require improvements?.What did the team do that did not produce value?. ![]() The idea in this questioning phase is to clarify problem areas, where value was not produced, and what was puzzling in the previous sprint. New ideas can be risky, so the Scrum team should carefully consider opportunities for improvement. In this part of the template, the team explores new ideas for how to improve their follow-up approach. What should team members do in the next sprint?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |