10 Phrases That Can Derail an Agile Project

Presentation abstract

“Communication”. Though not mentioned by name in the Agile Manifesto, it is its corner stone. The more we communicate, we’re bound to succeed. Yet nobody teaches us how to do it well.

Think of how “It will be done when it’s done” sounds to a product owner (hint: the developers don’t know what they are doing). Or what the team hears when the test manager states that “We need 100% coverage” (hint: she doesn’t understand anything about development).

In this session, I’ll talk about how innocent phrases, thrown around casually, can have a devastating effect on agile projects. I’m going to discuss where these phrases come from, and how they can easily be misinterpreted and the effect they can have on a project, from mild cynicism to utter distrust.

You don’t want that, do you?
Then come to the session and learn what NOT to say, how to react effectively to these phrases, and keep your project on track.

About the speaker – Gil Zilberfeld

Gil Zilberfeld has been in software since childhood, starting out with Logo turtles. With more than15 years of developing commercial software, he has vast experience in software methodology and practices.
Gil is the product manager at Typemock, working as part of an agile team in an agile company, creating tools for agile developers. He promotes unit testing and other design practices, down–to–earth agile methods, and some incredibly cool tools. Gil presented locally and abroad about unit testing, TDD, and agile practices. And in his spare time he shoots zombies, for fun.
Gil blogs at http:⁄⁄www.gilzilberfeld.com on different agile topics, including processes, communication and unit testing. He also writes at the Typemock blog and presents locally and abroad on these topics.


Subscribe to get updates from practical agile