Managing SCRUM

From apppm
Revision as of 19:24, 20 February 2022 by HannibalDanielsen (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Managing SCRUM

This wiki page article will try to help the reader gain knowledge about the agile managing method SCRUM and focus on SCRUM as a project management framework and the implementation. The SCRUM method is a very popular agile managing method, and the internet provides a whole ocean with information on the topic. SCRUM has even become that popular that it is possible to take an education in SCRUM which allows you to become a SCRUM-master. Since the world we live in is in a every changing stage and decisions and projects becomes more and more complex, the ability to control and handle project managing is that more important. So called standard project frameworks as the waterfall-model will in some cases not be applicable. Because of this very reason, SCRUM, which is an adaptive project management framework can be used instead since the method exceed in agility and fast project deliveries if used correct. It should be mentioned that SCRUM is part of the project and development life cycle in the PMI standard.

History of SCRUM

Back in the 1990’s the SCRUM framework was developed by Ken Schwaber & Jeff Sutherland and was based on LEAN thinking and mainly derives from software development. The word SCRUM itself Jeff Sutherland borrowed from a paper by Takeuchi and Nonaka, published in the Harvard Business Review. In this paper they used the word SCRUM as an analogy for high-performing and cross-functional product development teams with a so-called Scrum formation which are when the play is a rugby match is reset (insert reference). Today as before mention the SCRUM framework has become a popular way for organization to be more agile and a deal with various project types. Organization who uses this framework will have an easier time when it comes to structure the development life cycle of projects by having transparency, continues improvements and in general embrace change during projects. The soul process in SCRUM is to first and foremost create the backlog of the product and thereafter define the so-called sprint (insert reference), by making sprint backlogs and then make performing development results, often measured in pre chosen KPI’s in an increment. Working in an incrementally way, the project team can thereby make continues improvements and learn from previous sprint and optimize. This framework then create value in an adaptive and agile way through the team, events, and SCRUM-values (insert reference).

Why use SCRUM

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox