Skip to main content

Why Agile does not work in some projects

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

Popuar

MVP in project management

What is MVP in project management? In Project management, MVP is an acronym derived from the term Minimum Viable Product. If you’ve never used or come across such an idea, don’t worry because by the time you’ve finished reading this article, you will have gained a clear insight of what the concept is about. To start with, the concept is usually used to improve planning in agile project management. Similar to agile software development model which emphasizes collaborative development and responsiveness to customer feedback, agile project management offers a way for managing the almost constant changes we experience in today’s organizations. And what is this MVP? As already mentioned, MVP is the Minimum Viable Product. In more clear terms, it’s the simplest prototype which could be put into use. The goal of MVP is to put the simplest version of the product into the hands of the users so as to be convinced that you’re on the right track and then to identify things of highest-priority...

Lean Methodology

Lean Methodology is a subset of Agile Methodology and it meaningfully applies to both startups and software development. It can therefore be used to develop both businesses and products. By being fans of the Agile methodology, we must be interested in learning more about lean startup and lean software development. The Lean Startup Concept The idea upon which the lean startup concept is anchored revolves around avoiding the creation of a product that doesn’t work or that which is not needed by people. It is therefore advisable to find a problem worth solving first before building a business model around it. Lean startup is a perfect fit for entrepreneurs and startups that are still seeking out a business model or product that generate genuine value. However, larger organizations can still use it if they can be flexible while responding quickly to new information and listening to customer needs. In the lean startup model, entrepreneurs will summarize untested hypotheses (basically...