[Use Case Templates] Scrum / Sprint Retrospective ⏮
Hello, Community 🤗
2021 is almost over, but we still have time to look at another Use Case template 😊Today, we’d like to start a discussion about the Scrum/Sprint Retrospective Template.
Accessing Wrike’s Use Case Templates
Use Case templates are available in the Space creation dialogue. In order to use a template, start creating a Wrike Space how you usually would and you’ll see the option to create this space from a pre-made Wrike Use Case template:
Now, not only account owners and admins can use these templates, but also those users who have the right to create spaces 👍
What is Retrospective
A retrospective is a meeting held by a project team at the end of a project or process to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in the future iterations or projects.
If you’re not on an engineering team, it can still be a good practice to hold “lessons learned” meetings after a project is completed to discuss what went well, and what can be improved. It’s also a good opportunity to give shoutouts to team members and prepare a list of action items for improvements for future projects.
Scrum / Sprint Retrospective Template
With this pre-built template, you can streamline your post-sprint or post-project processes. It helps you ensure your retrospectives produce results that positively impact future projects or sprints. It will help you to:
- Ensure the team understands the goals and rules for each sprint with guidelines
- Organize individual feedback with individual board views
- Make retrospective meetings count by prioritizing action items
- Instantly organize feedback by category with a custom retrospective report
The template includes customizable board views for individuals and teams to organize retrospective feedback and turn it into actionable tasks.
When a project manager is ready to start a retrospective, they can use the sprint retrospective template to automatically set up boards. These will then help team members capture the right info, categorize it, and filter it depending on what information they need.
The project manager can use the sprint retrospective template as a guide to the following three steps.
Step 1: Ensure team members understand goals
The Scrum/Sprint Retrospective template automatically creates a task with goals and ground rules for sprint retrospectives, which can help all team members get on the same page before you start a retrospective. This information will also save project managers time by informing new team members about expectations.
After you launch this template, a folder called “Preparation” will automatically be created. It consists of an introduction, goals and ground rules, and Q&A represented as tasks.
Step 2: Set up individual and team boards
With this template, project managers or scrum masters can quickly set up individual boards, where team members can offer their own positive or constructive feedback. They’ll also be able to set up a team retrospective board where all feedback can be collected.
For ease of use, it also comes with a pre-created custom workflow that represents statuses needed for a successful retrospective meeting:
Step 3: Prioritize and assign action items
Finally, this template will automatically set up a board to view action items, and the project manager or Scrum master can drag and drop tasks in based on priority, assign accountability to individuals, and keep an eye on their status going forward.
What else?
The Scrum/Sprint Retrospective template also comes with a report that will give you an overview of all past retrospectives. It can be found in the Tools section:
The template also has pre-created custom fields to capture all important info for retrospectives:
Do you have retrospective or “lessons learned” meetings after projects or sprints? Please share how you manage those, or if you’d like to learn more and implement this process 👇
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
We actually have a call after the project is live to review any delays, why, and if there is a process to be reviewed / modified. Our company is big on Kaizen's! We would then use Wrike if we need to implement a new process.
Making an own space for retroperspective is an interisting idea to accumulate the knowledge over all projects. Up to now every project is doing it alone and writing meeting minutes.
We go through a "Lessons Learned" activity after each major milestone. We then assignee these lessons to owners to make sure that we mitigate and implement these lessons.
Thank you for sharing, everyone!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
We go through various reviews (in Wrike!), but I like the idea of a retrospective at the end of a project. Thanks for the info!
Okay, this is SUCH A COOL IDEA. One of our goals is to start doing more retrospectives after our large campaigns, and I love the way this is laid out and it's easily digestible.
So glad to hear this is useful for you, Sean Wright, Brittany Stringer 🤗
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
We do Retrospective Meetings after each large annual event. They are very helpful and can get us in line with what we need to do or change for the next semester or year. We haven't put them in Wrike up to this point but it would be a great place to house them so that everyone has access.
This is a great idea!! we have a post mortem process and this might be a great way to standardize this!
Great to hear this can be helpful for your teams, Melynda Willis, Sherrie Besecker 🙌
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
We do lessons learned after a project is released. We use a template to to document all the successes and pitfalls of the project. I will have to check on this. Sounds like this is going to be a great help for us! Thanks for sharing!
We don't have a documented process after a project is delivered/finished, but I'm sure gonna implement it now. 😃
Amazing! Please share how it goes, folks 🙌
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
What are Wrike's plans for a retrospective that includes a breakdown of effort vs time spent, estimated cost vs actual cost?
Hi Nicole DiTrani, I've raised this topic with our team 👍 I don't have news to share at the moment, but we'll keep you posted.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover