1. Introduction
1.1. nicknames
1.1.1. Shanban
1.1.2. Kanban boy
1.1.3. Bruce
1.1.4. Krusher
1.2. previous lives
1.2.1. researcher
1.2.1.1. MDD
1.2.1.1.1. publications
1.2.2. small startup: online gaming and AI (Snowie)
1.2.2.1. developer
1.2.2.2. team lead/project manager
1.2.3. business school
1.2.3.1. team lead/project manager
1.2.4. startup focused on a single product (Nexthink)
1.2.4.1. scrum master / agile coach
1.2.5. Suncorp
1.2.5.1. agile coach
1.3. agile heretic
1.3.1. history
1.3.2. assumptions
1.3.3. mindset
1.4. favourite quotes
1.4.1. top 3
1.4.1.1. "If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea.”
1.4.1.1.1. Antoine de Saint-Exupéry
1.4.1.2. The brick walls are there for a reason. The brick walls are not there to keep us out. The brick walls are there to give us a chance to show how badly we want something. Because the brick walls are there to stop the people who don’t want it badly enough. They’re there to stop the other people
1.4.1.2.1. Randy Pausch
1.4.1.3. "A journey of a thousand miles starts with a single step"
1.4.1.3.1. Lao Tzu
1.4.2. runners up
1.4.2.1. "Teams today are all too often feature factories, with little regard for whether the features actually solve business problems."
1.4.2.1.1. Marty Cagan
1.4.2.2. “It’s not the customer’s job to know what they want."
1.4.2.2.1. Steve Jobs
1.4.2.3. "Scope doesn’t creep; understanding grows"
1.4.2.3.1. Jeff Patton
1.4.2.4. “It ain’t what you don’t know that gets you into trouble. It’s what you know for sure that just ain’t so.”
1.4.2.5. Engineering isn't about perfect solutions; it's about doing the best you can with limited resources.
1.4.2.5.1. Randy Pausch
1.4.2.6. “In product development, our greatest waste is not unproductive engineers, but work products sitting idle in process queues.”
1.4.2.6.1. Donald G. Reinertsen
1.4.2.7. “You have to decide what your highest priorities are and have the courage pleasantly, smilingly, and non-apologetically — to say “no” to other things. And the way to do that is by having a bigger yes burning inside.”
1.4.2.7.1. Stephen Covey
1.4.2.8. There will always be more good ideas than you have the capacity to execute
1.5. my responsibilities at WM
1.5.1. my mandate
1.5.1.1. support project delivery from scoping stage onwards
1.5.1.2. define a roadmap for improving project delivery capability and way of working
1.5.1.2.1. understand the gaps
1.5.1.2.2. propose a model for scaling the operating model towards world domination
1.5.1.2.3. examples
1.5.1.3. propose training/coaching opportunities
1.5.2. what I would like to be renowned for:
1.5.2.1. help increase the capability of the groups to solve their own problems
1.5.2.1.1. => I don't want to be the bottleneck
1.5.2.2. support the groups and help them remove blockers/impediments from their way
1.5.2.3. ensure work flows swiftly through delivery
1.5.2.4. making our customers awesome
2. Vision "The North Star"
2.1. i.e., what does the 'endless immensity of the sea' look like?
2.2. We make our customers awesome
2.2.1. our customers treat us as trusted advisers
2.2.1.1. For example:
2.2.1.1.1. rather than asking us:
2.2.1.1.2. we are sufficiently trusted so that WE can ask them:
2.2.1.2. This means:
2.2.1.2.1. we are trusted to deliver to our commitments
2.2.1.2.2. we maximise the amount of work NOT done by spending much less time:
2.2.1.2.3. we are not just a service provider, but we co-create a solution with our customer that is significantly more valuable than their initial idea
2.3. Each group:
2.3.1. has fun
2.3.1.1. 'I want to' versus 'I have to' outlook
2.3.2. works at a sustainable pace
2.3.3. shares ownership of the customer outcomes
2.3.4. understands their capacity
2.3.4.1. for capacity planning
2.3.5. visualises their work
2.3.5.1. progress, setbacks, unvalidated decisions/risks, etc.
2.3.6. limits their Work In Progress (WIP)
2.3.6.1. Not doing too many things to be effective
2.3.7. seeks to maximise their learning
2.3.7.1. My belief:
2.3.7.1.1. the speed with which you learn is the BIGGEST constraint in projects
2.3.7.2. Thought experiment:
2.3.7.2.1. if you go to end of a project and 'start again' how long would it take you to do it again?
2.3.7.2.2. Studies show 1/4 to 1/2 time
2.3.8. has a capability development and recovery plan
2.3.8.1. has a plan to grow their capability
2.3.8.2. has a plan B and C for mitigating single points of knowledge/capability
2.3.9. contributes to making our codebots platform awesome
2.3.10. embraces a craft ethic around technical excellence
2.3.11. pursue high quality through pride of workmanship
2.3.12. looks to move towards a continuous delivery model
2.3.12.1. increased capability according to 4 metrics
2.3.12.1.1. deployment frequency
2.3.12.1.2. lead time for changes
2.3.12.1.3. mean time to fix bug
2.3.12.1.4. change failure rate
2.4. The team:
2.4.1. celebrates it's successes and it's learnings
2.4.2. has plenty of opportunities to learn from each other
2.4.3. makes fact-based decisions
2.4.3.1. actionable metrics to support decision making
2.5. Individuals
2.5.1. care and collaborate deeply
2.5.1.1. ask for help
2.5.1.2. seek to help
2.5.2. are willing to take small steps and seek feedback
2.5.2.1. in the spirit of:
2.5.2.1.1. incremental and iterative delivery
2.5.2.1.2. and creating the simplest possible thing that works
2.5.3. are adaptable
2.5.4. willing to work outside their core expertise as part of a group