The document outlines the sprint planning process for a cake shop's online ordering system, detailing inputs, outputs, and the roles of team members involved. It emphasizes the importance of defining user stories, priority estimation, sprint goals, and creating a sprint backlog to manage tasks effectively. Best practices and common challenges are also discussed to enhance the efficiency of the sprint planning meeting.

2. A DIVE INTO SPRINT PLANNING
Priyanka Nomula

3. GOAL OF THE MEETING
Inputs and outputs of sprint planning
Group activity of Sprint Planning
Evaluate commonalities and differences in approach
Share and reflect on sprint planning practices

4. WHAT'S YOUR SPRINT JOURNEY?
SPRINT DURATION YOUR ROLE ACTIVITIES DURING
SPRINT
HAPPY THINGS PAIN POINTS

6. PRODUCT
ROADMAP User journey
Estimation
Scope
RELEASE
PLANNING
PRODUCT
BACKLOG
GROOMING

7. CASE STUDY
Build online system for cake shop customers to order
cakes and track progress of their order.

8. MIND MAP/CAPABILITY
Website
Mobile
Online
shoppers
Retail
Outlets Event
Organisers
Restaurants
View
cakes
Single
cake
Order
number
Shippin
g
address
Status
updates
Email
updates
Add to
cart
Make
paymen
t
Order for
future
date
Multiple
cakes
Build online system for cake shop customers to order cakes and track
progress of their order.
Administrato
r
shipment
specialist
Baker

9. USER JOURNEY
Select Cake Add to Cart Review order
Make
Payment
Track order
Receive
order
Display cakes
View Cake
details
Select quantity
Edit Quantity
View order
Enter shipping
details
Generate Order
Number
Receive order to
shipping address
Remove cakes
from cart
Update cart
Add to cart Show Total
Amount
Choose payment
method
Enter payment
details
Process
payment
Enter Order
Number
Display Order
Status
Send confirmation
email

10. Stories Priority Estimation
As a shopper I want to be able to view a list of
so I can select one or more to purchase
As a user I want to ….
As a user I want to be….
As an administrator I want to be able to
As an administrator I want to be able to
…
…
Development
team gives
estimation
Product owner
sets priority
PRODUCT BACKLOG
GROOMING

11. PRODUCT
BACKLOG ITEMS
Stories Priority Estimation
As a shopper I want to be able to view a list of cakes so I can
select one or more to purchase
1
As a shopper I want to review my cart so I can make
adjustments prior to checkout
1
As a shopper I want to check out so I can get my cake shipped
to me
1
As a shopper I want to see my orders so I can see what I’ve
purchased in the past
3
As an administrator I want to modify the list of cakes so I can
adjust our offerings over time
2
As an administrator I want to view analytics about orders so I
can track progress on our goals
3
As a baker I want to view and print an order report so I can
prepare cakes
2
As a shipment specialist I want to be able to print packing
labels so I can ship packages
3
As a user I want to be able to track my order so I know when
my order is delivered
1

12. SPRINT PLANNING PREP
Review
Review product
roadmap and
vision.
Ask
Ask team
members to
update boards
and focus on
moving tickets
to done.
Feedback
Run sprint
review and
retrospective.
Groom
Groom product
backlog: Make sure
every user story has a
clear priority, is fully
formed, and up-to-
date with context and
estimates.
Create
Create a sprint
backlog of
enough user
stories to fill 2
sprints.
Choose
Proposed sprint
goal.
velocity
Check team
capacity and
establish velocity

13. SPRINT PLANNING
The work to be performed in the Sprint is planned at the Sprint Planning.
Start of the sprint planning meeting is the official start of the sprint and goal of this meeting is to select a set of PBIs
that will be delivered during the sprint.
Meeting has 2 distinct parts:
What can be delivered in the Increment resulting from
the upcoming Sprint?
How will the work needed to deliver the Increment be
achieved?
Duration of sprint planning
2 hours for 1 week sprint
4 hours for 2 week sprint
8 hours for 1 month sprint

14. CHECK
LIST
• Ensure your entire team is present.
• Status of open tickets, Discuss spill-
overs
• Create a sprint backlog of enough
user stories to fill 2 sprints.
• Discuss proposed sprint backlog: Let
the team pick user stories and tasks
that match the sprint goal and
capacity.
• Discuss acceptance test criteria
• Evaluate team’s capacity
• Define the sprint goal.
• Break down each user story into
individual tasks
• Discuss Approach
• Check definition of “done”.
• Create a “new sprint”.
• Move sprint backlog of agreed user
stories and associated tasks into the
new sprint.
• Get verbal confirmation from the
team that they know what to do.

15. SCRUM ROLES
Product Owner – Represents the client
and the business, own roadmap,
responsible for PBIs
Scrum Master – Responsible for ensuring
the team everything they need to deliver
value
Development team – A group of cross-
functional team members all focused on
the delivery of working software

16. SPRINT GOAL
Implement basic shopping cart functionality including add, remove, and update quantities on
their website.
Develop the checkout process: pay for an order, pick shipping, order gift wrapping, etc.
A short, one or two-sentence, description of what the team plans to achieve during the
sprint.
Examples:

17. PROPOSED SPRINT BACKLOG
As a shopper I want to be
able to view a list of cakes
so I can select one or more
to purchase.See image of the cakes
Click on view details
Add to cart from detail page
Search for a product
Sort option for viewing cakes
As a shopper I want to
review my cart so I can
make adjustments prior to
checkout.View Quantities and items in the
cart
See a total cost before tax and
shipping
Remove items
Adjust quantities
Click to navigate to cake detail page
As a shopper I want to
check out so I can get my
cake shipped to me
Trigger checkout from any page if
there are items in cart.
Enter shipping address
Enter Credit card details
Include tax and shipping before
finalising
Show confirmation page
Verify payment via payment
As an administrator I want
to view all my open orders
View all the open orders
Sort by time of order placement

18. SPRINT
PLANNING
BREAKOUT
SESSION
Role play of scrum team
Scrum master facilitates the planning
PO presents the story map/ high priority product backlog items
Discuss Q& A and details of the user stories
Development team selects user stories (Sprint backlog)
Development team breaks down user stories in to individual tasks
PO and Dev team declares the sprint goal
Apply acceptance criteria, constraints
Agree on definition of Done

19. ACCEPTANCE CRITERIA
• Given
• When
• Then
User story: As a cake shopper
I want to be able to checkout
So that I can get my cake shipped to me
Acceptance criteria :
Given I’m in a cake shop website and I have added a cake to my cart
When I am in any page of the website and I click on the my cart icon
Then the system allows me to initiate checkout process.

20. DEFINITION OF DONE
Definition od Done is a collection of valuable deliverables
required to produce software
Example:
• Unit tests passed
• Code reviewed
• Acceptance criteria met
• Functional tests passed
• Non-Functional requirements met
• Product Owner accepts the User Story

21. OUTPUT
SPRINT GOAL SPRINT BACKLOG

22. COMMON
CHALLENGES
Fixed Sprint Backlog
Introducing Brand new stories
Spill overs
Meetings
Unplanned leaves/holiday – Impacting velocity

23. BEST PRACTICES
PRESENT A LIST OF PBIS
> TEAM’S CAPACITY
ADVANCE NOTICE OF
USER STORIES
CHECK TEAM CAPACITY IMPORTANCE OF
SCRUM ROLES
FOCUS ON MVP

24. QUESTIONS

25. REFERENCES
• https://www.mountaingoatsoftware.com/
• https://www.scrumguides.org
• https://www.mitchlacey.com

26. THANK YOU