Scrum
Balaji Sathram, PMI-ACP, CSP, CSM.
9th April 2015.
2
Samuel Johnson (1709-1784)
Lexicographer, Critic and Poet
Video: Lead India - The Tree
3
NONE
of us is as
STRONG
as
ALL
of us
4
Agenda
• Scrum-History
• What is Scrum?
• Agile manifesto
• Scrum Values
• Scrum Framework
• Scrum Roles
• Scrum Ceremonies
• Scrum Artifacts
• Scrum Rules
• Summary
5
Scrum-History
• 1986: Scrum was first defined as "a flexible, holistic product
development strategy where a development team works as a
unit to reach a common goal" as opposed to a "traditional,
sequential approach" by Hirotaka Takeuchi and Ikujiro Nonaka
in the "New New Product Development Game"
• Early 1990’s: Ken Schwaber used what would become Scrum at
his company, Advanced Development Methods, and Jeff Sutherland,
with John Scumniotales and Jeff McKenna, developed a similar
approach at Easel Corporation, and were the first to refer to it using
the single word Scrum
• 2001: Ken Schwaber worked with Mike Beedle to describe the
method in the book Agile Software Development with Scrum
Ken Schwaber Jeff Sutherland
Hirotaka Takeuchi Ikujiro Nonaka
6
What is Scrum?
• One of the agile methodologies
• A framework within which people can
address complex adaptive problems while
productively and creatively delivering
products of the highest possible value
• All activities performed in scrum are based
on agile manifesto and scrum values. Team
needs to practice these to achieve effective
team work and continuous improvement.
The scrum values are Commitment,
Courage, Focus, Openness and Respect
7
Agile Manifesto
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
That is, while there is value in the items on the right, we value the
items on the left more.
Individuals and Interactions Processes and ToolsOVER
Working Software
Comprehensive
DocumentationOVER
Customer Collaboration Contract negotiationOVER
Responding to Change Following a PlanOVER
8
Scrum Values
• Commitment
• Courage
• Focus
• Openness
• Respect
9
Scrum Framework
• Scrum framework consists of
Scrum roles
Scrum Ceremonies/Activities
Scrum Artifacts
Scrum Rules
10
Scrum Roles
3 Roles
• Scrum Master (SM)
• Product Owner (PO)
• Development Team (DT)
11
SCRUM MASTER PRODUCT OWNER
DEVELOPMENT TEAM
Scrum Ceremonies
5 Ceremonies
• Product backlog refinement meeting
• Sprint Planning Meeting
• Daily Scrum Meeting
• Sprint Review Meeting
• Sprint Retrospective Meeting
12
Scrum Artifacts
3 Artifacts
• Product backlog
• Sprint Backlog
• Product Increment
13
Scrum Rules
• Officially, the Scrum Guide is the Scrum
rulebook maintained by Ken Schwaber
and Jeff Sutherland. Please download
your copy here and go through it
14
Scrum
Framework
15
Summary
Scrum Practices
Scrum Roles
Scrum Master
Product Owner
Development Team
Scrum
Ceremonies
Product Backlog Grooming
Sprint Planning Meeting
Daily Scrum Meeting
Sprint Review Meeting
Sprint Retrospective Meeting
Scrum Artifacts
Product Backlog
Sprint Backlog
Product Increment
Scrum Rules
16
Thank you
17

Scrum

  • 1.
    Scrum Balaji Sathram, PMI-ACP,CSP, CSM. 9th April 2015.
  • 2.
  • 3.
    Video: Lead India- The Tree 3
  • 4.
    NONE of us isas STRONG as ALL of us 4
  • 5.
    Agenda • Scrum-History • Whatis Scrum? • Agile manifesto • Scrum Values • Scrum Framework • Scrum Roles • Scrum Ceremonies • Scrum Artifacts • Scrum Rules • Summary 5
  • 6.
    Scrum-History • 1986: Scrumwas first defined as "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach" by Hirotaka Takeuchi and Ikujiro Nonaka in the "New New Product Development Game" • Early 1990’s: Ken Schwaber used what would become Scrum at his company, Advanced Development Methods, and Jeff Sutherland, with John Scumniotales and Jeff McKenna, developed a similar approach at Easel Corporation, and were the first to refer to it using the single word Scrum • 2001: Ken Schwaber worked with Mike Beedle to describe the method in the book Agile Software Development with Scrum Ken Schwaber Jeff Sutherland Hirotaka Takeuchi Ikujiro Nonaka 6
  • 7.
    What is Scrum? •One of the agile methodologies • A framework within which people can address complex adaptive problems while productively and creatively delivering products of the highest possible value • All activities performed in scrum are based on agile manifesto and scrum values. Team needs to practice these to achieve effective team work and continuous improvement. The scrum values are Commitment, Courage, Focus, Openness and Respect 7
  • 8.
    Agile Manifesto We areuncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. Individuals and Interactions Processes and ToolsOVER Working Software Comprehensive DocumentationOVER Customer Collaboration Contract negotiationOVER Responding to Change Following a PlanOVER 8
  • 9.
    Scrum Values • Commitment •Courage • Focus • Openness • Respect 9
  • 10.
    Scrum Framework • Scrumframework consists of Scrum roles Scrum Ceremonies/Activities Scrum Artifacts Scrum Rules 10
  • 11.
    Scrum Roles 3 Roles •Scrum Master (SM) • Product Owner (PO) • Development Team (DT) 11 SCRUM MASTER PRODUCT OWNER DEVELOPMENT TEAM
  • 12.
    Scrum Ceremonies 5 Ceremonies •Product backlog refinement meeting • Sprint Planning Meeting • Daily Scrum Meeting • Sprint Review Meeting • Sprint Retrospective Meeting 12
  • 13.
    Scrum Artifacts 3 Artifacts •Product backlog • Sprint Backlog • Product Increment 13
  • 14.
    Scrum Rules • Officially,the Scrum Guide is the Scrum rulebook maintained by Ken Schwaber and Jeff Sutherland. Please download your copy here and go through it 14
  • 15.
  • 16.
    Summary Scrum Practices Scrum Roles ScrumMaster Product Owner Development Team Scrum Ceremonies Product Backlog Grooming Sprint Planning Meeting Daily Scrum Meeting Sprint Review Meeting Sprint Retrospective Meeting Scrum Artifacts Product Backlog Sprint Backlog Product Increment Scrum Rules 16
  • 17.