This document outlines the key elements of a Scrum sprint structure: 1. It defines common Scrum terms like user stories, sprints, product owner, and scrum master. 2. It describes the sprint flow as consisting of product backlog, backlog refinement, sprint planning, daily scrums, development, testing, sprint review, and retrospective. 3. It provides information on creating and ordering a product backlog, estimating effort using planning poker, and planning a sprint to select backlog items within the team's estimated sprint capacity.

1. Scrum Sprint Structure
Workshop
Nermina DURMIC
nermina@agile.ba

2. About Me
• Product Owner, Mistral Technologies
• Co-founder of Bosnia Agile
• PhD Candidate, Information Technologies, IBU
My Backlog
• To become a certified ScrumMaster

3. Agenda
Product
Backlog

4. Key Terms
• User Story A short, simple description of a feature told from the perspective of
the person who desires the new capability
• Sprint An iteration of work during which an increment of product functionality
is implemented
• Product Owner A person responsible for maximizing the value of the product, the work
of the Development Team, and management of the Product Backlog.
• Scrum Team Optimally comprised of seven plus or minus two people
• Scrum Master A facilitator for the team and product owner. He makes sure Scrum
practices are implemented correctly.

5. Sprint Flow

6. Long story short
Product Backlog
Backlog Refinement
Sprint Planning
Sprint Backlog
Daily Scrum
Development
Testing
Sprint Review
Sprint Retrospective

7. Product Backlog
• An ordered list of everything that might be needed
in the product
• A single source of requirements for any changes to
be made to the product
• The Product Owner is responsible for the Product
Backlog, including its content, availability, and
ordering
• Can be composed of:
o Features in form of Themes/Epics/User Stories
o Bugs
o Technical work
o Knowledge acquisition

8. Exercise: Create Product Backlog 20min.
• Read the functional
requirements for a new product
• Break the functional
requirements into user stories
• HINT: For each functionality
think about “WHAT needs to be
seen” and “HOW can it be
accomplished”

9. Exercise: Ordering 10min.
Ordering of Product Backlog determines Product Backlog items’ order of delivery
• Assign value to each card (Product Backlog Item) starting from 1 with respect of its importance
and possibility of delivery
• No two Product Backlog Items can have the same value
• Sort

10. Backlog Refinement
• Its purpose:
to help the Product Owner get the top of the
Product Backlog ready for the next Sprint
Planning Meeting
• It includes:
o Estimation of effort
o Clarification of requirements
o Decomposition of large product Backlog items
into smaller ones
• Whole team involved

11. Estimating Effort
• Why is estimation necessary?
• Sprint Velocity
• Planning Poker:
An agile estimating and planning technique
(1, 2, 3, 5, 8, 13, 21, ...)

12. Exercise: Planning Poker 15min.
1. Install Scrum Poker application
2. Choose an average sized Product Backlog Item and assign it the value “5” as an estimate of
work to do it
3. Everyone at the table votes on the relative effort required for each Product Backlog Item
• Effort can be marked with 1, 2, 3, 5, 8, 13, 21 ….
• Discuss it further if large discrepancies in voting occur
• All team members should agree about the final Item estimate
• If decision should be made between two values, use the higher one
4. Write the relative size on the Product Backlog Item
5. Calculate the total effort by summarizing the effort values on all Product Backlog Items

13. Sprint Planning
• The work to be performed in the Sprint is planned
at the Sprint Planning Meeting
• Sprint velocity
• Whole team involved
• Result of Sprint Planning:
o Defined sprint goal
o Defined sprint backlog

14. Exercise: Sprint Planning 5min.
• Assume your team can deliver 20 points per sprint
• Sprint is 2 weeks
• Plan the first sprint with respect to Product Backlog
Items’ ordering values and estimation

15. Follow Us
www.agile.ba
LinkedIn - http://www.linkedin.com/groups/Bosnia-Agile-7415020
Facebook - https://www.facebook.com/BosniaAgile
Twitter @BosniaAgile

17. Scrum Sprint Structure
Workshop
Nermina DURMIC
nermina@agile.ba