Scrum 101 Introduction To Scrum

SCRUM INTRODUCTION
 Why Agile? Why Scrum?
Arrielle Mali::CSM::CSPO
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:
Individuals and interactions over processes and tools

Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Project Vision Drives the Features
Waterfall Agile
The Plan creates The Vision creates
cost/schedule estimates feature estimates
Constraints Features Costs Schedule
Value -
Vision
Plan Driven
Driven
Estimates Cost Schedule Features

Waterfall Project Profile
Specify
Design
Code
Test
Ship
Time
Waterfall Project Profile
Phased Plan Driven
BDUF Expensive to change

Big Design Up Front
Contractual Document-centric
Integration surprises
Pull Systems
Input Capacity ?
Push systems overwhelm capacity,
creating turbulence, waste, and delay.
Input Capacity
Pull systems have a steady flow that
provides predictability.
Agile Benefits for Business
Quicker ROI Respond to Change

Lower Total Cost
Reduce Risk Stakeholder

Faster Time to Market
Arrielle Mali::CSM::CSPO Relations
Agile Benefits for Developers
Teaming A Sense of Done

Quality Work
Create
Feedback
ate
Im
pro
lid
Va
ve
Rhythm Visible Progress
SCRUM INTRODUCTION
 The Scrum Framework
What is Agile Software Development?
• Team Based
• Incremental
• Iterative
• Value Driven
• Frequent Delivery
• Production Quality
• Inspect & Adapt
What is Scrum?
PLA
N
T
AP
AD
Empirical
Process
IN
S
DO
PE
CT
Scrum Framework
1. What did you do
Release Planning yesterday?
2. What will you do
Daily Scrum today?
3. Do you have any
impediments?
Sprint
Review
Sprint
Sprint Retrospective
Product Planning 1-4 weeks Potentially
Backlog shippable
Sprint Backlog product
increment
Sprint Timeline
Sprint
Two Week Sprint Pattern Planning
Sprint Review
Development
Retrospective
Each
development
begins with a
Development Development
Daily Scrum
Analysis,
design,
coding,
testing & Development Development
integration in
a continuous
flow
The Scrum Team
Desired
Features
feature
feature
feature feature
feature
Feature
Feature
Feature
workin
Scrum Master
g
feature feature feature feature on

feature
Product Owner
Product
Delivery Team
The Product Owner
Sets the Vision
Manages Backlog
Elaborates Features
Decides Release
Dates
Develops the
product with
Reviews Work high quality.
The Team
•7 +/- 2
•Cross functional
•Full time
•Self organizing
•Empowered
•Trust
Scrum Master
Helps the Facilitates
Team be
awesome!
Protect
Coach
Teach
Administer
SCRUM INTRODUCTION
 Common Scrum Practices & Artifacts
Five Levels of Planning
Strategy Z
Portfolio P1 P2 P3 P4 P5
Vision Product Backlog
Roadmap Release 1 Release 2 Release 3
Release S1 S2 S3 S4 S5 SN
Sprint
Day
The Elements of Agile Planning
Priorities:
Which items
are more
Release Plan:
valuable?
How long will it take or how
many can we do by a given date?
Product
Backlog S1 S2 S3 S4 S5 SN
Sized: Velocity:
What is the effort, How much can the team
risk & complexity complete in a Sprint?
for each item?
Value:
What capabilities are needed
for financial success?
Product Backlog
Story
Dynamic set of
Story items to be done
Items are added
Spike
Story
Prioritized
Story
Refactor
Defect Constantly in flux

as the situation
Story changes
Story Items are removed
SAMPLE BURNDOWN CHART
User Story Template
As a <user role>,
I can <functionality>
so that <value>
Sample User Stories
As a registered user, I can As a purchaser, I can search

purchase OTC products for generic equivalents of
online so that I do not have brand named items so I can
to drive to the store. save money.
As a purchaser, I can get a As a vendor, I can see

receipt for a past monthly sales reports so I
transaction so that I can can see which products are
keep my own off-line selling best.
records.
INVEST Criteria for User Stories
I Independent Can deliver value by itself.
N Negotiable Details can be worked out by conversation.

V Valuable The value to the user is clear.
E Estimable Team understands it well to estimate.
S Small Fits in one Sprint.
T Testable We have clear test criteria.
Bill Wake 2003

User Story Details
<front>
Story 1: Home Page
Speclet
As a prospective user, I can • Formula
view the home page so that • UI design
I can decide if I want to try • Algorithm
• Business rules
the service.
<back>
Story 1 Acceptance Criteria
[] Shows company logo and site banner at top
[] Shows sales pitch Automated Tests
[] Introduces site services
[] Has copyright information at bottom
[] Uses site “look and feel”
Estimation Basics
2
Story 1: Home Page More than
As a prospective user, I can 2X effort
view the home page so that required
I can decide if I want to try
the service.
5
Story 19: Generics
• Quick As a purchaser, I can search
• Relative for generic equivalents of
• Estimation name-brand items so I can
• Done by Team save money.
Grooming Basics
Keeping the Product Backlog Healthy
Earlier Prioritization
Feedback
Story Mapping
Done By Team
Realistic Sprint
Sprint Commitments
Preparation
Shared
Ideation Understanding
Prioritization : MoSCoW
• Business Value
Must Have • New Knowledge
• Risk/Complexity
• Desirability
Should Have
Feature buffers
Could Have
Won’t Have Out of Scope
Source: The DSDM Consortium

Sprint Planning Meeting
Attended PART TWO
by:
Product
Priority
Backlog Which tasks can we

Other identify for each story?
PO, Team,
interested
Scrum
stake-
Master How long do we think
holders
each will take?
PART ONE
Which PBIs can Sprint Backlog

we commit to?
What is our
Sprint goal?
Sprint Retrospective
• Team meets privately

• PO?
•Format
• Gather Data
• Reflect on what worked well and what didn’t
• Generate Insights
• Discuss results and new ideas 1.5 hours
• Decide Action Items
• Consider adopting new practices
• Stop doing things that are not working
If we could redo the
If we could redo the Concrete ideas
same sprint again,
same sprint again, about what we
we would do these
we would do these could do differently
things the same
things differently. in the future.
way.
SCRUM INTRODUCTION
 Q&A
 Arrielle Mali :: CSM :: CSPO

Scrum 101 Introduction To Scrum

Uploaded by

Copyright:

Available Formats

You might also like

Scrum 101 Introduction To Scrum

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scrum 101 Introduction To Scrum

Uploaded by

Copyright:

Available Formats

SCRUM INTRODUCTION

 Why Agile? Why Scrum?

We are uncovering better ways of developing software by doing it and helping

Individuals and interactions over processes and tools

Constraints Features Costs Schedule

Estimates Cost Schedule Features

BDUF Expensive to change

Quicker ROI Respond to Change

Reduce Risk Stakeholder

Teaming A Sense of Done

 The Scrum Framework

feature feature feature feature on

 Common Scrum Practices & Artifacts

Vision Product Backlog

Roadmap Release 1 Release 2 Release 3

Defect Constantly in flux

Story Items are removed

As a registered user, I can As a purchaser, I can search

As a purchaser, I can get a As a vendor, I can see

I Independent Can deliver value by itself.

N Negotiable Details can be worked out by conversation.

E Estimable Team understands it well to estimate.

S Small Fits in one Sprint.

T Testable We have clear test criteria.

Bill Wake 2003

Won’t Have Out of Scope

Source: The DSDM Consortium

Backlog Which tasks can we

Which PBIs can Sprint Backlog

• Team meets privately

You might also like