A series of cartoons depicts the terrible things that happen when agile practices aren’t followed. This session is valid for any persona, but especially for the product owner who will suffer when their product fails because they follow a process that isn’t helping their team deliver!

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.

As Agile practitioners, a great deal of our time is focused on having targeted, directed impact. But sometimes we miss opportunities to repurpose our efforts into syngergistic, many-pronged effects. Not multi-tasking — multi-EFFECTing, from one piece of effort. This talk will explore this topic, both in theory and in practice. We will examine a particular client case-study, where two disparate 6-person developer teams, with minimal pairing and TDD experience, were developed into highly-productive “gelled” teams, through “Group Pair Programming” — 6 individuals, 1 workstation.

This talk focuses around a series of diagrams that help explain how various practices work.

Many practices work to different degrees of success depending on exactly how they’re implemented. We’ll discuss why this is so, with examples of multiple ways to do pair programming, testing, and planning. Along the way, we’ll show some new work: how to get a better plan by not estimating, models to identify which practices to experiment on, and how to find what to vary.

Each concept will be explained with diagrams that get to the gist of the practice - and methods of thinking about variations.