As the project manager in this case study, John had utilized the waterfall method of management. The waterfall model, which was introduced by Dr. Winston Royce in 1970, emphasizes that a logical progression of steps be taken throughout the software development life cycle (SDLC), much like the cascading steps down an incremental waterfall (Powell-Morse,2016). In using this method, John had divided his project team into smaller teams so that he could divide all responsibilities among the smaller groups in order to accomplish the end goal of successfully complete the project.
Should John be allowed a second chance in completing this project, I feel that the Agile method would be better suited. The Agile method is an iterative, team based approach to development that emphasizes the rapid delivery of an application in complete functional components rather than creating tasks and schedules all time is compartmentalized into phases known as sprints(Lotz, 2013). Each of these sprints have a defined duration with a list of deliverables that are planned out before the sprint officially starts. The project manager prioritizes these deliverables based on what the customer determines has the most value for the business. If there is a set back within a sprint that has delayed the completion of the phase then the work will be re-prioritized with all the knowledge gained from the setback being used in future planning. By using the Agile method, John will be better informed as to what the customer requires for a quality product.
Lotz, M. (2013, July 5). Waterfall vs. Agile: Which Methodology is Right for Your Project? Retrieved from https://www.seguetech.com/Waterfall-vs-Agile-methodology/
Powell-Morse, A. (2016, December 8). Waterfall Model: What Is It and When Should You Use It? Retrieved from https://airbrake.io/blog/sdlc/waterfall-model