Going Agile, 10 Mistakes: Fail To Define Roles

snowman

Levent Gurses has an article, 10 Mistakes in Transitioning to Agile, in the Dec 2006 Dr. Dobbs Journal. He writes about the most common mistakes that companies make when transitioning from “legacy development methodologies” to agile ones. In this series of short articles for the winter holidays, we’re looking at each of the ten mistakes he identified. Enjoy the light reading, and don’t think too much about work.

Mistake 5: Fail to Define Roles Within the Agile Team

We have to define the roles and responsibilities of each person within the team. This helps both with execution and communication (to people outside the team).

Our Addition

This is project management 101. The people on the team are going to be new to operating on an agile project. They need to understand how everyone works together. The people outside the team will see this as a confusing effort, or a black box. By defining roles, we can manage expectations and improve our ability to execute.

  • Scott Sehlhorst

    Scott Sehlhorst is a product management and strategy consultant with over 30 years of experience in engineering, software development, and business. Scott founded Tyner Blain in 2005 to focus on helping companies, teams, and product managers build better products. Follow him on LinkedIn, and connect to see how Scott can help your organization.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.