Managing SCRUM - Revision history

HannibalDanielsen: /* Why use SCRUM */

2022-03-27T19:49:54Z

Why use SCRUM

← Older revision		Revision as of 19:49, 27 March 2022
Line 9:		Line 9:

	== Why use SCRUM ==		== 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.		So why do we really want to use the SCRUM model instead of the classic Waterfall model. 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]])~~.		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.

	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.		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.

HannibalDanielsen: /* History of SCRUM */

2022-03-27T19:49:41Z

History of SCRUM

← Older revision		Revision as of 19:49, 27 March 2022
Line 5:		Line 5:

	== History of SCRUM ==		== 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]])~~.		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.
	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]])~~.		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, 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.

	== Why use SCRUM ==		== Why use SCRUM ==

HannibalDanielsen: /* References */

2022-03-27T19:49:13Z

References

← Older revision		Revision as of 19:49, 27 March 2022
Line 89:		Line 89:

	3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ		3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ

			4. Agile project management with Scrum: https://www.pmi.org/learning/library/agile-project-management-scrum-6269

HannibalDanielsen: /* References */

2022-03-27T19:48:03Z

References

← Older revision		Revision as of 19:48, 27 March 2022
Line 87:		Line 87:

	2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.		2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.

			3. What Is Scrum in Project Management?: https://www.youtube.com/watch?v=M12HSYZkrgQ

HannibalDanielsen: /* Limitations */

2022-03-27T19:46:37Z

Limitations

← Older revision		Revision as of 19:46, 27 March 2022
Line 75:		Line 75:

	== Limitations ==		== Limitations ==
	~~Insert text~~
			As explained SCRUM is a very valuable framework and can be used regarding many different projects but of course have downfalls and cannot always be applicable. In cases where it is not applicable is projects which by their nature is not that complex. In these less complex projects all the iterations and many feedback loops will not necessarily be generate value where a more straight forward approach will be of better use.

			As a general theme through the SCRUM framework it is highly necessary that the team who is doing the project need to have certain prementioned skills such as being self-organized, etc. if these things are not present and the team is not on the same page and understand the framework of SCRUM it will run in to a pitfall.

			Last but not least the biggest issue when it comes to implementing SCRUM in an organization is the cultural change it brings with it. As a company you cannot just pick up SCRUM and simply implement it during a project to managing tool and framework. For many people who have not been working with the framework and the philosophy before it is an entirely new way of thinking. So to probably use the SCRUM framework a slowly and time consuming training and education is needed to fully benefit from it.

	== References ==		== References ==

HannibalDanielsen: /* 2. Sprint Backlog */

2022-03-27T18:41:04Z

2. Sprint Backlog

← Older revision		Revision as of 18:41, 27 March 2022
Line 71:		Line 71:

	==== 2. Sprint Backlog ====		==== 2. Sprint Backlog ====
	~~Insert text~~
			The sprint backlog is created by the development team when the sprint planning is taken place. This plan is consisting of goals which explains why it is valuable. Here items from the product backlog is used to define what work should be done to reach an increment. The main focus of the sprint backlog should be transparency a visibility so they are easy to read and understand. There are many different tools which can used and help with the visibility. A tool here can be a Kanban board. A Kanban board can help the team visualize where they are in the process and what actions is the next to come to help them fulfill the increment. When the sprint is taking place and the work is overviewed during the daily SCRUM meetings adjustments can be made.

	== Limitations ==		== Limitations ==

HannibalDanielsen: /* 1. Product Backlog */

2022-03-27T17:27:04Z

1. Product Backlog

← Older revision		Revision as of 17:27, 27 March 2022
Line 67:		Line 67:

	==== 1. Product Backlog ====		==== 1. Product Backlog ====
	~~Insert text~~
			The product backlog is a very important artifact and is owned by the product owner. This backlog contains a long list of all the requirements from the stakeholder which needs to be fulfilled so the final product goal can be reached. All the different items on this list need to be in prioritized in descending order and specified. Some of these items on the list can be grouped into logical groupings which can be different user stories. A user story is defined work which will generate value for the customer. Since the product owner is the owner of the product backlog this person decides which user stories should be handle in the certain sprint.

	==== 2. Sprint Backlog ====		==== 2. Sprint Backlog ====

HannibalDanielsen: /* SCRUM Artifacts */

2022-03-27T17:19:32Z

SCRUM Artifacts

← Older revision		Revision as of 17:19, 27 March 2022
Line 63:		Line 63:

	=== SCRUM Artifacts ===		=== SCRUM Artifacts ===
	~~Insert text~~
			The SCRUM artifacts is what indicates value and will in a whole increase transparency.

	==== 1. Product Backlog ====		==== 1. Product Backlog ====

HannibalDanielsen: /* References */

2022-03-27T17:17:51Z

References

← Older revision		Revision as of 17:17, 27 March 2022
Line 78:		Line 78:
	1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.		1. Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.

	2.		2. McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA.

HannibalDanielsen: /* 4. Sprint Retrospective */

2022-03-27T17:17:24Z

4. Sprint Retrospective

← Older revision		Revision as of 17:17, 27 March 2022
Line 59:		Line 59:

	==== 4. Sprint Retrospective ====		==== 4. Sprint Retrospective ====
	~~Insert text~~
			As before mentions the last phase in the sprint is the retrospective phase. In this phase the SCRUM-master is the host of the meeting where the development team can review how the sprint went. This is where the team can talk about and raise concerns to problems or issues they have encountered during the sprint and actions will be taken towards solving them.

	=== SCRUM Artifacts ===		=== SCRUM Artifacts ===