Almost important knowledge about Scrum is summarized in a page. [Made by Axon Active Vietnam | CC_BY-NC-ND]

1. (1) (2)
Scrum Artifacts
SprintBacklog
Understanding requirements
Focus on: WHAT should we do
Showing live demonstration
Getting feedback
Getting deeper understanding of business
Understanding the Products Changes
thetimeisbasedon2weekssprint
IsupdateddailybyTeam
thatshows
theremainingwork
Scrum Artifacts Scrum Artifacts
Finding product improvements
Finding process improvements
Focusing on a constructive attitude
What can WE do, to improve?
Review
SCRUM ON A PAGE
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile Manifesto 2001
Re
trospective
Planning Part I
PlanningPartII
User Story
WHO?WHAT?WHY?
S
electedPBL
Product
Backlog
ProductChanges
Potiential Shippable Product IncrementProduct
Product
Vision
2
hours
2
w
eeks
1.5
hours
2 hours
2hours
Release Planning
Breaking down Task
Focus on: HOW should we do it
Arecognizable,visibly
improved,operatingsubset
ofthisproductwhichmeets
thedefinitionofdone
Product Increment
Burndown Chart
Aprioritizedlistof
everythingthatis
neededforthisSprint
Selected PBL
Product success
Responsible for the ROI
Responsible for the product
Owns the Product Backlog
Feature delivery / report
Responsible for quality
Responsible for delivering
the potentially shippable
product of each Sprint
Report progress
based on remaining time
Self Organized
7 +/- 2 members
Owns the Sprint Backlog
Facilitate Scrum Team
Responsible for increasing
productivity
Responsible for using the
Scrum framework
Facilitates and Coaches
the Team
Owns the Impediment
Backlog Agile Approach
Scrum Approach
Legs
Impediment Backlog
Transparency
Inspection
Adaption
Iterative Development
Self-organisation
Continuous Improvement
Collaboration
Value based Priority
Time boxed
Commitment
Focuses
Reduce complexity
Handle changes
Identify and handle risk
Produce value early
Regularly feedback
Eliminate waste
Avoid over-engineering
Improve quality
Use the 5-Whys
rule for finding
root cause
Meeting Time Allocation (time boxed) Frequency Attendance
(2)
Sprint Planning Part I (what)
Sprint Planning Part II (how)
Daily Stand-up
Sprint Review
Retrospective
As needed
As needed
Max : 2 hours (2 week Sprint)
Max : 2 hours (2 week Sprint)
Max : 15 minutes
Max : 2 hours (2 week Sprint)
Max : 1.5 hours (2 week Sprint)
As needed
During the Sprint as needed
At the beginning of the Sprint
At the beginning of the Sprint
Daily during the Sprint
At the end of the Sprint & after major events
Release Planning
(1)
Backlog Grooming
(1)
Agile methods
scope
cost time
scope
is driven
by the budget
& schedule
scope
cost time
scope
drives
the budget
& schedule
Traditional methods
Listofnecessarytasks
identifiedbyScrumTeam
thathavetobe
completedinthisSprint
Sprint Backlog
At the end of the Sprint
Getting the team working closer together
Non-Scrum Roles
Can be anybody who is
not part of Scrum Team:
Customer, User, Sponsor,
Vendors, Manager,...
Observe, advise, supportProduct Backlog
Aprioritizedlistof
everythingthatmightbe
neededinthisproduct
At least 3 items in each
Sprint needed to work on
in order to improve
working condition for the
team
Owned by Scrum Master
Im
pediment Backlog
Scrum Team
What will I do today to help the Development
Team meet the Sprint Goal ?
Do I see any impediment that prevents me or the
Development Team from meeting the Sprint Goal ?
What did I do yesterday that helped the
Development Team meet the Sprint Goal ?
Best Practice in offshore software development Mandatory Mandatory facilitating As needed or service to the Scrum Team As needed also twice a day as a Scrum of Scrum together with Stakeholder, Product Owner Agile Manifesto 2001, www.agilemanifesto

