Академический Документы
Профессиональный Документы
Культура Документы
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
tro
Responsible for development Pillars Scrum Values
An ordered list of
Re
2h
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
cklog
Own the Sprint Backlog Scrum Approach
that have to be
Backlog Item: User Story
t Ba Facilitate Scrum Team
nge
productivity
vie
Continuous Improvement
w
Value-based priority
ek
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
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)
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
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
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.