How Responding to Change Over Following a Plan Always Works for Agile
When it comes to Agile, the project has to respect its value.
Until Agile came into the picture, the traditional model of software development i.e Waterfall methodology was relying on torment planning of the project which was entire project planning before the project starts. The project team tries to manage the deadline with a maximum delivered part of the project. Due to heavy work pressure, skeptical and unanswered queries, derange the project team with partial delivery. At the mid-stage of the project, business people are occupied planning the next project. This obstacle leads to work on assumptions and deliver the project inaccurately. The project team is blindly following the plan and missing the opportunity to create a valuable product.
If I take an example of my project experience where my team was delivering a project for an eCommerce client. The project was to integrate a new order management system to track orders and its statuses.
In the waterfall approach, the business team and the project team rigorously made a plan and decided to deliver the project in 3 months. The plan includes-
- Month 1: Deintegrate the existing order management system and it’s component and figure out the impact.
