Scrum - Revision history

Tkokotas at 12:40, 20 December 2018

2018-12-20T12:40:53Z

← Older revision		Revision as of 12:40, 20 December 2018
Line 1:		Line 1:
			''Developed by Elisabeth Opøien''


	[[File:Scrum framework.jpg\|400px\|thumb\|right\|Fig 1: The Scrum Framework Source: Author]]		[[File:Scrum framework.jpg\|400px\|thumb\|right\|Fig 1: The Scrum Framework Source: Author]]
	This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.		This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.

Murcs: /* Sprint Backlog */

2014-12-01T22:42:23Z

Sprint Backlog

← Older revision		Revision as of 22:42, 1 December 2014
Line 341:		Line 341:
	</span>		</span>

	Figure 4 Example of a Sprint Backlog for a software development		Figure 4 Example of a Sprint Backlog for a software development<ref name=two/>

	Since the Team is self-managing it needs to know how the Sprint is going and if they are able to finish the items on time. To manage this a Sprint Burndown Chart is used <ref name=tvelve>Understanding the Scrum Burndown Chart, Dusan Kocurek, ScrumDesk Link: www.methodsandtools.com </ref><ref name=two/>. This Charts contains the ideal time set to do the tasks, while one person adds everyday to the Sprint Burndown Chart what the expected hours remaining to finish for the entire Team is. The goal is that the Burndown Chart has a downward slope, meaning that they at the end of the Sprint have reach the goal <ref name=two/>.		Since the Team is self-managing it needs to know how the Sprint is going and if they are able to finish the items on time. To manage this a Sprint Burndown Chart is used <ref name=tvelve>Understanding the Scrum Burndown Chart, Dusan Kocurek, ScrumDesk Link: www.methodsandtools.com </ref><ref name=two/>. This Charts contains the ideal time set to do the tasks, while one person adds everyday to the Sprint Burndown Chart what the expected hours remaining to finish for the entire Team is. The goal is that the Burndown Chart has a downward slope, meaning that they at the end of the Sprint have reach the goal <ref name=two/>.

Murcs: /* Product Backlog */

2014-12-01T22:42:04Z

Product Backlog

← Older revision		Revision as of 22:42, 1 December 2014
Line 241:		Line 241:
	</span>		</span>

	Figure 3 Show an example of a Product Backlog of a software development.		Figure 3 Show an example of a Product Backlog of a software development<ref name=two/>.

	In figure 3 it can be seen that the the items are listed and prioritized, this list can be as long as needed. The estimated value for the product is given indication how high of importance it is for the customer, one can also see what the initial estimated effort is this can change when a Sprint has started. There can also be seen the how many Sprints there are left and where the item can be placed or when it was done.		In figure 3 it can be seen that the the items are listed and prioritized, this list can be as long as needed. The estimated value for the product is given indication how high of importance it is for the customer, one can also see what the initial estimated effort is this can change when a Sprint has started. There can also be seen the how many Sprints there are left and where the item can be placed or when it was done.

Murcs: /* Sprints */

2014-12-01T22:41:39Z

Sprints

← Older revision		Revision as of 22:41, 1 December 2014
Line 117:		Line 117:
	</span>		</span>

	Figure 2. Estimating Available hours during a Sprint		Figure 2. Estimating Available hours during a Sprint <ref name=two/>

	====Daily scrum====		====Daily scrum====

Murcs: /* Sprint Backlog */

2014-12-01T22:41:05Z

Sprint Backlog

@@ Line 248: / Line 248: @@
 The Sprint Backlog contains what needs to be done during a sprint. The Sprint Backlog is made by looking at the Product Backlog and taking the highest priority item and break it down into individual tasks<ref name=two/>. The Sprint Backlog visualized the work that the Development Team needs to do to reach the Sprint Goal. If something is found unnecessary to do it is removed from the Sprint Backlog.
-Table of SB
+<span style="font-size:18%">
-Since the Team is self-managing it needs to know how the Sprint is going and if they are able to finish the items on time. To manage this a Sprint Burndown Chart is used <ref name=tvelve>Understanding the Scrum Burndown Chart, Dusan Kocurek, ScrumDesk Link: www.methodsandtools.com </ref><ref name=two/>. This Charts contains the ideal time set to do the tasks, while one person adds everyday to the Sprint Burndown Chart what the expected hours remaining to finish for the entire Team is. The goal is that the Burndown Chart has a downward slope, meaning that they at the end of the Sprint have reach the goal <ref name=two/>.
+Figure 4 Example of a Sprint Backlog for a software development
-Figure of a burndown chart
+Since the Team is self-managing it needs to know how the Sprint is going and if they are able to finish the items on time. To manage this a Sprint Burndown Chart is used <ref name=tvelve>Understanding the Scrum Burndown Chart, Dusan Kocurek, ScrumDesk Link: www.methodsandtools.com </ref><ref name=two/>. This Charts contains the ideal time set to do the tasks, while one person adds everyday to the Sprint Burndown Chart what the expected hours remaining to finish for the entire Team is. The goal is that the Burndown Chart has a downward slope, meaning that they at the end of the Sprint have reach the goal <ref name=two/>.
 ==Implementation of Scrum==

Murcs at 22:28, 1 December 2014

2014-12-01T22:28:54Z

← Older revision		Revision as of 22:28, 1 December 2014
Line 1:		Line 1:
	[[File:Scrum framework.jpg\|~~200px~~\|thumb\|right\|Fig 1: The Scrum Framework Source: Author]]		[[File:Scrum framework.jpg\|400px\|thumb\|right\|Fig 1: The Scrum Framework Source: Author]]
	This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.		This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.

Murcs at 22:27, 1 December 2014

2014-12-01T22:27:39Z

← Older revision		Revision as of 22:27, 1 December 2014
Line 1:		Line 1:
			[[File:Scrum framework.jpg\|200px\|thumb\|right\|Fig 1: The Scrum Framework Source: Author]]
	This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.		This article focuses on Scrum, which is a framework <ref name=one>A Brief History of Scrum, A Confusing Origin Story, Venkatesh Krishnamurthy, October 15, 2012</ref> for dealing with [[Agile Project Management]]. Scrum can be used in different size projects and can also be used for Program and Portfolio management. The article will introduce the framework and the underlying principles. The framework has been developed by many contributors, but was introduced by Jeff Sutherland and Ken Schwaber at the OOPSLA 1995 conference <ref name=one/>.

Murcs: /* Product Backlog */

2014-12-01T21:40:18Z

Product Backlog

← Older revision		Revision as of 21:40, 1 December 2014
Line 242:		Line 242:
	Figure 3 Show an example of a Product Backlog of a software development.		Figure 3 Show an example of a Product Backlog of a software development.

	In figure 3 it can be seen that the the items are listed and prioritized, this list can be as long as needed. The estimated value for the product is given indication how high of importance it is for the customer, one can also see what the initial estimated effort is this can change when a Sprint has started. There can also be seen the how many Sprints there are left.		In figure 3 it can be seen that the the items are listed and prioritized, this list can be as long as needed. The estimated value for the product is given indication how high of importance it is for the customer, one can also see what the initial estimated effort is this can change when a Sprint has started. There can also be seen the how many Sprints there are left and where the item can be placed or when it was done.

	====Sprint Backlog====		====Sprint Backlog====

Murcs: /* Product Backlog */

2014-12-01T21:39:24Z

Product Backlog

@@ Line 139: / Line 139: @@
 One of the ways the product backlog is prioritizing is by looking at the relative size of the items (factoring in complexity, uncertainty and effort) <ref name=two/>, using a unit of Story Points. This is used to see how many tasks they can to each Sprint, by saying that they on average can do 24 Story Points per Sprint <ref name=two/>.
-table of PB
+<span style="font-size:18%">
 ====Sprint Backlog====

Murcs: /* Artifacts */

2014-12-01T21:18:19Z

Artifacts

← Older revision		Revision as of 21:18, 1 December 2014
Line 132:		Line 132:

	===Artifacts===		===Artifacts===
			Scrum consists of different Artifacts, where the main ones are the Product Backlog containing all the tasks ever needed to be done. Sprint Backlog where the tasks that needs du be done during the Sprint is listed, and a Burndown chart which tells how the progress is going.

	====Product Backlog====		====Product Backlog====
	The Product Backlog is a list of everything that might be needed done to the product <ref name=nine/><ref name=four/><ref name=two/>, it is where any changes to the product will be added. The Product Backlog is the POs responsibility, anyone can add to it but it is the PO that has the responsibility of prioritize the list to maximize the ROI<ref name=two/><ref name=four/>. But there is always only one item on the top of the list. If something is not in the Product Backlog then it does not exist, but the Product Backlog is never done, and at the beginning only the known requirements are added <ref name=nine/>. There can be multiple Scrum Teams working on the same Product Backlog.		The Product Backlog is a list of everything that might be needed done to the product <ref name=nine/><ref name=four/><ref name=two/>, it is where any changes to the product will be added. The Product Backlog is the POs responsibility, anyone can add to it but it is the PO that has the responsibility of prioritize the list to maximize the ROI<ref name=two/><ref name=four/>. But there is always only one item on the top of the list. If something is not in the Product Backlog then it does not exist, but the Product Backlog is never done, and at the beginning only the known requirements are added <ref name=nine/>. There can be multiple Scrum Teams working on the same Product Backlog.