Scribd
Upload
51 views1 page

Sprint Planning Template 01

The document outlines a Sprint Planning Template designed to facilitate effective team collaboration and goal setting in Agile-Scrum projects. It includes suggested steps such as preparing the meeting space, reviewing previous sprint results, establishing the sprint goal, and breaking down tasks to assess team capacity. The template emphasizes the importance of open communication, community building, and iterative processes to enhance team performance and focus on deliverables.

Uploaded by

mohammed adel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
51 views1 page

Sprint Planning Template 01

The document outlines a Sprint Planning Template designed to facilitate effective team collaboration and goal setting in Agile-Scrum projects. It includes suggested steps such as preparing the meeting space, reviewing previous sprint results, establishing the sprint goal, and breaking down tasks to assess team capacity. The template emphasizes the importance of open communication, community building, and iterative processes to enhance team performance and focus on deliverables.

Uploaded by

mohammed adel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Jesus’s Sprint Planning Template

Purpose Suggested Steps Techniques


•Get the room prepared (Meeting agenda is visible to everybody in the room, everything is set)
HELPS THE TEAM WITH •Welcome the scrum team to the room, make them feel safe by saying good morning/afternoon
CREATING THE BOND Build community •Ask an open ended powerful question to warm them up: i.e.: What’s new in our lives? What about your
REQUIRED TO MOVE ON
TOGETHER weekend?

HELPS THE TEAM WITH •Ask permission to the team to go over previous sprint results, which means :
CREATING AWARENESS
ABOUT WHAT HAPPENED Close previous Sprint •Revise sprint burn down to validate how the sprint went and ask/tell the team to look for patterns that
could lead the team to improve
PREVIOUS SPRINT

• Ask the Product Owner to set its expectations for the sprint by establishing the main focus of the sprint.

W W Identify/Discuss/Agree Sprint Goal • Ask the Product Owner to share the sprint goal with the development team
• Help the development team challenge the Product Owner sprint goal by asking open ended questions
H H Anything to be groom/refined from • Be sure that everything in the backlog is ready to be planned. If there is something to be discussed, go for
it. Ask the team if they feel OK to include the item into the sprint backlog and look for signs of
Y A Product Backlog? If yes let’s do it confirmation: Check the teams behaviour and watch them to validate if that match their speech.

T •Ask the Product Owner to go over of its sprint wish list.


The Product Owner Wish list for the sprint •Open the floor for questions about why are we doing this wish list. Challenge priorities until the team gets
common understanding (Remember: this is an iterative process, so you would get the team to do it step by step)

HELPS WITH CREATING THE


•Ask the team to Include breaks in the agenda sprint planning agenda and then stick to it.
STEP BACK TO THINK
MINDSET IN THE TEAM
Do we need a break before moving on ? •Make sure that it happens when planned.

Calculate Team’s capacity


ESTABLISHES LIMITS TO • I do use team’s median velocity and man hours to help team assess how accurate it’s the amount of work that the team is
HELP THE TEAM WITH
committing to deliver. Here is a formula that could help you with calculating Teams Capacity in hours for the sprint:
FOCUSING ON WHAT’S
(#Workable Hours x day )*(#Workable Days of the sprint)*(#Workable Days x developer )*(#Developers working)
POSSIBLE TO BE
DELIVERED
[Sprint level]
DEVELOPMENT TEAM
• Let the team break down every single item identified in the Product Owner Wish list in tasks (<=1 day. Duration). Ask the
TIME TO DISCUSS ABOUT
team to estimate how long it will take to complete each task in hours, in order to compare with the calculated Team
HOW TO DO THE JOB IN
Capacity in man hours. Once the team is done, challenge the sprint commitment comparing the amount of hours that
ORDER TO REACH THE
SPRINT GOAL
Task breakdown team committed to do with the calculated team capacity. Do the same with the amount of Story Points that the team is
committing to deliver and the median Velocity of the team.
HELPS THE TEAM GIVE
SOME VISIBILITY AND BE •Ask the development team to present to the Product Owner what would be the sprint
CHALLENGED ABOUT
WHAT’S GOING TO BE
commitment (what
DELIVERED (THE PLAN) Close the Sprint planning they are expecting to deliver by the of the sprint). Ask if it make sense for everybody in the room, and verify
with the Product Owner if the sprint backlog priorities ow are OK. Now the team is ready to start the sprint!

Improved to be used
www.jesusmendez.ca During the Sprint Planning
Template version 1.0 Fill Sens: for Agile - Scrum projects

You might also like