Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our goals?

Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our goals?

Purpose

Capture learnings from [initiative] and identify what went wrong so we can get better

The Situation

Put all the details of what happened here. Only the facts. Make sure you answer who what where when why. Customer feedback is good to include if we have it. Include any and all mistakes and what went well. Break up into sections, like “research” “engineering” “customer feedback” “the feature” “marketing efforts” etc.

The results

What happened as a result of the situation? This could include how an initiative performed, what happened as a result of a bug, how a feature fared, etc. Support this section with data

What went wrong

All the details of what went wrong. Opinions are welcome here. Be fair to other people who were involved and let them add to the postmortem or give you context as needed. In the case of bugs, what we could have done better to prevent a problem can be included here as well.

What we can do better next time

Whatever we learned that will affect how we do things next go around, it goes here. This is the synthesis of everything we’ve figured out from doing the postmortem.

Action items

Any action items we have, and who owns each of them, plus dates if possible

Capture Input

Do any key stakeholders have discussion points, insights, ideas, or requests to contribute? Share this template before the product roadmap meeting to gather feedback.‍

The Big Picture

With stakeholder input, develop a clear product vision by identifying the strategic goals most important to your organization. Examples include customer acquisition, churn reduction, technical improvements, upselling new services, etc.‍

Identifying Themes

What themes can be formed by grouping together the listed initiatives, features, and epics? ‍

Prioritization

Why is each theme being pursued? What value does each one provide to the customer? Make sure to account for market space, customer data, and potential return on investment for each new project.‍

Execution Strategy

Break each initiative down into specific tasks, requirements, and deadlines. Confirm that each one is viable by allocating resources accordingly. Assign ownership and designate release dates.‍

Measuring Success

What metrics will you use to measure progress for each initiative? Define what success looks like.‍

Key Risks & Concerns

What potential issues could arise? How can we solve them? Does the scope of work allot enough time for unexpected issues?‍

Main Takeaways

What were the main insights from this product roadmap meeting? Include key decisions made, opportunities, and potential issues that should be shared with key stakeholders.‍

Visualization

Put together a visual aid for your roadmap. Ensure it communicates product direction and value to key stakeholders. Also, make sure that your engineering team can use it to see details and logistics clearly. Your roadmap should be dynamic so that it can easily evolve and adapt to changes over time.‍

Take Action

What can be done now? Who is responsible? Clarify next steps, who's completing them, and when they should be done by. Note this information here to share.‍

Share

List all key stakeholders not present and other departments that this information should be shared with.‍

Follow-Up

Now that plans have been set in motion, it's time to schedule meetings with other stakeholder parties to align them on what's coming next. Ensure that everyone is on the same page and plan roadmap check-ins for the future.

Sprint Goal

What is the main purpose of this sprint? Define key objectives below.‍

Sprint Backlog

What user stories match the sprint goal? Share this with your team prior to the meeting so they can contribute. Break each user story down into individual tasks. Make sure each task has as much information as possible. Include important metrics.

‍Epics to be Delivered

List out the epics that we're planning to start or deliver during this sprint.‍

Scope of Work Clarification

Revisit your definition of "done." Decide on the acceptance criteria that will be used to determine when each individual task is complete. Make sure all of this realistically aligns with your team's capacity. ‍

Key Risks & Concerns

What potential issues could come up based on the goal and sprint backlog? How can we solve them? Does the scope of work allot enough time for unexpected issues

‍Notes and Takeaways

What were the main insights and discussion points from this sprint planning session?‍

Take Action

Get verbal confirmation from your team about the next steps to be taken. Clarify who's completing them and when they should be done by. Note this information here to share and assign.‍

Follow-Up

How will we keep in touch and stay up-to-date about progress? Should we schedule a follow-up meeting?

Quick Review

Summarize all notable events since the last retrospective. Share updates on initiatives, key metrics, and anecdotes. Compare the current timeline and deliverables with what was originally planned.‍

Positive Highlights

What went well? Were any special milestones accomplished? Let each team member contribute.‍

Reflect on Roadblocks

What went wrong? Did any unforeseen obstacles arise? Identify the root cause of each one. Allow each team member to contribute. And remember, this isn't a blame game—focus on continuous improvement.‍

Room for Improvement

What were the main lessons from the roadblocks discussed? How can we solve each issue and improve?‍

Other Important Feedback

Summarize any other valuable discussion points. It does not have to be directly related to the retrospective's main topic.‍

Main Takeaways

What were the main insights from this retrospective meeting? Include key decisions, plans, and any opportunities or concerns that should be shared with key stakeholders.‍

Take Action

Clarify next steps, who's completing them, how we will measure them, and when they should be done by. Note this information here to share and assign.‍

Follow-Up

How will we keep in touch and stay up-to-date about progress? When is the next retrospective?

Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our goals?

Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our goals?

Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our sprint goals?

Name

• What did you do yesterday?
• What will you do today?
• Where are you blocked?
• Comfort Level — How close are we to hitting our sprint goals?

--

Tips:

• Use this 15-minute meeting to check the pulse on your work and stay on top of your sprint
• Remember: Problem-solving is not part of scrum (although it can take place informally right after).
• Personalize this template with an update section with the name of each engineer
  

Last sprint

Celebrate what you achieved and discuss what wasn't completed.

Backlog

The list of things we want to accomplish in this sprint.

Sprint goal for the week

Why are we implementing these backlog items?

Assign backlog items

What items/tickets is each person focusing on during this sprint?

Notepad

Anything else to write down?

Links and Attachments

Documents and such that are referenced on the call.