7 Common Agile Development FAILS
4/6/2018Topics:Agile Development • Kanban • Scrum
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.
- Using high friction tools
- Designing for conformity
- Not stopping what doesn’t work!
- Focusing on data over teamwork
- Measuring output over outcomes
- Not holding retrospectives
- Not releasing completed work
About the Healthy Software Developer show.
On the show, Jayme shares all of his 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.
Develop a mindset and habits to keep you calm so you still love writing code - avoiding the traps most developers fall into.
A family man and veteran of over 30 software projects, Jayme experienced many wins and losses that led him to helping developers succeed in their careers online.