Slide 1

Slide 1 text

@devpg Agile Enterprise War Stories André Neubauer, JAX 2014, Mainz

Slide 2

Slide 2 text

@devpg Preamble No blaming - Just reviews & learnings! Respect - Without the effort to gain agility, there would be no war stories! Don’t repeat - This is not a blueprint, but only my experiences!

Slide 3

Slide 3 text

@devpg About me “Software engineering enthusiast. Moved to the dark side. Now executive and strong advocate on lean leadership. Totally motivated by 'Y'. Loving startup culture.“ @devpg

Slide 4

Slide 4 text

@devpg Agility “My understanding of #agility isn't an efficient IT department but an effective overall organisation!“ @devpg → Process, Structure, Culture!

Slide 5

Slide 5 text

@devpg The Need For Enterprise Agility Welcome to the post-industrial age! “Companies are really being driven by the need for change and innovation instead of doing the same thing year after year better. [...] Companies are having to change from a focus on stability to a focus on being able to change very quickly. [...] What these companies need is to tighten the feedback loop to understand where the market is going.” (Jeff Sussna, WJAX 2013)

Slide 6

Slide 6 text

@devpg Context ●  External ●  Waterfall ●  Bonn ●  E-POSTBRIEF ➔ Internal (with external support) ➔ Scrum ➔ Berlin ➔ E-POST

Slide 7

Slide 7 text

@devpg #12 Stories

Slide 8

Slide 8 text

@devpg #1 Degraded by Scrum

Slide 9

Slide 9 text

@devpg Degraded by Scrum Examples: ●  “I’m just a Scrum Developer.” (former team leader) ●  Impediments needs to be approved by management! → Management by control is no longer needed!

Slide 10

Slide 10 text

@devpg Degraded by Scrum Learning: You have to have a clear view on what‘s the future purpose of management!

Slide 11

Slide 11 text

@devpg #2 Stakeholder Overflow

Slide 12

Slide 12 text

@devpg Stakeholder Overflow Stakeholder: Als Stakeholder [ˈsteɪkhoʊldɐ] (engl. ‚Teilhaber‘)[1] wird eine Person oder Gruppe bezeichnet, die ein berechtigtes Interesse am Verlauf oder Ergebnis eines Prozesses oder Projektes hat.

Slide 13

Slide 13 text

@devpg Stakeholder Overflow Situation: ●  Experts advicing from the outside rather than working in the team ●  Masked as stakeholder Attention: Veto culture! Solution: Put them in the team!

Slide 14

Slide 14 text

@devpg #3 Overwhelmed by Speed of Change

Slide 15

Slide 15 text

@devpg Overwhelmed by Speed of Change Situation: Product changes went live without any notification... Protip: As a product guy you should always be better informed about the product than your boss! ;-)

Slide 16

Slide 16 text

@devpg Overwhelmed by Speed of Change Complication: Information flows are difficult, especially in a matrix organization … Result: Lots of newsletters → Find the fine line between information overload and information deficit!

Slide 17

Slide 17 text

@devpg #4 “People over Process” Meets Internal Audit

Slide 18

Slide 18 text

@devpg Source: http://www.sonypictures.com/movies/meninblack3/

Slide 19

Slide 19 text

@devpg Meets Internal Audit People Process over Who has fixed that bug? Me! Who allowed you that? Um … well ...

Slide 20

Slide 20 text

@devpg Meets Internal Audit Context: Doing things right, not doing the right things! Task: Integrate cross-departments (Legal, privacy, ...) People Process over

Slide 21

Slide 21 text

@devpg Meets Internal Audit Attention: Process compliance may limit the assumption of responsibility! Approach: Ensure process complaince in background (by automation) People Process over

Slide 22

Slide 22 text

@devpg #5 Waiting for Big Bang

Slide 23

Slide 23 text

@devpg Waiting for Big Bang “As long as it’s not marketable, I'm not interested.” (VP Product) Lessons learned: Classical businesses often don‘t know the iterative approach. They think in perfect products not in „Beta‘s“.

