Quick Links

5 Common Agile PM Transition Pitfalls to Avoid

Agile transformations do not take place overnight, which is the stark reality. They require discipline and consistent inspecting, adapting and follow-through. Any well-intended transformation is at risk of slipping back to old ways if certain challenges and pitfalls are not addressed and avoided.

Here are five major pitfalls organizations face in their agile transitions:

1. Double Work Agile: Organizations new to agile may expect to continue using traditional reports, artifacts and meetings in addition to agile activities and artifacts. Teams will burn out quickly if expected to meet the demands of two very different approaches.

2. Ineffective Product Owner: Without alignment between the business and development teams, projects will resemble traditional and waterfall projects as siloed teams try to work together without a clear and common vision.

3. Discipline Slips: Returning to old ways is easy. Agility is not rudderless, but demands discipline and dedication to deliver continuous improvement.

4. Diluting Until Dead: When change is difficult, it is common for teams to start diluting proven agile practices in order to accommodate fears and frustrations, until the methods being used no longer resemble agility.

5. Inappropriate Physical Environment: At the heart of agile values and principles are individuals, interactions, face-to-face communication and collaboration. Effectively applying these values and principles requires changes in physical environments. The reality is that sometimes even the simplest of changes get overlooked by teams that try to cut corners.

Professional transition support in the form of agile coaching and mentoring can be key in organizations ensuring they avoid these common pitfalls.

Share This Post

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Please complete this equation so we know you’re not a robot. *

Thanks for submitting your comment!
You must be logged in to comment.