What makes some IT projects succeed while others fail? Alistair Cockburn says it all boils down to three behaviors: “Those that were co-locating face to face, (with) short delivery cycles, (and) access to customers were delivering.” Since Agile software development methodologies encourage all three of these behaviors, it makes sense that many Agile teams are more successful than those that use other development techniques.
So how do you convince your team to give Agile techniques a try? Steve Rogalsky suggests six “influence strategies”:
- Make the Undesirable Desirable (Personal Motivation)
- Surpass Your Limits (Personal Ability)
- Harness Peer Pressures (Social Motivation)
- Find Strength in Numbers (Social Ability)
- Design Rewards and Demand Accountability (Structural Motivation)
- Change the Environment (Structural Ability)