agile war stories sneak preview - wolfgang hilpert - "und sie bewegt sich doch"
TRANSCRIPT
Agile War Stories
„Und sie bewegt sich doch“
m it B e i t räge n vonNico las Dü rr & Vo lke r Same s ke
Von Hindernissen und Fallstricken auf dem Weg zur agilen Transformation eines über 3
Kontinente verteilten Produktentwicklungsteams
Wolfgang HilpertAg i le Café – Dü s s e ld or f
27 . Se pte mb e r 2017
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 1
Speaker Background – Wolfgang Hilpert
Product & Technology Leader in various roles◦ Chief Technology Officer, Head of Engineering / Software Development, Chief Product Owner
◦ @ startup, mid-size and industry leading ISVs incl. IBM, MSFT, SAP
◦ Entire product life cycle from idea on drawing board, design, development, market introduction & adoption
◦ Within plan-driven & agile product development environments
Initiated and led several lean & agile transformations◦ @ SAP (Netweaver), @ AGT International, @ Sophos (NSG)
◦ Product owner, Scrum master, scaled agile (SAFe)
◦ Established cross-functions for User eXperience, Quality Management & Engineering Excellence, Product Line Architecture and Program Management
Personal◦ Husband & father of 2 children (19 & 15 years old)
◦ Football player, runner (HM), cross-country skier
www.linkedin.com/in/whilpert
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 2
KontextDie Produktentwicklung eines Teams mit über 200 Entwicklern an 5 weltweit verteilten Standorten musste so organisiert werden, dass ein Softwareprodukt mit einer ganzen Reihe von funktionalen und vor allem signifikanten qualitativen Verbesserungen am gleichen Tag ausgeliefert werden konnte.
In diesem Vortrag stellen wir vor, welche Techniken und Konzepte angewendet wurden, um die agile Transformation und die Skalierung agiler Methoden bei der einem mittelständischen, international verteilt operierenden Unternehmen voranzutreiben. Wir diskutieren Herausforderungen, die sich dabei stellten, und Maßnahmen, die dagegen ergriffen wurden.
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 3
Scrum Teams and Lab Locations
Vancouver (CA) Budapest (HU)
Karlsruhe (DE)
Bangalore (IN)
Ahmedabad (IN)
• >200 Engineers in 5 locations• Different cultures – region &
company• Diverse skills, processes, tools
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 4
Predictibility Issues – version beforeCase – Timeline: Lack of Predictability
◦ v1 required 35% more time than initially planned
◦ Long path towards Concept Commit
◦ More time spent for stabilization than for development
Reality
Plan
Planning
Development
Hardening
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 5
Some War Stories➢Which level of support does the agile transformation need?
➢Scaling agile methods – yes! However, based on which framework?
➢How does an 18-months product roadmap fit into an agile project plan
➢How do agile Scrum product owner and a product management organization fit together?
➢How can the agile transformation of global organizations distributed across locations, timezones & cultures be successful?
➢Is the application of agile methods a necessary or sufficient condition for a successful product development?
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 6
Ausgewählte „War Stories“➢Auf welcher Ebene muss eine agile Transformation abstützt werden?
➢Skalierung agiler Methoden ➢Ja, aber mit welchem Framework?
➢„Scrum hurts. Really?“ ➢Metriken & Transparenz helfen, die vorhandene Situation und Entwicklungen sichtbar zu machen
➢Wie passt eine 18-monatige Product Roadmap zur agilen Projektplanung?
➢Wie passen Scrum Product Owner und Product Manager zusammen?
➢Wie kann die agile Transformation über weltweit verteilte Standorte und unterschiedliche Kulturenüberhaupt gelingen?
➢Ist die Anwendung agiler Methoden notwendige oder hinreichende Bedingung für eine erfolgreiche Produktentwicklung?
➢Doing agile vs. being agile
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 7
Buy-in for Agile Transformation on all levels
Leadership provides the frame for the transition
Teams own the execution
Agile Development
Agile Support
Development Level
Management Level
Executive Level
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 8
Buy-in for Agile Transformation on all levels
◦ Some teams delayed their agile transformation
◦ Historical reasons
◦ Interface issues
◦ Resistance to adoption
◦ This hurts a lot:
◦ Yet we were able to generate important insights.
◦ We discussed it, we decided to improve in collaboration between teams and alligned all teams to an agile approach.
◦ This takes time. Respect that and don‘t force people.
June 2016
Agile Development
Agile Support
Development Level
Management Level
Executive Level
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 9
Foster new experiences and change will happen
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 10
Boundary Conditions
11
Don‘t disrupt agile transformation◦ Transparency -> Burn up chart of accomplished product increment
◦ Quality -> early tests, significantly reduce defects previous vs. next rel.
◦ Predictability -> 4 months delay vs. 2 weeks (previous vs. next release)
◦ Stay true to core agile principle, e.g. ◦ Magic triangle, commit only based on estimates provided by the engineers
◦ Still a lot of runway for improvement (TA, UT, etc.)
Provide visibility of roadmap for annual business planning◦ Visibility into 12 months vs. 3 months
Quality = f ( S / R / T mix)
Resource Time
Scope
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT.
Ausgewählte „War Stories“➢Auf welcher Ebene muss eine agile Transformation abstützt werden?
➢Skalierung agiler Methoden ➢Ja, aber mit welchem Framework?
➢„Scrum hurts. Really?“ ➢Metriken & Transparenz helfen, die vorhandene Situation und Entwicklungen sichtbar zu machen
➢Wie passt eine 18-monatige Product Roadmap zur agilen Projektplanung?
➢Wie passen Scrum Product Owner und Product Manager zusammen?
➢Wie kann die agile Transformation über weltweit verteilte Standorte und unterschiedliche Kulturenüberhaupt gelingen?
➢Ist die Anwendung agiler Methoden notwendige oder hinreichende Bedingung für eine erfolgreiche Produktentwicklung?
➢„Doing agile“ vs. „being agile“
Voraussichtliche Themen meines Vortrags beim
Scrum Deutschland 2017am 17.November 2017
https://www.prowareness.de/agenda-scrum-deutschland-2017/
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 12
Doing Agile vs. Being AgileKanban boards, daily scrums, sprints Agile mindset, intent-based Management
„Scrum, BUT …“
„Cargo Cult Agile“
~20% Benefit
▪Some ability to adapt to changing priorities
▪Improved visibility, communication
▪Increased productivity
▪Early tests, better transparency of realistic quality status, improved quality
▪Reduced risk
„Joy at work“ „#1 workplace“
„delighted customers“
~200%+ Benefit
▪Customer delight
▪Joy at work, Employee Engagement
▪Innovation, creativity
▪Leadership at all levels
▪Continuous learning
Practices ≠ Mindset
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT. 13
Doing Agile ≠ Being Agile
14
Don’t ‘Do’ Agile. Be Agile!–Alan Kelly
Stop ‘Doing Agile’. Start ‘Being Agile’!
–Jim Highsmith
How to get to being agile? • Good agile practices that are necessary, but
not sufficient.• Early indicator for being agile:
Truly empowered product owner(s) Long, thorny journey; will hurt, needs coaching
Doing AgileExecuting the practices as closely as possible to “as prescribed” description, and trying to “inspect and adapt” to remove impediments to achieving the “as prescribed” execution.
Being AgileInternalizing the mindset, values, and principlesthen applying the right practices and tailoring them to different situations as they arise.
27.09.2017 © COPYRIGHT 2017 WOLFGANG HILPERT.