Brief history of software development processes
In the earliest days of software development, code and fix model was mainly used. Development team started the work with a very general idea of the product and then repeated the same process of informally coding, testing and fixing issues until the product was ready for release. It was common to forego planning.
The waterfall model was officially identified as an alternative to the code–and–fix model in 1970. The classic waterfall model has served the software development community well for many years. Though this model works well when requirements are simple and crystal clear, and changes are not expected, it is not found suitable for complex products where requirements cannot be finalized upfront and changes are frequently expected. High schedule and cost variances are very common in projects that follow the waterfall model.
Many frameworks, models and methods were introduced in 1990 s to address the problems with the waterfall model. Of all the frameworks and models, Scrum is extremely popular. Scrum follows iterative and incremental approach for development. Accordingly, a large development work is broken down into smaller chunks and each chunk is delivered iteratively. In Scrum, each iteration is called a Sprint. Each Sprint has a consistent period of 2 to 4 weeks. Sprint is the heart of Scrum. The commitment to short iterations of work is the main reason for the popularity of Scrum.
Courses : 1
Specification: Scrum for Beginners