Le Blog De Dan
We are always looking for ways to improve our internal processes to provide better services and software. Recently, we've started experimenting with a different software development methodology called Scrum. Traditionally, we have used the Waterfall methodology, which our clients will be familiar with in practice if not by name. Roughly, the process progresses through the following steps: business requirement -> functional design -> development -> QA -> release. Here is a diagram of the classic Waterfall method we've been using for the past 30 years.
Why change if the current process works? Well, we're not throwing out the Waterfall model entirely - it can be effective in some instances. However, in some development projects, particularly larger ones involving several engineers, the …