Scrum Case Study

Due to the complexity of modern technology and solutions, organisations have been forced to develop and use advanced methods and frameworks for managing projects. While there are many project models that can govern a project, this paper compares two models and list their benefits. The goal of these two project models, Scrum and PMBOK are the same however: to bring value to the business.
The traditional organisational management structure is ill-equipped to manage large and complex projects. General management is broken into departments, with each department focused on producing a repetitive output or deliverable. However, a project management structure involves a temporary team from different departments and different skillsets working together to deliver a unique product. Different project models have been developed to govern and direct projects and the project team. These project models, while different in nature, all seek to generate business value through the products they deliver. Scrum is a project model developed in the early 1990s. Scrum was developed out of a need for a lightweight project management framework that could cope with constantly changing requirements. Scrum’s focus is to develop a working product or deliverable in a short period of time called a sprint. At the end of each sprint, the

PMBOK creates a scope statement from a well-defined business need or problem. Once defined, the scope is broken down into pieces, providing a greater understanding of the scope and the work required to achieve the project objectives. A clear scope also assists with defining when a project is complete. In Scrum however, the scope is not defined for the entire project, rather it is defined for the individual sprint. It is difficult to estimate when a project will be complete in Scrum because the scope is not known. PMBOK however, places great importance on scope and is effective at defining