being agile and seeing big picture

42
being Agile and seeing the Big Picture Alex Leonov [email protected] @alexanderleonov

Upload: alex-leonov

Post on 25-Jan-2017

619 views

Category:

Services


3 download

TRANSCRIPT

Page 1: Being Agile and Seeing Big Picture

beingAgile

and seeing theBig Picture

Alex [email protected]

@alexanderleonov

Page 2: Being Agile and Seeing Big Picture

Agile Operations• granular• many data points• fast moving

Page 3: Being Agile and Seeing Big Picture

Big Picture• multiple channels• portfolio of projects• strategic and tactical needs

Page 4: Being Agile and Seeing Big Picture

The Challenge

Page 5: Being Agile and Seeing Big Picture

FEELING OVERWHELMED?There is a lot of action

at the level of agile teamswhich clutters the perspective

Page 6: Being Agile and Seeing Big Picture

2 4 6 8 10 12 14 16 18 202

4

6

8

10

12

14

2 4 6 8 10 12 14 16 18 202

4

6

8

10

12

14

2 4 6 8 10 12 14 16 18 202

4

6

8

10

12

14

2 4 6 8 10 12 14 16 18 202

4

6

8

10

12

14FAILIn this examplestatistics arethe same for all4 data sets:Mean of xSample variance of xMean of ySample variance of yCorrelation between x & yLinear regression line

Now imaginetaking actionbased on thesestatistics!

Page 7: Being Agile and Seeing Big Picture

A WIZARD IS NEVER LATE

TOO BAD YOU’RE NOT A WIZARD

By the time lessons learntor other forms of feedback are due

it is too late to act anyway

Page 8: Being Agile and Seeing Big Picture

The Challenge:

be flexible and fastwith attention to detail

while keeping a perspective* and not collapsing of overload

Page 9: Being Agile and Seeing Big Picture

The Solution(principles to follow)

Page 10: Being Agile and Seeing Big Picture

WHYtrumps

HOW

Page 11: Being Agile and Seeing Big Picture

1. Traceability2. Disintermediation3. Realtime Feedback

Page 12: Being Agile and Seeing Big Picture

1. Traceability

Page 13: Being Agile and Seeing Big Picture
Page 14: Being Agile and Seeing Big Picture
Page 15: Being Agile and Seeing Big Picture
Page 16: Being Agile and Seeing Big Picture
Page 17: Being Agile and Seeing Big Picture
Page 18: Being Agile and Seeing Big Picture
Page 19: Being Agile and Seeing Big Picture
Page 20: Being Agile and Seeing Big Picture
Page 21: Being Agile and Seeing Big Picture
Page 22: Being Agile and Seeing Big Picture
Page 23: Being Agile and Seeing Big Picture

All these are connected, and you can move seamlessly between the levels of detail, from Big Picture to my favourite cafe

Page 24: Being Agile and Seeing Big Picture

2. Disintermediation

Page 25: Being Agile and Seeing Big Picture
Page 26: Being Agile and Seeing Big Picture

Let’s imagine that parking is a problem(if you’ve been there on Saturday morning,

you’d know it’s true anyway)

Page 27: Being Agile and Seeing Big Picture

just 3 car parks at the entranceparking near shops in Ponsonby

need more parking in Aucklandbuild new CBD parking building

will it help the original problem?

Page 28: Being Agile and Seeing Big Picture

3. Realtime Feedback

Page 29: Being Agile and Seeing Big Picture
Page 30: Being Agile and Seeing Big Picture
Page 31: Being Agile and Seeing Big Picture

Just show the places to park to the visitors (on the website, in the booklet, etc.) – it’s a good and quick solution

Page 32: Being Agile and Seeing Big Picture

1. Traceability2. Disintermediation3. Realtime Feedback

Page 33: Being Agile and Seeing Big Picture

be flexible and fastwith attention to detail

while keeping a perspective

Page 34: Being Agile and Seeing Big Picture

Some Examples

Page 35: Being Agile and Seeing Big Picture

One view for theBig Picture (perspective)which allows drilling downto any level of detail

Page 36: Being Agile and Seeing Big Picture

Typical “service request”form that can scare eventhe most formidableusers

Notice that it only hasone required field!

Page 37: Being Agile and Seeing Big Picture

This is what the previousform should look liketo make life easy for users,improve service levels,and bring about realtimefeedback

Page 38: Being Agile and Seeing Big Picture

Any major ITSM suite canshow you relationshipsbetween tickets thatenable traceability, drillingdown, and perspectives

Things like “blockers” canalso help withrealtime feedback

Page 39: Being Agile and Seeing Big Picture

Typical Problems• weak signals lost due to aggregation• interpretation changes the message• too hard to use -> loopholes• too slow to change -> stagnation• incomprehensible from the outside• micromanagement

Page 40: Being Agile and Seeing Big Picture

Implementation Tips• use familiar tools• ease of use over universality• react to exceptions quickly• don’t over-constrain or over-protect• no “why” – no “go”• experiment!

Page 41: Being Agile and Seeing Big Picture

WHYtrumps

HOW

Page 42: Being Agile and Seeing Big Picture

beingAgile

and seeing theBig Picture

Alex [email protected]@alexanderleonov