You are on page 1of 2

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

Scrum Artifacts Scrum Team Non-Scrum Roles


Product Backlog Product success Support the Scrum Team and

everything that might be


Release Planning Responsible for the ROI the Product

needed in this product


Responsible for the order Can be anybody who is not part

An ordered list of
Responsible for the product of Scrum Team: Customer, User,
Own the Product Backlog Sponsor, Vendor, Manager,...
Finding product improvements
Finding process improvements
Understanding requirements
Be sure that the PBL is
Focusing on a constructive attitude
What can WE do, to improve? 2 ho Focus on: WHAT should we do transparent / visible
urs Be sure the Dev. Team
s
ur Top
ic 1 understand the PBL Items
ho tiv
e Selected PBL

everything that is needed


.5 ec Feature delivery
sp
1

tro
Responsible for development Pillars Scrum Values

An ordered list of
Re

Responsible for quality

2h

for this Sprint.


Product S Transparency Commitment

To

ou
Vision Pro
du
Responsible for delivering the
Inspection Courage

pic

rs
el
ct useful increment in each Sprint

ec
the time is based on 2-week Sprint

2
Adaption Focus

DEV.
ted
Share progress &

Ba

PBL
Openness
remaining work

ckl
Respect

og
Self-organizing
P ro d u c t C h a

Sprint Backlog

identified by Scrum Team


Breaking down Task & create the Design

completed in this Sprint


3 - 9 Cross-functional,

List of necessary tasks


Focus on: HOW should we do it
full-time team members

cklog
Own the Sprint Backlog Scrum Approach

that have to be
Backlog Item: User Story
t Ba Facilitate Scrum Team
nge

WHO? WHAT? WHY?


Iterative, incremental delivery
rin
s

Responsible for increasing Self-organization


Sp
Re

productivity
vie

Continuous Improvement
w

Responsible for using the Scrum Collaboration


Product Potiential Shippable Product Increment Burndown Chart
framework
s

Value-based priority
ek

Updated daily by Team


w Facilitate, serve and

to show the remaining


2 Time-box

work (Everything is
Im 2h coach the Team, PO &
pe our Organisation
s

Transparent)
di
me Support to remove Impediments Agile Approach
nt
Bac
klog Reduce complexity
Impediment Backlog Handle changes
Use the 5-Whys
Increment rule for finding Identify and handle risk

meets the Definition of Done


A recognizable, improved,
root cause Produce values early

and has Customer value


incremental product that
Everyday Teamwork, have always a plan for 24 hours
At least 3 items in each
Feedback regularly
What did I do yesterday that helped the
Development Team meet the Sprint Goal ?
Sprint needed to work on Eliminate waste
in order to improve
Showing live demonstration What will I do today to help the Development working condition for the Avoid over-engineering
Getting feedback Team meet the Sprint Goal ?
Getting a deeper understanding of business
Scrum Team and Improve quality
Do I see any impediment that prevents me or the Organisation
Understanding the Product Changes Development Team from meeting the Sprint Goal ?
Traditional methods
scope
Meeting Time Allocation (time-boxed) Frequency Attendance
(2)

scope
Release Planning As needed As needed
(1)
drives
the budget
& schedule
Product Backlog refinement (Backlog Grooming) Max : 10% of the Capacity of the Dev. Team During the Sprint as needed
cost time
Sprint Planning Topic I (What) Max : 2 hours (2-week Sprint) At the beginning of the Sprint
Agile methods
Sprint Planning Topic II (How) Max : 2 hours (2-week Sprint) At the beginning of the Sprint scope
Daily Scrum (Stand-up) Max : 15 minutes Daily during the Sprint
scope
Sprint Review (should be with Stakeholders) Max : 2 hours (2-week Sprint) At the end of the Sprint is driven
by the budget
& schedule
Retrospective Max : 1.5 hours (2-week Sprint) At the end of the Sprint & after major events cost time

