Abstract/Description

Is your your organization or team moving to the latest software development fad? Learn the art of sabotage!

Learn how to prevent it from succeeding, or to reduce it to the “flavor of the month” so it’s irrelevant in the long term.

We’ll explore seven ways to sabotage the transition, ranging from the over-controlling “Let One Flower Bloom” to the subtle “Muddy the Motives.”

For your safety, we’ll look at how methods' proponents may sneakily try to counteract each sabotage.

Additional Resources

About the Speaker(s)

Tim is a long-time programmer (since 1979), reviewer, speaker, writer. He has been active in many of the big changes in software over the past 36 years (including Design Patterns, Object-Oriented Design, and Agile software development).In addition to his contributions in "Clean Code" and "Agile In A Flash", Tim's articles appeared in the C++ Journal, Pragmatic Bookshelf, InfoQ, CIO, and SmartBear.Tim is one of the crew of experts at Industrial Logic, a premier agile consultancy, eLearning vendor, and thought leader. Here he joins with other industry experts to help people develop the skills that will make them awesome.Tim muses about of his experiences and ideas on the Agile Otter blog and the Industrial Logic company blog.Tim has writing credits in Agile In A Flash, Clean Code, and many articles scattered through old magazines and the world wide web.He is interested in becoming more effective and valuable, and in helping others do the same.