SCRUM - A Project Management Framework
(→References) |
(→Main idea) |
||
| Line 7: | Line 7: | ||
== Main idea == | == Main idea == | ||
Purpose of the framework. | Purpose of the framework. | ||
| − | |||
| − | |||
== Application == | == Application == | ||
Revision as of 12:58, 14 February 2021
SCRUM - A framework for managing projects in an agile way.
Contents |
Abstract
In a 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 and schedule management PMBOK(ref) may not be applicable today. To accommodate this issue, SCRUM can be used because it embraces agility and a fast pace. The SCRUM framework was developed in the early 1990's by Ken Schwaber & Jeff Sutherland, has roots in software development but it is widely used today for any kind of complex project, program and portfolio management. The great benefit of using the SCRUM framework is that you get a focused and high-pace project that is executed in iterations, which accommodates the complexity of the project and ensures that changes to the project plan always can be made. By following the Scrum rules and structure the project will be able to deliver more frequently, with higher value and better outcomes (scrum.org) but only by close collaboration between the Product Owner (PO), Scrum master (SM) and the self-organizing Development Team (DT). Other than the roles, the framework consists of events, and artifacts. The events are Sprints, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective and the artifacts (or documents) product backlog, sprint backlog and burndown chart. The framework is applied in complex projects which are suitable for an agile way of working, and working in iterations (sprints) to obtain increments during the project. 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. SCRUM has limitations by being non-applicable to 'buisness-as-usual' projects, potential scope creep due to an indefinite end-date, implementation in large teams is challenging etc. [1]
Main idea
Purpose of the framework.
Application
Where to use SCRUM. Which projects can benefit from using SCRUM. When and who.
Limitations
SCRUM is extending the current practice of project management but cannot always be applicable. Explain where not to use SCRUM.
Annotated Bibliography
The most important key references will be described here. Standards Journals Papers
References
- ↑ Project Management Institute, Inc.. (2017). Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th Edition). Project Management Institute, Inc. (PMI). Retrieved from https://app.knovel.com/hotlink/toc/id:kpGPMBKP02/guide-project-management/guide-project-management
SCRUM.org. Retrieved from [1]
SCRUM guides. Retrieved from [2]
Retrieved from [3]
