My hypothesis is this; Agile at the project level is a focused set of principles and practices defined by movements like XP, Scrum and Lean. When adopting Agile at scale we take teams through a learning journey to teach them these practices and guide them to learn the principles under which they are applied. As these teams start to adopt Agile they will encounter blockers inherent in the culture and legacy process of the enterprise. Therefore Agile at scale is dependent on cultural change, the appetite for change and the degree in which support structures such as HR, Legal, Finance, Procurement and Vendor Management engage and adapt.
With that, welcome to my blog.
A blog on Agile led cultural change, Agile leadership, Agile scaling and general organisational transformation.
As an entree here is a bit of a learning journey that I have found useful. No doubt you all have other ideas to add and I would be happy to get your input on it as Im sure I will add to it along the way…. use it, or not!!
- The Principles of Product Development Flow: Second Generation Lean Product Development – Donald G. Reinertsen
- Agile Requirements – Dean Leffingwell
- The Lean Start Up – Eric Ries
- Kanban and Scrum – making the most of both – Henrik Kniberg and Mattias Skari
- British Telecom Agile Journey – http://www.methodsandtools.com/archive/archive.php?id=43
- Adaptive Leadership – Accelerating enterprise agility – Jim Highsmith
- Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation – Humble, Farley
- New New Product Development Game – Takeuchi, Nonaka
- DTE – Aligning Portfolio Case Study – ThomasBaker-EstablishAgilePortfolio-Paper
- Escaping Velocity – Moore
- Have an understanding of:
- Personal Kanban
- Continuous Delivery
- Adaptive Leadership
- Rolling Wave Planning
- Dan Pink – AMP
- Ritual Dissent – Cognitive Edge
- Validated Learning