{"id":11611,"date":"2017-07-20T13:35:25","date_gmt":"2017-07-20T13:35:25","guid":{"rendered":"https:\/\/www.process.st\/templates\/sprint-retrospective-process\/"},"modified":"2024-02-28T20:45:54","modified_gmt":"2024-02-28T20:45:54","slug":"sprint-retrospective-process","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/sprint-retrospective-process\/","title":{"rendered":"Sprint Retrospective Process"},"content":{"rendered":"
\n

Introduction: <\/h2>\n
\n

The exact same way that agile methodology encourages short, iterative bursts of work that incrementally improve your product, it also encourages iterating and improving upon the way you run sprints<\/strong>.<\/p>\n

A sprint retrospective is the process agile teams go through to optimize sprints by looking back on and learning from their successes and failures<\/strong>.<\/p>\n

The key part of a retrospective is asking the team what they think went wrong, what went well, and what could be done differently to improve. This checklist will give the process structure, and give you a place to record the information<\/strong> (and, if you like, to automatically send that information to another app like Slack<\/a> or JIRA<\/a>).<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Select participants <\/h2>\n
\n

Edit the sub-checklist items below with the names of your team members. Every time you run the process, check off who will be participating so you have a record.<\/p>\n<\/p><\/div>\n

\n
    \n
  • \n
    \n
    \n 1\n <\/div>\n<\/p><\/div>\n
    \n
    <\/div>\n<\/p><\/div>\n
    \n [Team member name 1]\n <\/div>\n<\/li>\n
  • \n
    \n
    \n 2\n <\/div>\n<\/p><\/div>\n
    \n
    <\/div>\n<\/p><\/div>\n
    \n [Team member name 2]\n <\/div>\n<\/li>\n
  • \n
    \n
    \n 3\n <\/div>\n<\/p><\/div>\n
    \n
    <\/div>\n<\/p><\/div>\n
    \n [Team member name 3]\n <\/div>\n<\/li>\n
  • \n
    \n
    \n 4\n <\/div>\n<\/p><\/div>\n
    \n
    <\/div>\n<\/p><\/div>\n
    \n [Team member name 4]\n <\/div>\n<\/li>\n
  • \n
    \n
    \n 5\n <\/div>\n<\/p><\/div>\n
    \n
    <\/div>\n<\/p><\/div>\n
    \n [Team member name 5]\n <\/div>\n<\/li>\n<\/ul><\/div>\n<\/section>\n
    \n

    Review tasks from last retrospective <\/h2>\n
    \n

    Find all tasks in JIRA tagged "Retrospective" from the last sprint and see how they progressed.<\/p>\n

    If they weren't completed, discuss why.<\/p>\n<\/p><\/div>\n<\/section>\n

    \n

    What went well \/ wrong during the sprint cycle? <\/h2>\n
    \n

    This is an opportunity to gripe about the sprint. It's an open forum, so feel free to say anything on your mind.<\/p>\n

    Each team member should have 1 thing that went well, and 1 thing that went wrong. If they don't, they should explain why.<\/p>\n<\/p><\/div>\n

    \n
    \n