Slide 24

Slide 24 text

@devpg #6 Scrum as Performance Program for IT

Slide 25

Slide 25 text

@devpg Scrum as Performance Program for IT „We need technical project management to make the teams performing.” → Rapid implementation of big things is needed! Complication: Incremental over Iterative ...

Slide 26

Slide 26 text

@devpg Scrum as Performance Program for IT Attention: Business doesn‘t make advantage of „continuous improvement“! Efficiency is nothing without effectiveness!

Slide 27

Slide 27 text

@devpg #7 Doing The Right Things vs. Doing Things Right

Slide 28

Slide 28 text

@devpg Doing Situation: Strong focus on ●  On time delivery ●  Team utilization Result: Reason for failure: „Doing it wrong“ instead of „Doing the wrong thing“ The Right Things Things Right

Slide 29

Slide 29 text

@devpg #8 The Planning Dilemma

Slide 30

Slide 30 text

@devpg The Planning Dilemma “We needs a detailed roadmap for the next year!” (Department XYZ) Learning: Questioning need! Some are myth ;-) (Some are not ...)

Slide 31

Slide 31 text

@devpg #9 Continuous Reprioritization

Slide 32

Slide 32 text

@devpg Continuous Reprioritization There are always more ideas than teams! Prioritization needed! Situation: Continuous reprioritization in order to realize all projects!

Slide 33

Slide 33 text

@devpg Continuous Reprioritization Learning: Continuous reprioritization leads to standstill! Project A Project B Project C Project D Project A Project B Project C Project D Project A Project B Project C Project D Project A Project B Project C Project D

Slide 34

Slide 34 text

@devpg #10 Avoid Failure, Be Innovative

Slide 35

Slide 35 text

@devpg Avoid Failure, Be Innovative Situation: Classic business try to avoid failure. Most times it‘s part of the company culture. Reason why: Do the same thing year after year better is the core requirement from the industrial age!

Slide 36

Slide 36 text

@devpg Avoid Failure, Be Innovative Result: ●  No learning (because failure don‘t happen) ●  Failure prevention kills your innovativeness But: There is no success without failure!

Slide 37

Slide 37 text

@devpg Avoid Handle Failure ●  Mindset change: Failure → Opportunity ●  Reduce risks by using techniques like interviews, prototypes, …

Slide 38

Slide 38 text

@devpg #11 Passive Product Management

Slide 39

Slide 39 text

@devpg Passive Product Management PM Team(s) C(X)O Sales Marketing BusDev ... Situation: Product management as gateway not creator of the product Complication: Missing product validation

Slide 40

Slide 40 text

@devpg Market-Driven Product Management Business unit C Team(s) Business unit B Team(s) Business unit A Team(s) Passive → Setting-up business units each focussing on a market segment

Slide 41

Slide 41 text

@devpg #12 Product Ownership meets P&L Responsibility

Slide 42

Slide 42 text

@devpg Product Ownership Meets P&L Question: Who owns a product when you have a strong focus on profit and loss? Business owner (BO) or product owner (PO)?

Slide 43

Slide 43 text

@devpg Product Ownership Meets P&L Situation: ●  No independent decisions → Slow decision making processes ●  BO: Overruling... ●  PO: „Stuck between a rock and a hard place“

Slide 44

Slide 44 text

@devpg Product Ownership Meets P&L Approach: ●  Team of responsibilities! (Business & product) ●  Separation of tasks based on e. g. T-shape or mid-/ longterm)

Slide 45

Slide 45 text

@devpg Done!

Slide 46

Slide 46 text

@devpg Learnings ●  Being agile over doing agile! ●  Effectiveness over efficiency! ●  Process, Structure, Culture!

Slide 47

Slide 47 text

@devpg Thanks for your attention! Any questions? Source: http://www.flickr.com/photos/peterjlambert/97671748/sizes/o/in/photostream/