Scrum 2 - Revision history

Peter Vilhelmsen: /* Limitations of Scrum */

2022-03-22T21:22:42Z

Limitations of Scrum

← Older revision		Revision as of 21:22, 22 March 2022
Line 137:		Line 137:
	== Limitations of Scrum ==		== Limitations of Scrum ==

	No methodology is perfect. Scrum, just like any other framework, has some drawbacks. Some organizations have experienced trouble adapting this framework to larger groups. This has led some organizations to develop their own variation of the Scrum framework. One of the most popular alternatives to the Scrum framework is the Spotify model. This model splits the entire organizations into groups which are named; Squads, Tribes, Chapters Guilds etc. <ref name="spotify"\>.		No methodology is perfect. Scrum, just like any other framework, has some drawbacks. Some organizations have experienced trouble adapting this framework to larger groups. This has led some organizations to develop their own variation of the Scrum framework. One of the most popular alternatives to the Scrum framework is the Spotify model. This model splits the entire organizations into groups which are named; Squads, Tribes, Chapters Guilds etc. <ref name="spotify"/>.
	Scrum also divides responsibility and authority among the team members. This is done to strengthen self-management and engagement. However, this means that if team member is to leave, it can have devasting consequences for the Scrum team. Some people also find it frustrating with the daily meeting, which is a key feature of the Scrum framework.		Scrum also divides responsibility and authority among the team members. This is done to strengthen self-management and engagement. However, this means that if team member is to leave, it can have devasting consequences for the Scrum team. Some people also find it frustrating with the daily meeting, which is a key feature of the Scrum framework.
	These drawbacks show why it is important for organizations looking to adopt the Scrum methodology, to understand how it may affect them and possibly make their own adaptations.		These drawbacks show why it is important for organizations looking to adopt the Scrum methodology, to understand how it may affect them and possibly make their own adaptations.

Peter Vilhelmsen: /* Scrum and Agile management */

2022-03-22T21:22:13Z

Scrum and Agile management

← Older revision		Revision as of 21:22, 22 March 2022
Line 133:		Line 133:
	“Facilitating change is more effective than attempting to prevent it. Learn to trust in your ability to respond to unpredictable events; it's more important than trusting in your ability to plan for disaster.”<ref name="manifesto"/>		“Facilitating change is more effective than attempting to prevent it. Learn to trust in your ability to respond to unpredictable events; it's more important than trusting in your ability to plan for disaster.”<ref name="manifesto"/>

	Agile practitioners will opt for lighter and simpler management tools, with one of the most popular being the Scrum framework. Scrum was designed to be simple and easily applicable to whatever goal to organization wants to achieve. The paper “Agile Software Development Methods: Review and Analysis” written by Pekka Abrahamsson, Outi Salo, Jussi Ronkainen and Juhani Warsta<ref name="Agile methods"/>, mentions Scrum as a popular agile development method alongside or frameworks such as: Extreme Programming, Feature Driven Development and The Rational Unified Process.		Agile practitioners will opt for lighter and simpler management tools, with one of the most popular being the Scrum framework. Scrum was designed to be simple and easily applicable to whatever goal to organization wants to achieve. The paper “Agile Software Development Methods: Review and Analysis” written by Pekka Abrahamsson, Outi Salo, Jussi Ronkainen and Juhani Warsta<ref name="Agile methods"/>, mentions Scrum as a popular agile development method alongside or frameworks such as: Extreme Programming, Feature Driven Development and The Rational Unified Process.

	== Limitations of Scrum ==		== Limitations of Scrum ==

Peter Vilhelmsen: /* Limitations of Scrum */

2022-03-22T21:21:55Z

Limitations of Scrum

← Older revision		Revision as of 21:21, 22 March 2022
Line 137:		Line 137:
	== Limitations of Scrum ==		== Limitations of Scrum ==

	No methodology is perfect. Scrum, just like any other framework, has some drawbacks. Some organizations have experienced trouble adapting this framework to larger groups. This has led some organizations to develop their own variation of the Scrum framework. One of the most popular alternatives to the Scrum framework is the Spotify model. This model splits the entire organizations into groups which are named; Squads, Tribes, Chapters Guilds etc. (spotify ~~ref)~~.		No methodology is perfect. Scrum, just like any other framework, has some drawbacks. Some organizations have experienced trouble adapting this framework to larger groups. This has led some organizations to develop their own variation of the Scrum framework. One of the most popular alternatives to the Scrum framework is the Spotify model. This model splits the entire organizations into groups which are named; Squads, Tribes, Chapters Guilds etc. <ref name="spotify"\>.
	Scrum also divides responsibility and authority among the team members. This is done to strengthen self-management and engagement. However, this means that if team member is to leave, it can have devasting consequences for the Scrum team. Some people also find it frustrating with the daily meeting, which is a key feature of the Scrum framework.		Scrum also divides responsibility and authority among the team members. This is done to strengthen self-management and engagement. However, this means that if team member is to leave, it can have devasting consequences for the Scrum team. Some people also find it frustrating with the daily meeting, which is a key feature of the Scrum framework.
	These drawbacks show why it is important for organizations looking to adopt the Scrum methodology, to understand how it may affect them and possibly make their own adaptations.		These drawbacks show why it is important for organizations looking to adopt the Scrum methodology, to understand how it may affect them and possibly make their own adaptations.

Peter Vilhelmsen: /* References */

2022-03-22T21:20:48Z

References

← Older revision		Revision as of 21:20, 22 March 2022
Line 170:		Line 170:
	</ref>		</ref>

	<ref name="manifesto">~~Scrum Product Owner,”~~ Fowler, M. and Highsmith, J., 2001. The agile manifesto. Software development, 9(8), pp.28-35. </ref>		<ref name="manifesto">Fowler, M. and Highsmith, J., 2001. The agile manifesto. Software development, 9(8), pp.28-35. </ref>


			<ref name="spotify"> Discover the Spotify model MARK CRUTH Available online: https://www.atlassian.com/agile/agile-at-scale/spotify </ref>


	</references>		</references>

S184301: /* References */

2022-03-22T21:14:55Z

References

← Older revision		Revision as of 21:14, 22 March 2022
Line 153:		Line 153:
	=References=		=References=

	</references>		<references>


Line 165:		Line 165:
	<ref name="Agile methods"> Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. </ref>		<ref name="Agile methods"> Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. </ref>

	<ref name="orginal scrum">Takeuchi, H. and Nonaka, I., 1986. The new new product development game. Harvard business review, 64(1), pp.137-146./ref>		<ref name="orginal scrum">Takeuchi, H. and Nonaka, I., 1986. The new new product development game. Harvard business review, 64(1), pp.137-146.</ref>

	<ref name="workfront">Scrum Product Owner,” Available online: https://www.workfront.com/project-management/methodologies/scrum/product-owner#:~:text=What%20is%20a%20Scrum%20Product,marketplace%2C%20competitors%2C%20and%20trends.		<ref name="workfront">Scrum Product Owner,” Available online: https://www.workfront.com/project-management/methodologies/scrum/product-owner#:~:text=What%20is%20a%20Scrum%20Product,marketplace%2C%20competitors%2C%20and%20trends.
	</ref>		</ref>

	<ref name="manifesto">Scrum Product Owner,” Fowler, M. and Highsmith, J., 2001. The agile manifesto. Software development, 9(8), pp.28-35.		<ref name="manifesto">Scrum Product Owner,” Fowler, M. and Highsmith, J., 2001. The agile manifesto. Software development, 9(8), pp.28-35. </ref>
	</ref>

S184301: /* References */

2022-03-22T21:14:10Z

References

← Older revision		Revision as of 21:14, 22 March 2022
Line 153:		Line 153:
	=References=		=References=

	<references>		</references>

Peter Vilhelmsen: /* Developers */

2022-03-22T21:11:11Z

Developers

← Older revision		Revision as of 21:11, 22 March 2022
Line 40:		Line 40:
	One part of the Scrum team is Developers. Ken Scwaber and Jeff Sutherland describes developers as follows in their Scrum Guide: “Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.”<ref name="scrum guide"/>. In addition to that, they are responsible for making the product at the end of each sprint. You do not need any specific skill in order to become a Developer, since the skill requirement relies heavily on the objective. The competences and background of the Developers varies a lot, however, there are a few characteristics most great Developers should possess, for example, the ability to work together in teams. However, according to the Scrum guide developers are always responsible for:		One part of the Scrum team is Developers. Ken Scwaber and Jeff Sutherland describes developers as follows in their Scrum Guide: “Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.”<ref name="scrum guide"/>. In addition to that, they are responsible for making the product at the end of each sprint. You do not need any specific skill in order to become a Developer, since the skill requirement relies heavily on the objective. The competences and background of the Developers varies a lot, however, there are a few characteristics most great Developers should possess, for example, the ability to work together in teams. However, according to the Scrum guide developers are always responsible for:

	• Creating a plan for the Sprint, the Sprint Backlog;		• Creating a plan for the Sprint, the Sprint Backlog
	• Instilling quality by adhering to a Definition of Done;
			• Instilling quality by adhering to a Definition of Done

	• Adapting their plan each day toward the Sprint Goal; and,		• Adapting their plan each day toward the Sprint Goal; and,

	• Holding each other accountable as professionals. <ref name="scrum guide"/>		• Holding each other accountable as professionals. <ref name="scrum guide"/>