2. The Team will identify what was working
well and what was not working during the
last Sprint. This is the basic for the
continous improvement and increasing
the productivity and quality. The Product
Owner also should be involved time by time.
Last Sprint
TWO WEEKS SPRINT TIMELINE ACTIVITY
What
Strategy Planning
Tactical Planning
When
Time Box
Involved
Actions
Output
Product Owner
(Explain the Product Vision)
Team
(Scrum Master facilitates)
Max : 2 hours Max : 2 hours Max : 2 hours
Team,
Scrum Master,
Product Owner
Team,
Scrum Master,
Product Owner
Product Owner will present
the maintained Product Back-
log. Team gets the size of the
Stories (L, M, S), get order
based on Risk and Customer
Value available. Team members
will ask clarified Questions.
User Stories, Selected
potiential Product Backlog
Items, Acceptance Criteria.
Team
(Scrum Master facilitates)
Team
(Scrum Master facilitates)
Team
Team
Product Owner
Team
(Scrum Master facilitates)
Sprint Start Sprint Start Sprint Start Sprint Start
10 minutes After meeting (by email
or personal)
Team,
Scrum Master
Product Owner,
Stakeholder
Create initial tasks, make
the final Estimation
(Using Planning Poker)
Check the velocity
with the commitment
of Sprint Backlog.
Product Owner
communicates the
commitment to Stakeholder.
Final Sprint Backlog, all
initialized Tasks for the
upcoming Sprint.
Commitment of
the Sprint Backlog.
Product Vision
Product Owner Product Owner
Product Owner
Backlog PrioritisationPlanning Part 1 Planning Part 2 Commitment Setting the forecast
Middle of second week
Around 1-3 hours
Product Owner,
Stakeholder
Product Owner,
Stakeholder,
Team, Scrum Master
The Product Owner
reviews the updated
Product Backlog with the
Priority based on MoSCoW.
Revise Product Backlog
and Release Plan
Review Meeting
Team
(Scrum Master facilitates)
Sprint End
The Team will make a live demonstration
of all finished features of this Sprint. Changes
may come out of this meeting and will be
added to the Product Backlog. The Product
Owner will define which story is finally DONE
(based on acceptance criteria and DoD).
Product Owner will accept or reject the
presented and demonstrated features.
What
Strategy Planning
Tactical Planning
When
Time Box
Involved
Actions
Output
Start Workshop
Product Owner
Product Owner
Grooming
Product Owner
Product Owner
Final Cross Test Retrospective Meeting
First week
Depends on the project
Product Owner, Stakeholder
Product Owner, Stakeholder,
Team
The Product Owner will work together
with the Stakeholder to prepare the
User Stories. Product Owner and
Stakeholder review Product Backlog.
They add, update, modify the new and
available stories.
Story based Clarification at the Product
Backlog, Update Priority (MoSCoW).
Team
Team
Team
Team (Scrum Master facilitates)
Team (Scrum Master facilitates)
Before Review
1 Day
The Product Owner should spend 5 to 15% of
his time with the Team or reviewing the updated
Product Backlog. Team will update the
estimation with Points.
Updated Product Backlog, estimation of the
whole Product Backlog to keep it up to date.
Second week, before Review
Around 1-6 hours (5-15%)
Team will make a Cross
team Test of all Stories.
Another Team member will
verify that the Stories have
been finished so far.
A whole tested System,
Knowledge exchange.
Sprint End
Max : 1.5 hours
Team, Scrum Master
At least 3 impediments, which will be
solved during the next Sprint.
SCROOL
MON TUE WED THU FRI MON TUE WED THU FRI
Current Sprint
Preparation
for next Sprint
Weeks
Sprint
Next Sprint
Product Owner, Stakeholder,
Team
Around 1-6 hours (5-15%)
Product Owner, Stakeholder,
Around 1-6 hours (5-15%)
Product Owner, Stakeholder,
Around 1-6 hours (5-15%)
Product Owner, Stakeholder,
Depends on the project
Product Owner, Stakeholder
Depends on the project
Product Owner, Stakeholder
Depends on the project
Product Owner, Stakeholder
1.5 hours
Team, Scrum MasterTeam
1 Day Max :
Team, Scrum Master