2016 Agility at Scale Survey Results
There are several interesting observations from this survey:
- Not all agile teams are small. As you can see in Figure 1, roughly half (48%) of agile teams are more than 10 people in size and one-quarter are more than 20 people in size.
Please see our detailed discussion around How Large are Agile Teams in Practice? on the Disciplined Agile blog.
- Few agile teams are co-located. As you can see in Figure 2, 71% of agile teams are geographically distributed in some manner.
- Few agile teams are truly whole. As you can see in Figure 3, agile teams commonly collaborate with teams external to them. In fact, 96% of agile delivery teams do so.
- Agile teams rarely get the simple problems. As you can see in Figure 4, Only 22% of agile teams are taking on a straightforward problem domain or are pilot teams.
- Most agile teams work in a compliance environment. As you can see in Figure 5, Two-thirds of agile teams face either regulatory compliance (i.e. PCI, FDA) or organizational compliance (i.e. CMMI, ISO 900x).
- Most agile teams work in technically complex situations. 93% of agile teams have to deal with one or more technical complexities. And as you can see in Figure 6, 87% of agile teams are dealing with technical debt in some manner.
- Some agile teams are working in outsourcing situations. As you can see in Figure 7, 17% of agile teams are involved with outsourcing.
- Half of agile teams have team members from other organizations. As you can see in Figure 7, 52% of agile teams are have either consultants or contractors as team members.
- The majority of agile teams deal with some form of governance. 64% of agile teams interact with a governance team/body, steering committee, or PMO (see Figure 3).
Figure 1. Agile team sizes.
Figure 2. Geographic distribution within agile teams.
Figure 3. Who do agile teams work with in practice?
Figure 4. Domain complexity and agile teams.
Figure 5. Regulatory compliance and agile teams.
Figure 6. Technical debt and agile teams.
Figure 7. Organization distribution and agile teams.
You may use this data
as you see fit, but may not sell it in whole or in part.
You may publish summaries of the findings, but if you do
so you must reference the survey accordingly (include
the name and the URL to this page). Feel free to
with questions. Better yet, if you publish,
please let me know so I can link to your work.
- This survey suffers from the
fundamental challenges faced by all surveys.
Why Share This Much Information?
I'm sharing the results, and in particular the source data, of my surveys for
- Other people can do a much better job of analysis than I can. If
they publish online, I am more than happy to include links to their
- Once I've published my column summarizing the data in DDJ, I really
don't have any reason not to share the information.
- I think that it's a good thing to do and I invite others to do the same.