Managing SCRUM
Contents |
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
So why do we really want to use the SCRUM model instead of the classic Waterfall model (Insert reference). There are many reasons behind this choice but mainly it is the skill to survive and out compete competitors on the marked when it comes to being agile and flexible so you as an organization can have success. The SCRUM framework is a relatively easy and simple framework to adapt and can fulfill own needs and goals. For addressing Agility it is in general acknowledge in the PMI standard for being one of the crucial parts of determining the project life cycle in an adaptive manner (Insert reference).
The SCRUM theory is based on empiricism (Insert reference), which is a philosophic term and means that all concepts originate in experience and that decision making should always be based on something that is observable. Furtherer more the decisions should also be based on the LEAN thinking that waste should be eliminated and there should be focus on what is value-adding. SCRUM also incorporate transparency, adaptation, and inspection. These three things further help in dealing with risks and dealing with unknown problems since they may be identified faster. This is an incredible feature when it comes to the current global business marked which is in a ongoing changing state.
Application and Implementation
When SCRUM is applied it is used as a framework that is managing the life cycle development of a project from start to finish. As previous mention SCRUM is often used in software development but can be implemented in almost every other type of project regardless. In the following section will dive deeper into the framework and describe the different types of blocks which it contains.
The Framework in a whole
Insert text
SCRUM Values
Insert text
SCRUM Teams
Insert text
1. The Product Owner
Insert text
2. The Team
Insert text
3. The SCRUM-Master
Insert text
4. The Development Team
Insert text
SCRUM Events
Insert text
1. Sprints
Insert text
2. Sprint Planning
Insert text
3. Daily SCRUM
Insert text
4. Sprint Review
Insert text
5. Sprint Retrospective
Insert text
SCRUM Artifacts
Insert text
1. Product Backlog
Insert text
2. Sprint Backlog
Insert text
Limitations
Insert text
References
Insert text
