Embed Size (px)
DESCRIPTION
View my presentation from 2014s Product Management Festival in Zürich. How my team changed its way to work from Scrum by the book to a more flexible way in between Scrum and Kanban. If you are struggling with the Scrum boundaries of fixed iterations and fixed commitment, here might be some ideas for you how to solve this.
Citation preview
www.autoscout24.de
When Scrum is getting to tight – widen the
framework, gain flexibility. A field report
Product
Management
Festival 2014
Katrin Grothues
Zurich,
17. September 2014
www.autoscout24.de
Who is AutoScout24und who am I?
AutoScout24 – IT IS ALL ABOUT CARS.
More than 2 million new and used cars
17.1 million visitors a year in Germany (WNK, ACTA 2012)
The largest online car marketplace Europe-wide
Over 100,000 used commercial vehicles
More than 10 million people Europe-wide use
AutoScout24 every month
More than 300 million virtual vehicle
inspections per month in Europe
More than 40,000 dealer clients Europe-
wide
More than 100,000 motorcycles
AutoScout24 - Europe
RUS
S
PL
NL
DB
F CH A
HR RO
BG
UA
I
TR
E
CZ
Involved in the markets in 18 countries,
AutoScout24 is the largest online car
marketplace Europe-wide.
AutoScout24 has more than
360 employees throughout
Europe.
A few words about myself
�Born in Marl / Ruhrgebiet
�Since 01/2012: Product Manager Vehicle Market Dealer Products @ AutoScout24
�Before: 3.5 years strategie and projectmanagement at big e-commerce companies
�Education: Cultural Science (M.A.), University of Lüneburg
From Scrum to "Scrumban"| Katrin Grothues
Page 5
What do you get today – and what not?
Page 6
-Introduction to Scrum
Introduction to Kanban
A discussion about the differences
between these methods
Problems
Findings
Actions
Metrics
of my
team
Inspiration for you
From Scrum to "Scrumban"| Katrin Grothues
Scrum by the book – that‘swhere we started
Agile development @ AutoScout24
From Scrum to "Scrumban"| Katrin Grothues
Page 8
PO* PM* Developer QA
Research & User Experience
Design
Agile Coaches
*Productowner / Productmanager
Fixed 2-weekly sprint iterations
From Scrum to "Scrumban"| Katrin Grothues
Page 9
Planning
Estimation
Retro
Estimation
PlanningRetro
Estimation
1. week 2. week 3. week 4. w…
2 week sprint
Planning every 2 weeks ½-1 day
Estimation 1 time per week Retro every 2 weeks
fixed commitment
But we had some problemswith it
1. What fits into the sprint – what not?
From Scrum to "Scrumban"| Katrin Grothues
Page 11
1. Story – 3 SP
2. Story – 1 SP
4. Story – 3 SP
5. Story – 5 SP
6. Story – 1 SP
3. Story – 3 SP
7. Story – 5 SP
2. A lot of waste for preparation
From Scrum to "Scrumban"| Katrin Grothues
Page 12
1. Story – 3 SP
2. Story – 1 SP
4. Story – 3 SP
5. Story – 5 SP
6. Story – 1 SP
3. Story – 3 SP
7. Story – 5 SP
3. Inflexibility
Page 13
1. Story – 3 SP
2. Story – 1 SP
3. Story – 5 SP
4. Story – 1 SP
5. Story – 3 SP
From Scrum to "Scrumban"| Katrin Grothues
4. Long plannings
Page 14
From Scrum to "Scrumban"| Katrin Grothues
5. Time gap between planning and implementation
From Scrum to "Scrumban"| Katrin Grothues
Page 15
Planning PlanningStart Story 3
?
6. Stress in the end
From Scrum to "Scrumban"| Katrin Grothues
Page 16
Planning Planning
Achieve commitment Testing
Design acceptance
Tracking acceptance
PM acceptance
Enough reasons for a change
Commited stories are not driven by priority.
Little flexibility and a lot of waste.
Long planning meetings.
Time gap between planning and implementation.
Difficult to onboard.
Acceptance stress in the end.
From Scrum to "Scrumban"| Katrin Grothues
Page 17
Sometimes you have to leave the ground
Page 18
From Scrum to "Scrumban"| Katrin Grothues
Our Hypothesis
The fixed [2-weekly] iteration is
the problem
Page 20
From Scrum to "Scrumban"| Katrin Grothues
If we do not have fixed sprint iterations…… we‘ll gain flexibility and can keep the priority.
Page 21
1. Story – 3 SP
2. Story – 1 SP
3. Story – 5 SP
4. Story – 1 SP
5. Story – 3 SP
From Scrum to "Scrumban"| Katrin Grothues
Page 22
1. Story – 3 SP
2. Story – 1 SP
3. Story – 5 SP
4. Story – 1 SP
5. Story – 3 SP
From Scrum to "Scrumban"| Katrin Grothues
If we do not have fixed sprint iterations…… we‘ll produce less waste.
Page 23
From Scrum to "Scrumban"| Katrin Grothues
If we do not have fixed sprint iterations…… we‘ll have shorter plannings.
From Scrum to "Scrumban"| Katrin Grothues
Page 24
Planning Planning Planning
Implementation Implementation
!
If we do not have fixed sprint iterations…… implementation will follow directly after planning.
Implementation
From Scrum to "Scrumban"| Katrin Grothues
Page 25
If we do not have fixed sprint iterations…… we‘ll have less acceptance stress.
Planning Planning Planning
Implementation ImplementationImplementation
That‘s how we changed ourschedule
The full picture of our working schedule
From Scrum to "Scrumban"| Katrin Grothues
Page 27
Planning
Estimation
Retro
Estimation
Retro
Estimation
1. week 2. week 3. week 4. w…
No fixed sprint iterationsPlanning on demand
Estimation 1 time per week Retro every 2 weeks
No fixed commitment
Planning Planning
Implementation ImplementationImplementation
Do the changes help us?
If we do not have fixed sprint iterations, priority will determine the sequence.
If we do not have fixed sprint iterations, we‘ll gain flexibility.
If we do not have fixed sprint iterations, we‘ll produce less waste.
If we do not have fixed sprint iterations, we‘ll have shorter plannings.
If we do not have fixed sprint iterations, onboarding will be easier.
If we do not have fixed sprint iterations, we‘ll have less acceptance stress.
From Scrum to "Scrumban"| Katrin Grothues
Page 28
And now, everything‘s fine? Concerns of a PM.
Timing, velocity and organisation
Page 30
From Scrum to "Scrumban"| Katrin Grothues
When do we finish a story?
Page 31
First estimation in planning.
Communication in Daily.
Communication with external stakeholders.
From Scrum to "Scrumban"| Katrin Grothues
Will my team get slow?
Page 32
Measure Leadtime.
PM has to be disciplined.
Devs have to be disciplined.
All tasks have to be put into the backlog –
no inofficial tasks.
Additional Task Lane.
From Scrum to "Scrumban"| Katrin Grothues
How do I organise Planning on Demand?
Page 33
Planning 1 will be shifted to Estimation.
PM takes part in Planning.
All Devs take part in Planning.
The team gets an own room.
Daily planning slot in the morning.
From Scrum to "Scrumban"| Katrin Grothues
Closing notes & take aways
„Scrumban“ solved a lot of problems…
More flexibility and less waste.
Short planning.
Sequence is determined by priority.
Planning is directly followed by implementation.
Easy onboarding.
Less acceptance stress in the end.
From Scrum to "Scrumban"| Katrin Grothues
Page 35
…but it holds new challenges!
Discipline on both PM and Dev side.
Keep an eye on velocity
Communication – internal and external – about Timings.
Meeting organisation.
From Scrum to "Scrumban"| Katrin Grothues
Page 36
!
!!
!
What should you take away?
Page 37
Every process should only support your team. Change the process, if it
constrains you.
„Scrumban“ has a lot of advantages, but also new challenges.
Decide together, if and what to change.
Observe yourself: do the changes support you? If not, change again!
Without discipline in all roles it won‘t work out.
From Scrum to "Scrumban"| Katrin Grothues
Thanks for your attention!
From Scrum to "Scrumban"| Katrin Grothues
Page 38
Contact me
on Xing
https://www.xing.com/profile/Katrin_Grothues
on LinkedIn
http://de.linkedin.com/in/katringrothues
My presentations are available on SlideShare
http://de.slideshare.net/KatrinGrothues
www.autoscout24.de
www.autoscout24.de
Thank you for your
attention!
Kontakt:
AutoScout24 GmbH
Dingolfinger Straße 1-15
81673 München
Katrin Grothues
Fon +49 89 444 56-1159
Fax +49 89 444 56 19-1159