V170901
(1) (2)
Best Practice in offshore software development Mandatory Mandatory facilitating Service to the Scrum Team Agile Manifesto 2001, www.agilemanifesto.org
TWO - WEEK SPRINT TIMELINE ACTIVITY
What Planning Topic 1 (What) Planning Topic 2 (How) Sprint forecast Sprint Goal communication Backlog Ordering Sprint Review
Strategic Planning Product Owner
Dev- Team Dev-Team Product Owner Product Owner Product Owner
(Explain the Product Vision)

Tactical Planning Dev-Team Dev-Team Dev-Team


Dev-Team Dev-Team Product Owner
(Scrum Master facilitates) (Scrum Master facilitates) (Scrum Master facilitates)

When Sprint Start Sprint Start Sprint Start Sprint Start Middle of the second week Sprint End

Time Box Max : 2 hours Max : 2 hours Define the Sprint Goal before and Around 1-3 hours Max : 2 hours
share the updates after planning

Leading role Dev-Team, Dev-Team, Product Owner,


Dev-Team, Product Owner, Product Owner,
Scrum Master, Scrum Master, Stakeholder,
Scrum Master Stakeholder Stakeholder
Product Owner Product Owner Dev-Team, Scrum Master
Actions Product Owner will present the Create initial tasks, estimation Based on the velocity, Product Owner The Product Owner The Dev-Team will show the work that they
maintained Product Backlog. (maybe with Planning Poker) the Development Team communicates the reviews the updated could finish at the real environment. Changes
The Dev-Team can get the size will prepare the forecast forecast to Stakeholder Product Backlog with the may come out of this meeting and will be
of the Stories (L, M, S), they can Discussion about design and Priority e.g.: with MoSCoW added to the Product Backlog. The Product
get the order based on risk and architecture based on the Customer need Owner will define which stories are finally
customer value. Team members and value DONE (based on acceptance criteria and
will ask to clarify Requirements. DoD).
Output Backlog Items e.g. User Stories, Final Sprint Backlog: all Forecast: the Team’s Product Vision Revised Product Backlog Product Owner will accept or reject the
Selected potential Product Backlog initial Tasks for the upcoming commitment for and Release Plan presented and showed features
Items, Acceptance Criteria Sprint that need to be done the Sprint Backlog

Last Sprint MON TUE WED THU FRI MON TUE WED THU FRI Next Sprint

What Start Workshop Product Backlog refinement Pair work Sprint Retrospective
- Week
Dev -Team (SM facilitates),
Sprint Strategic Planning Product Owner Product Owner Dev-Team
Product Owner
Tactical Planning Dev-Team Dev-Team (SM facilitates),
Product Owner Product Owner
Product Owner
When Once at the beginning of the Project Second week, before Review During the Sprint Sprint End
Current Sprint
Time Box Depends on the project max 10% capacity of the Development Team Depends on the Dev-Team Max : 1.5 hours

Preparation Leading role Product Owner, Stakeholder


Product Owner, Stakeholder,
Dev-Team
Dev-Team, Scrum Master,
Dev-Team Product Owner
for next Sprint
Actions The Product Owner will work together The Product Owner also should spend his time The Dev-Team can work The Dev-Team will identify what was
with the Stakeholder to prepare the with the Dev-Team and review the updated with Pair programming. working well and what was not working
SCROOL Backlog Items e.g. User Stories. Product Product Backlog. Dev-Team can update the Other Dev-Team members during the last Sprint. This is basic for the
Owner and Stakeholder review the Product estimation with Points. Everybody in the Scrum can verify which available continuous improvement and increasing
Backlog. They add, update, modify the Team has to understand the Customer needs. solution is the best fit for the productivity and quality (for the Scrum
new and available stories. They may use customer needs. Team, Organisation and Product).
the Story mapping approach. The Product Owner also should be involved.

Output Story based on clarifications at the Product Updated Product Backlog, estimation of the To increase the quality, At least 3 impediments should be selected,
Backlog, Update Priority (MoSCoW). whole Product Backlog to keep it up to date. productivity and get which will be solved in the next Sprint.
Based on the customer needs. knowledge exchange.