�ݺ�ߣ

@jatinkhosla
#hello
#jambo #namaste #bonjour
I am Jatin Khosla, I primarily write software to collect,
organise , analyse , visualise & report Data.
I am extremely passionate about working with Data &
Programming Languages at the Intersection of Technology &
Purpose.
I ﬁrmly believe in the 'Do-Manifesto' : As the point of being
done is not to ﬁnish but to get other things done and done is
the engine of more and more is to change the world .

@jatinkhosla
simplicity is complexity resolved
Simpliﬁed processes help build complex systems

@jatinkhosla
#scrum
“an ordered formation of players, used to restart play, in which the
forwards of a team form up with arms interlocked and heads down,
and push forward against a similar group from the opposing side.
The ball is thrown into the scrum and the players try to gain
possession of it by kicking it backwards towards their own side. “
“disorderly crowd of people or things.“

@jatinkhosla
#scrum
“Scrum is a simple yet incredibly powerful set of principles and
practices that help teams deliver products in short cycles, enabling
fast feedback, continual improvement, and rapid adaptation to
change.”
What is Scrum ?
Who is it for ?
“Anyone who has a complex project can beneﬁt from using Scrum.
Whether you’re working on the next smartphone app, managing
logistics for a store, or planning a charity event, you can use
Scrum!”

@jatinkhosla
#the mantra
inspect
&
adapt

@jatinkhosla
#roles
1.product owner
2.scrum master
3.team member

@jatinkhosla
#product owner
• holds the vision for the product.
• represents the interests of the business.
• represents the customers.
• owns the product backlog.
• orders(prioritises) the items in the product backlog.
• creates acceptance criteria for the backlog items.
• is available to answer team members’ questions.

@jatinkhosla
#scrum master
• scrum expert and advisor.
• coach.
• impediment bulldozer.
• facilitator.

@jatinkhosla
#team member
• responsible for completing user stories to incrementally
increase the value of the product.
• self-organises to get all of the necessary work done.
• creates and owns the estimates.
• owns the ‘how to do the work decisions’ .
• avoids ‘not my job’ thinking .

@jatinkhosla
#team size
5 < 7 < 9

@jatinkhosla
#tools
1.product backlog
2.sprint backlog
3.burn charts
4.task board

@jatinkhosla
#product backlog
the product backlog is a cumulative list of desired
deliverables for the product
• who is it for ?
• what needs to be built ?
• why it needs to be done ?
• how much time it will take ?
• acceptance criteria ?
each deliverable must answer the below -

@jatinkhosla
#sprint backlog
the sprint backlog is a cumulative list of desired
deliverables for the given iteration.

@jatinkhosla
#burn charts
a burn chart shows us the relationship between time and
scope. It shows us how much scope the team has got
done over a period of time .

@jatinkhosla
#task board
the simplest task board consists of three columns: to do,
doing and done . Its job is to provide visibility to
stakeholders on progress being made .

@jatinkhosla
# done
to avoid confusion - team collectively deﬁnes -
What is done ?

@jatinkhosla
#sprint cycle
1.sprint planning
2.daily scrum
3.story time
4.sprint review
5.retrospective

@jatinkhosla
#sprint duration
1 to 2 weeks

@jatinkhosla
#sprint planning
typically marks the beginning of each sprint .
• commit to a set of deliverables.
• identify tasks to accomplish committed deliverables.
two objectives of the meeting -
1-2 hours for each week of iteration.

@jatinkhosla
#daily scrum
the stand-up meeting once each day.
• brief - no more than 15 minutes.
• pointed - completed tasks , expected , obstacles
characteristics of the meeting -
usually held at the beginning of the day.

@jatinkhosla
#story time
discussing and improving items across the
product backlog.
• define - What is the definition of done ?
• refine - Refine ‘ done ‘ criteria.
• task splitting - making items at the top of log ‘small’.
• size - Assign size to a task .
1 or 2 hours per week

@jatinkhosla
#sprint review
public end to a sprint.
• participants - All Stakeholders.
• demo - Show what’s done.
• feedback - Collect feedback .
1 or 2 hours per week of iteration .

@jatinkhosla
#retrospective
internal end to a sprint.
• identify any strategic changes needed to improve .
• its about - process improvement.
1 or 2 hours per week of iteration .

@jatinkhosla
#thank you
#asante #dhanyawad #merci
GitHub LinkedIn Blog Instagram

�ݺ�ߣ

hello scrum : Scrum in a nutshell

More Related Content

hello scrum : Scrum in a nutshell