SCRUM

FRAMEWORK
AGILE METHODOLOGY
 SCRUM FRAMEWORK

• Scrum is a framework for project management that emphasizes teamwork,

accountability and iterative progress toward a well-defined goal.
• The Scrum framework is fairly simple being made up of a Scrum Team consisting of
a Product Owner, a Scrum Master and Development Team, each of which have
specific accountabilities.
• The Scrum Team takes part in five events and produces three artifacts in total.
SCRUM EVENTS
 What is a User Story?

• A user story is a short, simple description of a feature

told from the perspective of the person who desires the
new capability, usually a user or customer.
• User stories are often expressed in a simple sentence,
structured as follows:
“As a [persona], I [want to], [so that].”
User Story Description (iPad Inventory Tracker
Example)
 User Story vs Bug Ticket

• A bug is a problem which impairs or

prevents the functions of a product. A user
story is the smallest unit of work that needs
to be done.
 User Story vs Bug Ticket

• A bug is a problem which impairs or

prevents the functions of a product. A user
story is the smallest unit of work that needs
to be done.
 BACKLOG REFINEMENT SESSION

• Backlog Refinement is about creating shared understanding on what the Product will, and
won’t, do, on the effort it will take to implement it, and the order in which you’ll do that.
BACKLOG REFINEMENT SESSION
 BACKLOG REFINEMENT SESSION

• Steps for Backlog Refinement

1. SCRUM Master requests Product Owner to present User Stories with Description to team.
 BACKLOG REFINEMENT SESSION

• Steps for Backlog Refinement

2. Team or specific developer asks questions to the Product Owner.
 BACKLOG REFINEMENT SESSION

• Steps for Backlog Refinement

3. Story Estimations are done with the agreement with developers.
• Story Estimations Techniques
• Fibonacci Series
• T. Shirt Sizes
• Planning Pocker
• DARVIS Defined Formula (Agreed between Brian and Engineering Managers) (1 Story Point is
equal to Half Day of Work)
 BACKLOG REFINEMENT SESSION

• Steps for Backlog Refinement

4. Priorities are defined by the Product Owner.
 BACKLOG REFINEMENT SESSION

• Results of Backlog Refinement

• The outcome of the meeting is an ordered list of stories (based on priority and
dependencies) ready to be used in the next sprint planning.
• Teams can close gaps in their understanding of the stories and become closely aligned
on the work.
• Blockers are defined and discussed

• Saves time and money by ensuring that its items are ready for development at the right
time.
Sprint Planning Session

● Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint
planning is to define what can be delivered in the sprint and how that work will be
achieved. Sprint planning is done in collaboration with the whole scrum team.
● 3 Parts of the Session:
1. Capacity Planning
2. What Meeting
3. How Meeting
 Capacity Planning

• Capacity planning is to estimate the Scrum team's capacity for the work which can
be accomplished in the next sprint.
1. SCRUM Master lists total number of working days in a sprint.
2. SCRUM Master lists total number of hours available for all the team member.
3. Team members inform about planned leaves within the sprint and SCRUM master
calculates the total number of working hours.
 What Meeting

• The Scrum Product Owner defines the Sprint

Goal. Some of the examples are below:
Sprint Goal: “Show top-selling products on the
homepage”
Sprint Goal: “A visitor can order a product”
• Based on this goal the relevant entries in the
Scrum Product Backlog are chosen by the Scrum
Product Owner.
• These entries are updated and broken into
smaller stories so that they can be completed
within one Sprint.
 How Meeting

• The goal of the How-Meeting is to fill the Sprint

Backlog by identifying the concrete tasks needed
for complete implementation of the Scrum Product
Backlog entries.
• Tasks normally include design-, implementation-,
test- and documentation-activities.
• The tasks are estimated & prioritized.

• In case, if any user story or task cannot be

completed in a Sprint, then it is splitted down to
smaller level of user stories.
• Sprint tasks are reviewed and sprint is started with
set date.
 Team Velocity

• Velocity is a measure of the amount

of work a Team can tackle during a
single Sprint and is the key metric in
Scrum. Velocity is calculated at the
end of the Sprint by totaling the
Points for all fully completed User
Stories.
 Definition of Done

• The Definition of Done is an agreed-upon set of items that must be completed before a
project or user story can be considered complete.
 NEXT SESSION

1. Sprint Retrospective
2. Stand Ups
3. Backlog Grooming
4. Sprint Burndown Charts