Agile templates

M
Must have
S
Should have
C
Could have
W
Won’t have
Essential features that the product needs in order to be viable in the first release
Think v1.1 not v2!
Essential features that can wait for a future release
Nice-to-have features
Features that are being excluded
This is an opportunity to set expectations
MoSCoW feature prioritization
Read more
Less: Something that isn’t going as well, and we should do less of
More: Something that’s bringing value to the team, and we should do more of
L
M
Individually, brainstorm answers for each letter. Try sharing back after everyone is done with the current letter.
Try using the timer feature which you can find on the right side of the screen.
Add: Something new that the team should incorporate in the next sprint
The exercise is divided into four brainstorms – each around a different word that starts with the letter K, A, L and M.
A
K
Keep: Something we are doing well and should continue doing
This template helps you and your team to reflect on your previous sprint and generate ideas or observations to share on the board
K
KALM Retrospective
Read more
If you like to keep your stickies private while you write them out, try using the stack feature in the top right of your screen!
Where have we failed to put this value into practice?
How have we put this value into practice?
Is this value still relevant? Does it help us achieve our mission?
Value
Add the value you’re discussing here
Try to use specific examples – a conversation, a meeting or a decision
Actions
Drag and drop to add content to this group
Don’t worry too much about figuring out what action you need to take at first
Be as open as you can about what you think went wrong
This is your opportunity to reflect on the value itself – if it isn’t helping, change it!
Values Retrospective
Read more
If you like to keep your stickies private while you write them out, try using the stack feature in the top right of your screen!
Sad
Mad
Glad
😡
'Mad' is for discussing things the team found frustrating in the last iteration.
Mad, glad, sad retrospectives...
This template helps you run a popular agile retrospective method for discussing team emotion and morale in the last iteration.
😢
'Sad' is for discussing disappointments from the last iteration.
'Glad' is for discussing things that made the team feel happy and motivated in the last iteration.
😀
Try using a countdown timer while running this exercise!
Individually brainstorm answers to each emotion, then share them back with the team when everyone is finished.
Mad, Sad, Glad Retrospective
Read more
🙏 Longed for
🤓 Learned
❤️ Loved
😩 Loathed
This team template is a simple way to assess the last sprint and figure out how to improve for next time.
What did you love about the last sprint?
What lessons were learned last sprint?
What do you wish could have happened to make your job easier in the last sprint?
The exercise is divided into four brainstorms, each with a corresponding group on the board.
Try brainstorming each group silently then sharing back one at a time. Use the stack feature in the top right to write privately!
What did you dislike about the last sprint?
The Four ‘L’s Retrospective
Read more
Bad
Good
Questions
👎
👍
🤔
Add positive thoughts here!
Add anything negative that happened to this group!
If you have questions related to the last iteration of work, add them here!
A very simple retrospective template...
Focus on the positives and negatives as well as any questions the team has about the last sprint.
Individually brainstorm answers for each group, then share them back with the team when everyone is finished.
Try changing the title of the group to 'Actions' instead. it might help the team to be proactive about improving processes.
Good, Bad, Questions Retrospective
Read more
Excellent
Start
Middle
End
Good
Bad
A template for facilitating retrospectives looking back over a longer period of time.
Reflect on milestones, points of change and lessons learned.
The board is split horizontally into three columns, allowing you to look back at recent events as well as the more distant past.
The board is split vertically into three rows, which let's the team indicate how well they felt events went on a scale.
It's helpful to give the team time at the start to brainstorm and write down thoughts.
When everyone's ready, get the team to add their stickies to the board, arranging chronologically left to right.
Get your team to try the 'Stack' feature. It allows everyone to write stickies privately then drop them on the board when they are ready.
Timeline Retrospective
Read more

Is something missing?