Please login or join to subscribe to this thread
Organizations choose the methodology that is best meeting their business needs. So I have seen that their methodology is always evolving. There are companies where we see an amalgamation of both waterfall & agile.
So where the desire is to move to Agile to increase velocity but still retain the processes of waterfall, I would suggest to have an independent Agile coach, who can see the situation & the expectation & be able to help with the methodology to meet the business & employee needs.
Makes sense, somehow!
Thank you for sharing
The problem is the big misunderstanding outside there mainly created by people who is trying to sell something and instead of it contributes to the general confusion which is jeopardizing the intentions of other people who are working with Agile from long time ago. Sorry for writting about me but for a chance of the destiny I was part of the group which "invented" Agile in 1990 (which was totally outside the software domain) and then I was part of the software movement, including it I was part of the group which created DSDM. But returning to this interesting discussion and taken @Maria comment the first step is: 1-why to transform? what does mean? Because organizations are open and adaptable systems then when environment change they must to transform and adapt. This is one of the pillars of Agile: system theory. You can validate it in the original papers. 2-Agile has to be applied if and only if it is the solution to the transformation problem. 3-Agile is an approach not a life cycle, not a method/framework. Then you can apply Agile with any life cycle such as waterfall. By the way, people confuse waterfall with sequential. My recommendation is going to Mr. Royce original paper about waterfall where you can see things like feedback loops for example. 4-Lean and Agile are not the same. Lean provides flexibility. Agile provides agility. 5-what you state above about things to achieve full benefits is valid for anything than Agile too.
In addition to above ""Agile mindset is the key"""
Support Sergio's post.
Agile is a trend as Poorvi says. We humans tend to follow trends.
I support @Rajendra Medepalle's point of view,
I also think "transformation", first of all "thinking transition" and "mindset transition"
The problem with roles and responsibilities is that people usually use them as boxes or boundaries. Agile is all about people going beyond their comfort zone.
Scrum masters are important communication enablers. These are your leaders that will make a difference in your results.
Transparency also includes visibility into the project. People should be able to see your project status, preferably as it stands now.
The key to making agile approaches work is continuous improvements. As long as people are learning from their mistakes and trying something new, then you will gain value and efficiency.
Please login or join to reply