Traditionally, the previous software development models like the waterfall model required extensive planning and documentation before any development could even begin. This usually meant months of lost time documenting things that could, in a moments’ notice, all go to waste if there ever was any change in requirement or environment. As we can imagine, this caused a lot of delays in project delivery and was often the reason behind the frustration of developers.
One may wonder – “If this was the case, why did organizations continue to practice comprehensive documentation?” Well, the answer to this is quite simple – implementing the older development models meant that the teams heavily relied on having a fixed list of specifications in order to deliver a product/service that perfectly reflected the initial requirements to the T. However, in practice, a lot of these softwares would be very different from customer’s expectations or would be outdated or irrelevant at the time of delivery.
This is why the Agile method focuses more on getting the software out of the door and into the wild as early as possible. It is only when the product is actually in use that we can obtain relevant feedback from actual users and leverage that real-time feedback to improving the product or service for our customers.
Kommentare