Scrum

1
User Stories
(Def) a high-level description of a requirement (i.e. functionality) that is
valuable to a user or product owner of the software product.
User Role – who?
Goal – what? functionality/feature
Reason – why? value adding

As a sales rep
I want to view a list of customers

so that I can pick one to contact.

2
Scrum
• An iterative and incremental agile SW development methodology.
• Frequent releases in short development cycles: 2 to 4-week sprints

Product Sprint
Backlog Backlog Increment
Sprint
Sprint Sprint
Review
Planning Sprint Execution Retrospective
(“Demo”)

Daily Scrum
+ Stakeholders
(“Stand-up”)

Task Burn Down

Board Chart

3
Scrum Roles

Product Owner Scrum Master

• client stakeholder who controls the Product Backlog • a facilitator
• removes impediments, resolves issues

Development Team
• 5-9 members
• Cross-functional skills
• “the developers”
• self-organizing teams
• complete control over organization & work processes
• They decide what goes in a Sprint

4
Scrum Meetings
Sprint Planning Daily Scrum (“Stand-Up”)
• 8 hours - Creating the Sprint Backlog • 15 mins daily – Status update w/in dev team
• Yesterday, Today, Barriers
• Part I: Product Owner presents the desired User • Attended by: Development Team, Scrum
Stories & the acceptance criteria for each story. Master

• Part II: Dev Team identifies tasks for each story;

creates time estimates per task; Sprint Review (“Demo”)
finalizes the user stories they can commit to. • 4 hours - inspect & adapt the product;
add new items to product backlog
• Dev Team gets to say if there are details lacking in • Attended by: Product Owner, Dev Team,
the user stories & cannot commit to certain stories Scrum Master PLUS: stakeholders
• Attended by: Product Owner, Dev Team, Scrum
Master
Sprint Retrospective
• Story Points – effort estimation • 3-hours - Process improvement
• Fibonacci Sequence: 1, 2, 3, 5, 8, 13 • lessons learned, successes & failure
• T-Shirt Sizing: S, M, L, XL • Attended by: Scrum Master, Dev Team

5
Fibonacci Sequence

0 1 1 2 3 5 8 13 21 34
The sum of the 2 numbers to the left

With Fibonacci, you will never see half of any number! It forces you to
think! User Story
A
0 1 1 2 3 5 8 13 21 34

Assume: User Story B is about half the difficulty of User Story A.

• Is this user story a little more difficult than half (i.e. 5)?, or
• Is it a little less difficult than half (i.e. 3)?
6
Scrum Meetings
Backlog Refinement (“Grooming”)
• Refining the next items on the product backlog to
prepare for the next sprint(s).

• It includes:
• Clarifying backlog items
• Reducing Epics into smaller items
• Determining dependencies

• Task can be done during a Sprint Planning Meeting

but many prefer to do it separate; some do this as a
separate meeting toward the end of a sprint.

Epic - a large
Backlog item

7
Scrum Artifacts
Product Backlog Increment
• Product Owner • Potentially shippable product
• Prioritized List of Product Backlog Items • Product Owner decides when to release
(PBIs)
• PBIs are written as user stories and
will have:
• Acceptance Criteria
• Story Points/Effort Estimated Task Board
– by dev team • For each item in the Sprint Backlog, list &
classify all tasks: To Do, In Progress, Done

Sprint Backlog
• Development Team
• List of PBIs committed to
Sprint Burndown Chart
• Shows amount of work remaining
• Includes the Tasks for each PBI
in one sprint

8
Task Board
User Story To Do In Progress Done
As a Sales Rep, I want to
view a list of customers so
that I can pick one to Design Modify the Modify the
Test the Use Case
contact. the UIs Domain CD
UIs Diagram

Create a sketch
of the UIs

As a Sales Rep, I need to

maintain client data &
locations so that we can Create a sketch Modify the Modify the
of the UIs Domain CD Use Case
properly determine their Diagram
product needs based on
their profile.
Test the
Design UIs
the UIs

9
Burndown Chart

10
Story Map
Useful when we have so many user stories and we need to understand
how to progress through them.

11