SCRUM - A Project Management Framework
Abstract
In an ever-changing world that is getting more and more complex, the art of project management is becoming harder to control due to uncertainty and the speed in which requirements and demand change. Standard ways of planning a project, such as the Waterfall model, may not be applicable today. To accommodate this issue, the adaptive project management framework, Scrum, can be used because it embraces agility and a fast pace. Scrum relates to the project and development life cycles in the PMI standard[1]. Even though Scrum is applicable for both project, program and portfolio management, this article will focus solely on Scrum as a project management framework and the implementation of Scrum.
The Scrum framework was developed in the early 1990's by Ken Schwaber & Jeff Sutherland and is a framework based on empiricism and lean thinking and has its roots in software development[2]. Today, Scrum is one of the most popular ways of becoming agile and is widely used for various projects. Benefits of utilizing the Scrum Framework to structure the development life cycles are continuous improvements, transparency, early adoption, and embracing change, which is a great advantage compared to the classic Waterfall model.[3]. The process of Scrum is to first create the product backlog and then define the sprint by creating the sprint backlog and then performing development resulting in an increment. By working incrementally, the team can learn from previous sprints to optimize the next and the product may be ready for release earlier than first anticipated[4]. The Scrum Framework creates value in an adaptive and agile way through the Scrum values, the Scrum team, events and artifacts. The values focus on Commitment, Focus, Openness, Respect, and Courage. The team consists of the Product Owner (PO), the Scrum master (SM) and lastly, the self-organizing Development Team (DT). Furthermore, the framework consists of events such as Sprints, Sprint Planning and Sprint Retrospective, and artifacts which are the product backlog, sprint backlog and burndown chart[2]. Scrum has limitations by being non-applicable to 'business-as-usual' projects, potential scope creep due to an indefinite end-date, implementation in large teams is challenging etc.
Main idea
As the world emerges, new trends arise. Being agile and flexible has become a precondition to survive and succeed in today's buisness environment[5]. It is crucial for all kinds of businesses to be able to respond and adapt to unforeseen activities and events on the market because if not, someone else will fulfill the customers' demand. Agility is revolutionary and acknowledged in the PMI standard[1]
Cite error:
<ref> tags exist, but no <references/> tag was found
