ten tips to know if your agile team isn't really agile
Alistair Cockburn offers these ten tips to know if your agile team isn't really agile:
- The team is co-located, but people are not sitting within the length of a school bus to each other.
- They’re distributed, and there is an absence of microphones and webcams and one or two meetings a day.
- They have not delivered anything to real users in the last three months. Some of my agile friends would say that’s much too long, but I’m being generous there.
- If no user has seen real running software inside the last month.
- They don’t have the output of last month’s reflection workshop or retrospective on the wall.
- They don’t have fully automated unit tests, and a large number of acceptance tests aren’t automated.
- They’re not having a build integration at least once day. Good groups do it every half hour; there are groups that get away with it every other day.
- They write big requirements documents, and they don’t know how to split those up into smaller pieces so they could deliver a piece of software every month.
- They have itty-bitty requirements on the order of “here’s what happens when you click here,” but they don’t have long-term vision for what they’re trying to accomplish.
- People keep saying, “It’s not my job.” One of the things about proper agile development is that there is group accountability for results. Very specifically, if the requirements are not coming in fast enough, whoever has a bit of spare time (programmers, testers, etc.) drops what they’re doing and helps gather requirements; if tests aren’t getting done, people with some spare capacity help test and so on.
Want to learn more about product management in an agile world? Go to Pragmatic Institute's Living in an Agile World resources.
Looking for the latest in product and data science? Get our articles, webinars and podcasts.