Being Agile and Seeing Big Picture
- 1. being Agile and seeing the Alex Leonov alex@knowledgelab.nz @alexanderleonov
- 2. Agile Operations • granular • many data points • fast moving
- 3. Big Picture • multiple channels • portfolio of projects • strategic and tactical needs
- 6. 2 4 6 8 10 12 14 2 4 6 8 10 12 14 16 18 20 2 4 6 8 10 12 14 2 4 6 8 10 12 14 16 18 20 2 4 6 8 10 12 14 2 4 6 8 10 12 14 16 18 20 2 4 6 8 10 12 14 2 4 6 8 10 12 14 16 18 20 In this example statistics are the same for all 4 data sets: Mean of x Sample variance of x Mean of y Sample variance of y Correlation between x & y Linear regression line Now imagine taking action based on these statistics!
- 7. A WIZARD IS NEVER LATE TOO BAD YOU’RE NOT A WIZARD
- 8. The Challenge: be flexible and fast with attention to detail while keeping a perspective * and not collapsing of overload
- 9. The Solution (principles to follow)
- 11. 1. Traceability 2. Disintermediation 3. Realtime Feedback
- 12. 1. Traceability
- 23. All these are connected, and you can move seamlessly between the levels of detail, from Big Picture to my favourite cafe
- 26. Let’s imagine that parking is a problem (if you’ve been there on Saturday morning, you’d know it’s true anyway)
- 27. just 3 car parks at the entrance parking near shops in Ponsonby need more parking in Auckland build new CBD parking building will it help the original problem?
- 31. Just show the places to park to the visitors (on the website, in the booklet, etc.) – it’s a good and quick solution
- 32. 1. Traceability 2. Disintermediation 3. Realtime Feedback
- 33. be flexible and fast with attention to detail while keeping a perspective
- 34. Some Examples
- 35. One view for the Big Picture (perspective) which allows drilling down to any level of detail
- 36. Typical “service request” form that can scare even the most formidable users Notice that it only has one required field!
- 37. This is what the previous form should look like to make life easy for users, improve service levels, and bring about realtime feedback
- 38. Any major ITSM suite can show you relationships between tickets that enable traceability, drilling down, and perspectives Things like “blockers” can also help with realtime feedback
- 39. 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
- 40. 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!
- 42. being Agile and seeing the Alex Leonov alex@knowledgelab.nz @alexanderleonov