Monday, September 21, 2020

When Agile is not the right choice? - Part 2

 

(Image Credit: https://hygger.io/blog/agile-and-waterfall-teams/)

In the previous post, we discussed unknowns in the project. Based on that, we decide the Project management technique should be Agile or Traditional. 

In this post, we will discuss the criticality of the project for the organization. If the failure of the project can be a big impact on the organization, then adopting a new method is not prudent. Inspiration can be taken for some areas, but a complete revamp is not advisable. With the adaptation of Agile, the project should benefit instead of getting exposed to the risk of failure. If the project teams are comfortable in following a prescriptive plan, and the project is critical. In this case, adopting an Agile methodology is a risk not worth taking.

When the requirements will change and be more elaborated on as we progress with development, agile may be the best choice. However, if the project is of the type where requirements should not change, agile is not recommended. An example of such projects could be the one related to security and safety. One can not change the requirements, which may impact the safety of individuals. Like the foundation of a building is laid based upon the number of floors to be built. Customers cannot add a requirement of a few more floors in the building. Similarly, developing an off-roader on the chassis of a city car is a threat.

Agile is to be used only when it is a value add, otherwise it is better to stick to the traditional approach.

No comments:

Comments system