I know when you think of agile, what probably comes to your mind is the fact that it is the most widely employed and successful software development methodology today because of its iterative and flexible approach. Agile leveraged together with DevOps has revolutionized software development. However, this doesn’t imply that it is the right way to handle every situation or project. In some projects, Agile plus DevOps will not work at all because the incremental approach and flexibilities associated with this technologies are not feasible or compatible with those projects.
Situations in Which Agile is Not Helpful
- Agile cannot be applied in physical projects such as the design and build of a new hospital. Agile welcomes requirement and design changes even in late development but this would be unworthy in the hospital project as changes would have major impacts on the project cost and schedule.
- In physical projects like the hospital design and build contract, the design remains a major and discrete phase of the project and therefore cannot be iterated along the way but this is allowed in most agile projects.
- When it comes to software, older systems like those based on COBOL and ISAM don’t relate well with agile. Such systems don’t work and play well with modern tooling hence very little automated efforts could be applied to roll out changes to those systems on weekly or daily basis.
- Agile and DevOps don’t relate well with the planning and design of any project. When you consider system design for example, architects are much more likely to come up with a much more successful design and complete it within a compressed amount of time when they do this systematically as opposed to when they include boxed iterations.
- When overused through being extended to almost everything, Agile and DevOps become diluted by the amount of failures resulting from their overuse and thus their overall value is not witnessed.
Comments
Post a Comment