Skip to content

Elevate your tech career, reclaim your life.
Home / Content / The Show / 7 Common Agile Development FAILS

7 Common Agile Development FAILS

Agile Development Fails

In working with over 30 companies, I've seen 7 common agile software development fails that have little to do with whether you're using scrum or kanban.

Watch or listen to this episode




In working with over 30 companies, I’ve seen 7 common big FAILS in agile software development processes!

These are so common, but so easily avoided, and they have little to do with whether you’re doing kanban or scrum.

In my experience, agile issues are rarely because of a single step in the software development process, but rather because of not considering the implications on the team.

  1. Using high friction tools
  2. Designing for conformity
  3. Not stopping what doesn’t work!
  4. Focusing on data over teamwork
  5. Measuring output over outcomes
  6. Not holding retrospectives
  7. Not releasing completed work


I Can't Stop Thinking About Programming After Work!
Accepting What You Can’t Change On A Software Project


On YouTube and all major podcast networks, Jayme shares teamwork and leadership strategies, guidelines for healthy company culture, and stories about real projects so you can have a sustainable career in the software industry.

Subscribe Now

Jayme Edwards

A family man and veteran of nearly 40 software projects, Jayme experienced many wins and losses over his career as an architect and consultant.

Now he's coaching software developers, managers, and business owners to overcome challenges in the IT industry - so they keep growing.