![\"scaling-agile-xpconf2015\"](\"https:\/\/caroli.org\/en\/wp-content\/uploads\/sites\/5\/2015\/06\/scaling-agile-xpconf2015.jpg\")
<\/a><\/p>\nJutta Eckstein<\/a>, the workshop presenter, the great Charlie Poole<\/a> 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?<\/p>\n <\/p>\n 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.<\/p>\n <\/p>\n Charlie suggested a better term would be: Broadening Agile.<\/p>\n <\/p>\n 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.<\/p>\n <\/p>\n 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.<\/p>\n <\/p>\n What were we (these agile folks–including myself) doing? Scaling Agile? Broadening Agile?<\/p>\n <\/p>\n After reflecting on my present and past engagements, and rethinking the terms, I suggest the following terms: (1) deepening<\/strong> agile, (2) scaling<\/strong> agile, and (3) broadening<\/strong> agile.<\/p>\n <\/p>\n These three terms describe different aspects on applying agile on large organizations. Below, I will give one example for each of these terms.<\/p>\n <\/p>\n deepening agile<\/p><\/div>\n 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<\/strong> their knowledge on XP agile practices.<\/p>\n <\/p>\n scaling agile<\/p><\/div>\n 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<\/strong> it, making it work for to the whole programme of work.<\/p>\n <\/p>\n broadening agile<\/p><\/div>\n 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<\/strong> it towards the whole organization, and its partners.<\/p>\n Scaling, Deepening and Broadening Agile https:\/\/t.co\/Hb8cBRRf7s<\/a><\/p>\n \u2014 Paulo Caroli (@paulocaroli) August 11, 2016<\/a><\/p><\/blockquote>\n<\/a><\/a><\/a>\n