Peter Vilhelmsen: /* Product Owners */

2022-03-22T21:10:42Z

Product Owners

← Older revision		Revision as of 21:10, 22 March 2022
Line 53:		Line 53:

	- Defining the vision		- Defining the vision

	- Prioritizing the product backlog		- Prioritizing the product backlog

	- Taking an overview of development stages		- Taking an overview of development stages

	- Handling communications		- Handling communications

	- Knowing what the client needs		- Knowing what the client needs

	- Evaluating progress <ref name="workfront"/>		- Evaluating progress <ref name="workfront"/>

Peter Vilhelmsen: /* Product Owners */

2022-03-22T21:10:25Z

Product Owners

← Older revision		Revision as of 21:10, 22 March 2022
Line 47:		Line 47:
	===Product Owners===		===Product Owners===
	The product owner is often the key stakeholder of the project<ref name="workfront"/>. Their main purpose is ensuring the maximization of the value that the project intends to provide to the end customer. They do this by managing the product backlog which is an ordered list of the desired features the end product should have.		The product owner is often the key stakeholder of the project<ref name="workfront"/>. Their main purpose is ensuring the maximization of the value that the project intends to provide to the end customer. They do this by managing the product backlog which is an ordered list of the desired features the end product should have.
	Product owners often takes the perspective of the customer or consumer of the product. This customer centric perspective is meant to help ensure that the product actually delivers on the goals set in the beginning of the process. The product owner is the role within the Scrum framework that acts the most like what a project manager does in a traditional project group. It is fine for a product owner delegate work within the Scrum team, but the product owner is accountable of not only the daily executions of Scrum events but also the final product. A product owner is often a person with knowledge of both the business and technical side of the project and can therefore act as a mediator between developers with different backgrounds. It is also recommended that the product owner is someone with great leadership since the person is in charge of the entire Scrum team and the process. The Scrum guide also emphasizes the importance of their only being one single person as product owner within every Scrum team: “The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.”<ref name="scrum guide"/>. This also means that, in order for a product owner to be successful, the other members of the Scrum team must trust and respect the product owner decisions.
			Product owners often takes the perspective of the customer or consumer of the product. This customer centric perspective is meant to help ensure that the product actually delivers on the goals set in the beginning of the process. The product owner is the role within the Scrum framework that acts the most like what a project manager does in a traditional project group. It is fine for a product owner delegate work within the Scrum team, but the product owner is accountable of not only the daily executions of Scrum events but also the final product. A product owner is often a person with knowledge of both the business and technical side of the project and can therefore act as a mediator between developers with different backgrounds. It is also recommended that the product owner is someone with great leadership since the person is in charge of the entire Scrum team and the process. The Scrum guide also emphasizes the importance of their only being one single person as product owner within every Scrum team: “The Product Owner is one person, not a committee. The Product Owner may represent the needs of many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.”<ref name="scrum guide"/>. This also means that, in order for a product owner to be successful, the other members of the Scrum team must trust and respect the product owner decisions.

	The product owners key responsibilities can be summed up as follows:		The product owners key responsibilities can be summed up as follows:

	- Defining the vision		- Defining the vision
	- Prioritizing the product backlog		- Prioritizing the product backlog

Peter Vilhelmsen: /* Sprint Planning */

2022-03-22T21:09:54Z

Sprint Planning

← Older revision		Revision as of 21:09, 22 March 2022
Line 73:		Line 73:

	Sprint planning is the very first step of the sprint and kicks off the process. Before starting the sprint a clear goal needs to be set. In this event, the Scrum team has a discussion, facilitated by the product owner, about which items from the product backlog should be included in this sprints sprint backlog. When choosing the sprint goals, it is important to consider that they must be achievable within one sprint and how to actually reach them. To help with this discussion, the scrum guide provides three questions:		Sprint planning is the very first step of the sprint and kicks off the process. Before starting the sprint a clear goal needs to be set. In this event, the Scrum team has a discussion, facilitated by the product owner, about which items from the product backlog should be included in this sprints sprint backlog. When choosing the sprint goals, it is important to consider that they must be achievable within one sprint and how to actually reach them. To help with this discussion, the scrum guide provides three questions:


	Why is this Sprint valuable?		Why is this Sprint valuable?

	What can be Done this Sprint?		What can be Done this Sprint?

	How will the chosen work get done?<ref name="scrum guide"/>		How will the chosen work get done?<ref name="scrum guide"/>