The Ogre and The Wimp: Clever Influencing Tricks - Help the Most Reluctant Teams
What happens when the CIO decides the dev team needs to adopt agile practices and the dev team nods their heads but don’t plan on doing zilch? It is time to leverage those fancy shmancy influencing skills we agilists are so famous for. We’ll cover new fun tactics that have not yet been explored in some of the prevalent literature. All fresh information from the field.
A fun set of slides acts as the backdrop to a series of skits where we playact the proposed influencing techniques with three actors:
the ogre: the voice of authority, can tell the dev team how to work, etc.
the wimp: a dev coach, ocasionally gets the dev team to do the right thing by acting helpless
innocent victim: a member of the dev team who needs to shape up
The techniques: Each technique represents an orchestration between the Ogre and the Wimp to influence the reluctant developer into doing the right thing.
- How to get the “I’m too smart/too busy to write tests” developer to practice TDD
- How to get the “I like to work alone” developer to practice pairing
- How to get the “I only run the build once a month” dev to do it every couple of hours
- How to get the “I only check in code once I’m completely done” dev to practice frequent check-ins
- How to get the “this is my code!” developer to practice shared code ownership
- How to get the “I’m too amazing/ I’m not nearly good enough” developer to change their ways

Add to calendar