You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am reading some posts, discussions, articles and a lot of articles are "Why agile fails", "when agile fails"
I need help because for me agile does not fail, it only is not suitable for some projects. What is happening? :)
Agile frameworks are various, flexible, and compatible frameworks for some project, for some they are not. Working on an energetic, ngo, software development projects, agile never failed.
I see it fail mostly when
Most of the articles I've read on Agile failures have all sorts of interesting reasons expounded in them, but when I think about them, most come down to "well, we didn't understand this part of it, so we didn't do it".
Yeah I agree with this. In my experience it's not Agile itself that fails, but more that companies and individuals can fail to understand or buy into the principles. It takes a pretty significant cultural change reorient a waterfall company to Agile. It changes power dynamics and career trajectories, and may require letting go of long-term employees who are highly placed in the company.
I am unclear what you mean by "fail"; perhaps didn't achieve what was believed possible. If so, I have observed these cases:
Hi @Spasoje Jesic , My experience is very similar to what I've read in previous comments. The perception of Agile failing comes when it wasn't used properly, or when a flavor of Agile wasn't really a good fit. I have seen teams using Scrum when Kanban was a better fit because of the amount of support tickets and unplanned work that came their way. Also, while software development projects see big improvements with the use of Scrum, Kanban or other variations of Agile, hardware projects seem to have a harder time due to dependencies with vendors and other teams that may not be using Agile methodologies. I've also experienced that the introduction of scale agile processes (like SAFe) have helped teams and companies that wanted to keep some waterfall-like processes while letting their teams be agile.
In my experience, Agile can (and often does) fail because teams are unable or unwilling to be transparent and vulnerable when it comes to their work items.
I don't thing that a agile methodology is failing. It's the company not endorsing it fully, or the team not embracing it, or other problems with product/project itself.
Secondly, a weak team will still be a weak team - Agile might help to make it a better team, BUT Agile is not a silver bullet.
I don't thing that a nimble approach is coming up short. It's the organization not underwriting it completely, or the group not accepting it, or different issues with item/project itself.
Also, a feeble group will in any case be a powerless group - Agile may assist with making it a superior group, BUT Agile is certifiably not a silver projectile.