|

Scaling, Deepening and Broadening Agile

Last week I was on the scaling agile workshop at the amazing XPConf 2015 at Helsinki.

scaling-agile-xpconf2015

Jutta Eckstein, the workshop presenter, the great Charlie Poole along with all workshop participants had a quick and great conversation about the term: scaling agile. Are we talking about the same thing? Is scaling the right word for it?

 

All workshop participants shared a little about their experiences and expectations on scaling agile. It was clear to me that many of us mean different things when we say scaling agile.

 

Charlie suggested a better term would be: Broadening Agile.

 

Broadening Agile. I loved it! I related to the term right away. It is exactly what I am doing on a client at the moment: I am getting lean and agile principles and practices from the IT department and broadening it towards the whole (large) organization.

 

Today, one day after the workshop, I stopped to reflect about the terms again. It means different things for different people. Perhaps thinking about myself over the past ten years, and the different (large) organizations I was either sharing or applying agile and lean concepts and practices.

 

What were we (these agile folks–including myself) doing? Scaling Agile? Broadening Agile?

 

After reflecting on my present and past engagements, and rethinking the terms, I suggest the following terms: (1) deepening agile, (2) scaling agile, and (3) broadening agile.

 

These three terms describe different aspects on applying agile on large organizations. Below, I will give one example for each of these terms.

 

deepening agile

deepening agile

In 2006 I was working on a small agile team in a large organization. As a developer / agile coach I was helping that team with TDD, mock objects and script automation. The team was deepening their knowledge on XP agile practices.

 

scaling agile

scaling agile

In 2009 I was working on a organization as a team manager (one out of ten team managers) on a programme of 200 engineers, 10 teams, all working on the same code base, on a coordinated, orchestrated and synchronized release cycle. It is important to say that the programme of work started in 2007 with one Scrum team of ten people following XP practices such as TDD and Continuous Integration. The team (s) grew over time along with its growing challenges. On those years we were getting what worked for agile teams and tried scaling it, making it work for to the whole programme of work.

 

broadening agile

broadening agile

Currently (2014-2015), I have been working on a large organization (200 projects, involving 4000 people from several departments and third party companies) on a organizational transformation strategic project. On this project an experienced group of people are looking at improving the time to market for the organization portfolio. For doing so we did some work on the IT department related to software delivery, and a lot of work with the other departments, such as PMO, legal, procurement, finance, HR and recruiting. We have also been working with the third party companies. The team is getting lean and agile principles and practices from the IT department and broadening it towards the whole organization, and its partners.

Paulo Caroli

Paulo Caroli is the author of the best-selling book “Lean Inception: How to Align People and Build the Right Product” (the first on a series of books about Lean Strategy and Delivery). He's also the creator of FunRetrospectives.com , a site and book about retrospectives, futurospectives and team building activities. Caroli writes on this blog frequently. Receive the next post in your email. Sign up here .
Triple Track Development: Business Innovation Through Continuous Discovery and Continuous Delivery

Triple Track Development: Business Innovation Through Continuous Discovery and Continuous Delivery

Continuous Triple Track Development, comprising Business Strategy, Discovery, and Delivery, revolutionizes product development. Quarterly goals replace yearly plans, ensuring adaptability. Continuous Discovery delves deep into user needs, while Continuous Delivery swiftly transforms validated ideas into products. This synchronized approach fosters unprecedented collaboration, propelling teams towards collective success. It’s not just a methodology; it’s a strategic advantage, enabling businesses to innovate rapidly in today’s dynamic market.

read more
New Book Alert: How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas

New Book Alert: How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas

Introducing our enhanced book, “How to Define, Prioritize and Refine User Stories using the Product Backlog Building Canvas.” Evolving from its predecessor, this edition responds to valuable reader feedback, refining both content and title. Delve into the world of effective product development and user story management, discovering the integrated power of the PBB Canvas. Embrace an enriched reading experience and explore insights from thought leader Jeff Gothelf in the preface. Don’t miss a reader’s insightful review, preserved for wider readership. Join us on this journey of empowering user story craftsmanship, and witness the transformation of your product development goals.

read more
Product thinking strategy questionnaire

Product thinking strategy questionnaire

The questionnaire below elaborates on a few important aspects of product thinking, problem understanding, solutioning and strategic delivery planning.   I have used this questionnaire as part of a workshop on Product Leadership and Strategic Alignment. Basically,...

read more

Pin It on Pinterest