Scrum 101

1
Scrum 101

• Heather BoninApril 9 2008

2
Outline

• Why Scrum?
• What is Scrum?
• Confessions of a (Scrum Master) Addict
• Top 10 Reasons You Think Youre Scrumming But
  Youre Not

3
Why Scrum?
4
analysis paralysis
no business engagement
5
Why Scrum?

• Recognition that
• Highly defined process with predictable start and
  finish dates for tasks is unrealistic
• Predictive, phased-project waterfall approach not
  working

• Reality is
• SW development is intellectually intensive,
  creative process
• Often developing in highly complex and uncertain
  domain
• Requires empirical management control process
  inspect and adapt feedback loops

Scrum is inspect and adapt feedback loops on
steroids!
6
What is Scrum?
7
Scrum is a basic framework with some simple rules.
Scrum is extremely simple but very hard.
Scrum is an Agile process framework that allows
organizations to continuously direct the project
toward early delivery of real business value
through the frequent and regular delivery of high
quality software. Ken Schwaber
8
(No Transcript)
9
Scrum Framework
basic FRAMEWORKProduct BacklogSprint
PlanningSprint iterationDaily Scrum
meetingSprint ReviewSprint RetrospectiveScrum
TeamScrum MasterProduct Owner
Product BacklogList of features, enhancements,
bugs, etc requested by business. Prioritized and
owned by Product Owner. Highest priority items
are goals for Sprint.
10
Scrum Framework
basic FRAMEWORKProduct BacklogSprint
PlanningSprint iterationDaily Scrum
meetingSprint ReviewSprint RetrospectiveScrum
TeamScrum MasterProduct Owner
Sprint PlanningAt start of Sprint, Product
Owner and Team meet to figure out how to achieve
highest priority Backlog items. Team creates
unassigned tasks and commits to Sprint Goal.
11
Scrum Framework
basic FRAMEWORKProduct BacklogSprint
PlanningSprint iterationDaily Scrum
meetingSprint ReviewSprint RetrospectiveScrum
TeamScrum MasterProduct Owner
Sprint iterationTeam has 30 days to complete
goals.Progress tracked daily. Daily Scrum
meetingStanding 15-min meeting for team.What
did you do yesterday? What will you do today?
What obstacles are in your way?
Scrum forces us to keep asking these
questions 1. What is the simplest thing that can
move project forward?2. Does what I am doing
right now move project forward?3. Are there any
impediments preventing progress?
12
Scrum Framework
basic FRAMEWORKProduct BacklogSprint
PlanningSprint iterationDaily Scrum
meetingSprint ReviewSprint RetrospectiveScrum
TeamScrum MasterProduct Owner
Sprint ReviewAttended by all stakeholders.Infor
mal demo of product.Communication of design
issues, risks, etc.Sprint RetrospectiveWhat
worked / what didnt.Its about common sense.
13
Simple Rules to accompany Basic Framework

• Teams are
• Co-located in an open space
• Seven plus or minus two
• Cross-functional with no roles
• Self-organizing self-managing
• Responsible for committing to work / Sprint goals
• Authority to do whatever is needed to meet
  commitment

14
Simple Rules to accompany Basic Framework

• Product Owner
• Can change priorities and features every Sprint
• Accepts / rejects work results
• Is responsible for business value of deliverables
• Scrum Master ensures team is fully functional,
  productive, and following scrum process
• Scrum Master handles organizational change

• Development
• Deliver sushi style
• Deliver Production Ready demonstrable workable
  code every month
• Optimize delivery daily
• Integrate deliverables daily
• Remove impediments asap
• Timebox everything
• Make a decision
• Never add work to an iteration
• Iterate and refactor

15
Confessions of a Scrum Addict
16
Confessions of a Scrum Master

• Its fun fun to deliver, fun to work in a
  group, fun to empower people
• Encourage familiarity
• Controlled chaos!
• Team ownership and accountability to each other
  drives pace
• Fast pace means all wasteful activity dropped
• Fast pace means its hard to stay ahead of team
• Totally demystifies skills, people, processes
• Communication is rapid fire
• Knowledge and skills spread rapidly
• Your business partners will love you --
  Unparalleled trust and partnership with customer
• Food does wonders

17
Top 10 Reasons You Think Youre Scrumming But
Youre Not
18
Top 10 Reasons You Think Youre Scrumming But
Youre Not

• You create a year-long project plan laying out
  how many iterations there will be and what will
  be in each and think you can enforce it.
• Management or Scrum Master is directing Scrum
  Teams work
• You need to sit for Daily Scrum because its much
  longer than 15 min
• Team members are pre-paying late fees to get out
  of Daily Scrum
• Product Owner has been out on extended leave and
  nobody noticed

19
Top 10 Reasons You Think Youre Scrumming But
Youre Not

• Scrum team does all its work via NetMeeting and
  email
• Scrum team spends half its time on documentation
• Team members are lt 75 on project
• Sprint Review has only analyses, designs or what
  were planning to deliver to show stakeholders
• Youre not producing better code, faster with
  happier developers and customers

20
Q A