Agile 2

It’s true that there has been some criticism directed towards Scrum and a recent promotion of Agile 2 here https://medium.com/developer-rants/agile-has-failed-smash karts-officially-8136b0522c49. However, it’s important to note that Agile 2 is not a replacement for Scrum, but rather a framework that builds on the principles of Agile and Scrum.

Agile 2 is designed to help organizations become more agile and adaptable in a rapidly changing world. It emphasizes the importance of continuous learning, experimentation, and feedback, and provides a set of guiding principles and practices to help teams work more effectively 2.

While there may be some differences between Agile 2 and Scrum, it’s important to remember that both frameworks are designed to help teams work more collaboratively, iteratively, and adaptively. It’s possible that Scrum may evolve to incorporate some of the principles and practices of Agile 2, but it’s also possible that the two frameworks will continue to coexist and complement each other.

Agile 2 and Amplio are nothing more than a storm in a glas of water.

Agile is a set of values with underlining principles that stays lightweight. Just enough is codified to be universal and can be used as a guidance, yet it leaves it up to individuals to codify their best practices into frameworks or to adapt existing frameworks with new features that won't go against the spirit of Agile.

Agile 2 wants to be a set of values with underlining principles, but it became a framework that isn't lightweight at all. It codified too much and lost its "adapt the solution to anyone's specific circumstances" approach.

Don't get me started on Amplio, it is something horrible pretentious created by a notorious Scrum basher, yet hearing his takes on Scrum and his implementation of Scrum in the past, I can only come to the conclusion that he doesn't understand Scrum at all and blames the framework for his lack of understanding.


Best is just to understand Agile and Lean, learn several frameworks (Scrum, Kanban and eXtreme Programming (XP) are the bare minimum), understand why these frameworks are made in the way they are (which problems do they tackle specifically), what needs to be added to adapt them to your clients needs, etc... and never lose the focus that any framework (standard or customized) is just a means, and not the outcome, to add value to your client.

 

Well stated @Rene G!

Ahmed - Scrum was not developed to align with the Agile Manifesto because when Scrum was created in the early 90s the values and principles mentioned by Rene didn't exist until 2001. I see no need to adjust it for Agile 2.

Of course, I am biased towards Scrum, XP, Lean, and Kanban, yet I highly doubt we'd be talking about Agile today if Scrum didn't exist.

It seems as an attempt to monetize something on Agile word..

it is not something that can be as HTTP/1 vs HTTP/2 though :)

I stopped reading at  The only general principle is, “It depends”.

Agile and Scrum are easy to read and nothing what you just start, do and it runs perfect. In my experience, this is because of bad organizational processes and structures and not because of the team members.

That's the reason why I think, that on a long run, more than 50% of a Scrum Masters working time is used around the team.