One of my colleagues - a good agile coach - once told me, "Agile is one of the most abused words in the industry". I couldn’t agree more! While agility strives for welcoming change in requirements, quick adaption to change, eliminating wasteful processes, empowering developers, it is not intended in doing things at random. I have however seen people saying this in the name of "Agile" and hence this article, in an attempt to bust some of these myths.
Myth1: Agile means Ad-hoc
People think this way because the initial project plan is not "detailed" and is not written on stone. However, it doesn’t mean there is no planning. Planning in agile happens in multiple waves - called the rolling wave plan at multiple points of the project based on the available inputs at that point. This helps creating realistic plans rather than creating a plan that is not even looked into during execution or a plan that, if followed, leads to product's failure.
Myth2: Agile is undisciplined
Agile liberates you from constraints/processes that are followed at the cost of adding value to the project. But to create value, it mandates a strict discipline to be followed - else speed up for a failure. For e.g., In SCRUM, developers can choose to pull whichever user story they like to develop. However, you are mandated to discuss this in the daily stand-up meetings so that everyone in the team is aware and the dependencies are thought through. It mandates that anything and everything developed needs to come from the product owner as user story in the product backlog. It mandates that you need to have a sprint planning to decide the sprint goals and the stories to be developed. It mandates you cannot change stories picked up for a sprint in the middle of the sprint, unless if the sky falls. It mandates burn-down charts and task boards speak the truth at any given point in the sprint. It mandates that you have a sprint review at the end of each sprint with the stakeholders. It mandates a sprint retrospective at the end of each sprint. Above all, it mandates Trust and Transparency. This is Agile discipline and there is no compromise
Myth3: Change in Requirement with no trade-off
One of the key principles of Agile is to welcome change. This is often misunderstood that you can change anything anytime with no trade-off - very unrealistic! The traditional models have a detailed plan to strictly follow. So it automatically discourages change. This is because you have planned everything with a set of requirements and changing that needs a costlier change in plan and reworking. In agile, since the methodology by itself is built for changing requirements and development is done on iterative increments, it is much more accommodative to change. However, depending on the change, the priority of some other stories may be lowered and pushed to later iterations, some stories may be removed to hit the release date or more iterations may be needed to complete all stories. The product owners and customers should understand this. Agile can handle change with relative ease and help creating products that ultimately serve the business needs instead of a product that gets built on-time and on-budget but never gets used. Forget Agile, no methodology in this world, can predict a fixed date and fixed budget for changing/evolving requirements and additional scope.
Myth 4: No documentation
Agile gets rid of unnecessary documentation that are created for the sake of following "the process". For e.g., there is no need of filling in elaborate forms for record purposes; there is no need to minute every other meeting to create "evidence" - Trust is an undisputed trait of Agile teams; you need not create the system first in paper in the name of “design" or "TDD" with all the pseudo-code (sometimes even the code!!) before hitting the actual code. But you definitely have to create/update documents needed for successful development and tracking - for e.g., backlogs, progress radiators like burn-down chart, task board are very essential to build neat systems.
Myth 5: Agile means no control
A cheetah is agile yet in complete control - watch it in action! Agile projects are not any different. The methodology gives you ample techniques to stay in complete control throughout the execution. For e.g., during every iteration you demonstrate the product to the customer/product owner. This gives them the control over the product being built and ensure it caters to the changing business needs. The development team has complete control over their activities during a sprint - no one can disturb them in the middle of a sprint. The product is continuously and rigorously tested giving absolute control over the quality of code. This gives multi-dimensional control rather than single string control.
Myth 6: Agile team is a robot with no downtime
Yes, Agile strives for delivering value to customer at a quicker pace. But it also believes in sustainability over a long period. Delivering at constant pace is one of the agile principles. So, the team needs to be both passionate and balanced. A high stress on the team could challenge both quality and sustainability. Some of the frameworks like extreme programming(XP) recommends work not more than 40 hrs a week to maintain a good balance and productivity. There are even teams that gives a forced day off to recharge if a team member works beyond prescribed hours.
Myth 7: Agile is a "Silver Bullet"
I'm sure by now this myth is busted! While Agile is highly tuned to deliver value early, it doesn't substitute skills or reduce the complexity of a given problem. Agile teams can also fail but the good part is they quickly learn from failure and adapt/adopt the learning immediately instead of waiting for the next project. Agile, for sure, offers a structured way to handle project with high degree complexity & uncertainty in a much optimized fashion.
Now that I’ve given my thoughts, it is your turn to add yours…
Simply Yours,
Ram
No comments:
Post a Comment