Agile projects, especially working in ‘Scrums’ enables iterative development, which increases opportunities to get User and Stakeholder feedback and reduces the risk that functionality does not meet expectations. Agile cooperations also mean that a detailed specification document is not required, which can accelerate initial development. However, working in an agile environment does require a certain mindset and active project involvement that many organisations struggle to adapt to.
Traditional “Waterfall” software development is much more linear in nature and can be easier for organisations to accept, especially when the project is based on a ‘fixed price’. However, this usually requires a detailed specification document as basis for the fixed price. During the development phase, the client can select how involved they wish to be and far less active participation is required when compared with Agile projects. A significant risk of waterfall projects is that requirements change during the development and change usually has a price.
No one method is perfect, and mVISE has no interest in doggedly following any single development method – there are a number of approaches, for instance, that blend aspects of Agile and Waterfall. Our interest is in finding the sweet spot so that we share risk with our clients in-order that we all are motivated in generating a positive project outcome and winning Applications !