frustration #1. We Had to Plan Our Entire Project Before We Understood What The Project Was All About Without scrum, our teams had built and delivered entirely wrong software and hardware products that did not fulfill demands from our client. We had times in our professional lives when some third party companies had imposed how we supposed to build our software products or software services. Capability Maturity Model (CMM), ISO 9001:2008 and other derivates attempted to help our companies to ensure we build our correct software in correct ways. How successful they used to be is not part of this book. This book was meant to focus on the scrum process and merits of the scrum
framework rather than criticizing almost extinct procedures. However, I have to add that these process improvement frameworks before the scrum software engineering framework recommended a phased approach. They advised a phased software engineering approach which we called the Waterfall Software Engineering Model. With the Waterfall Model, each software project was supposed to start with requirement analysis, where we aimed to understand what our client needed and wanted. Then we designed these requirements, we implemented them, we tested (verified) them, and we maintained them in our software production environments. Finally, we reached to end of the software engineering lifecycle.
Nonetheless, the reality didn't play out like that!
32
