Better Software East 2016 - Improving the Team
Wednesday, November 16
Agile Snafus: When Good Teams Go Bad
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...
Your Agile Team Needs a Therapist
Imagine you’re on an agile development team—and something feels weird. People disagree constantly, and when they finally do agree, no one commits to deliver the solution. Vocal team members dominate the conversation. You don’t trust your teammates. They don’t trust you. This isn’t a team. It’s just a group of people. Does this sound familiar? Because people are people—not interchangeable robots—building high-performing, self-organizing teams takes specific skills and a lot of work. In his experience working with agile teams, Robb Pieper has often taken on the role...