1. They’re not comfortable with change.
2. They don’t feel their voices are being heard over those of the development team.
3. They, or someone they know, didn’t get what they wanted in an agile development project.
4. Documentation is the go-to method for butt-covering, and lean requirements make them feel exposed.
5. They’ve learned to anticipate emergencies on release days due to poor version control.
6. Real-time decisioning is inconvenient when paired with all-day conference calls, wall-to-wall meetings and heavy travel schedules.
7. They’ve been preached at by a well-meaning Agile zealot.
8. They’ve afraid it’s flavor-of-the-month, like other “revolutionary” new processes that blazed in and sputtered out over the years.
9. They’ve lost faith in the backlog – it’s the place projects go to live with Jesus.
10. They think “collaboration” is Latin for “I don’t get to drive”.