Agile Snafus: When Good Teams Go Bad

James Waletzky

Agile done well can lead to great successes—rapid delivery of business and user value, high product quality, fast time to market, and engineering productivity. Agile done poorly leads to skepticism of the methodologies, distrust of the principles, and failure to deliver—in essence, a snafu [sna-foo]: a badly confused or ridiculous muddled situation. James Waletzky has gathered a set of snafus (anti-patterns) that pose challenges for organizations adopting agile. Set yourself up for success by understanding where teams go wrong with agile, complete with tips on how to avoid or fix the issues. James starts with a backlog of agile anti-patterns. Like any backlog, external inputs factor into the ranking of the items within it. We first vote on which topics are most interesting. James then proceeds through each topic in the backlog—until we run out of time. Some examples of items in the backlog may include lack of management commitment, no “done” definitions, and poor development practices to support agile. Discover how to deal with these problems so they don’t “snafu” you.

Upcoming Events

Jun 23
Jul 12
Sep 29
Oct 20