SCRUM - An Agile Project Management Framework - Revision history

MadsH at 19:38, 28 February 2021

2021-02-28T19:38:56Z

MadsH at 19:30, 28 February 2021

2021-02-28T19:30:30Z

← Older revision		Revision as of 19:30, 28 February 2021
Line 4:		Line 4:

	To overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly, the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.		To overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly, the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.
	~~==Application of Scrum ==~~
	=== The agile foundation for Scrum ===		=== The agile foundation for Scrum ===

Line 27:		Line 27:
	The 12 principles can be read in full in the Agile Manifesto<ref>Agilemanifesto: The 12 Agile Principles https://agilemanifesto.org/principles (Visited 20/02/2020) </ref>. Even though the founders of Scrum signed the agile manifesto, it is a common misunderstanding that Scrum and agile are the same thing. As mentioned above, agile is a set of values and principles. To adopt an agile way of working, the Scrum team must work under these principles and beliefs. The implementation of Scrum can push you towards a more agile way of working but cannot do it alone<ref name = "fowler"> Fowler. F. M. (2018) Navigating hybrid scrum environments, Apress, Sunnyvale, CA. Retrieved from https://doi.org/10.1007/978-1-4842-4164-6 </ref>.		The 12 principles can be read in full in the Agile Manifesto<ref>Agilemanifesto: The 12 Agile Principles https://agilemanifesto.org/principles (Visited 20/02/2020) </ref>. Even though the founders of Scrum signed the agile manifesto, it is a common misunderstanding that Scrum and agile are the same thing. As mentioned above, agile is a set of values and principles. To adopt an agile way of working, the Scrum team must work under these principles and beliefs. The implementation of Scrum can push you towards a more agile way of working but cannot do it alone<ref name = "fowler"> Fowler. F. M. (2018) Navigating hybrid scrum environments, Apress, Sunnyvale, CA. Retrieved from https://doi.org/10.1007/978-1-4842-4164-6 </ref>.

	==~~How to organize for~~ Scrum==		==Application of Scrum ==
	====The Scrum Team====		====The Scrum Team====

Line 52:		Line 52:
	The Scrum master will help the Product Owner, as requested to, find techniques and tools for effective product goal definition, management of the product backlog, and stakeholder collaboration. Additionally, the Scrum master is involved with the rest of the organization to make sure they understand Scrum and the consequences of adoption. This will often include training and implementation of Scrum in the organization. Furthermore, the Scrum Master will often be involved in conflicts or challenges between the stakeholders and the Scrum team <ref name="scrum-guide" />.		The Scrum master will help the Product Owner, as requested to, find techniques and tools for effective product goal definition, management of the product backlog, and stakeholder collaboration. Additionally, the Scrum master is involved with the rest of the organization to make sure they understand Scrum and the consequences of adoption. This will often include training and implementation of Scrum in the organization. Furthermore, the Scrum Master will often be involved in conflicts or challenges between the stakeholders and the Scrum team <ref name="scrum-guide" />.

	== ~~How to perform Scrum~~ ==		=== The iterative process ===

	~~Project management, as presented by the PMBOK standard<ref name~~ = ~~"PMBOK" /> splits a project into 5 phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing. These phases can be compared to the way work is organized in the Scrum framework.~~

	Considering figure 2, the initiating phase can be compared to the process that will happen regarding the Backlog. In this process, the Product Owner will receive and gather inputs from the End-users, Customers, Team, and other relevant stakeholders. But instead of using these inputs to create the full plan of the project, the Product Owner will prioritize them in the product backlog. The product owner will then together with the development team begin the planning phase for the upcoming sprint; here the inputs will be further refined and receive a time estimate. This phase will also include a definition of a Sprint goal, the objective which the team aims to achieve during the sprint. Hereafter, the Executing process will follow; this will in Scrum terminology, be considered the sprint. This is the part where the actual work will be completed, and the sprint goal is hopefully obtained – the Scrum team is self-managed and will get the work done in the manner that works best for them. Considering the task of monitoring and controlling the progress, the Scrum team will benefit from the manageable number of tasks, as they only plan work for a short period of time and secondly a part of the sprint planning included the task of estimating time for the task, which can be used to make a burndown chart of keeping track of expected progress for the team. Lastly is the closing phase of the project, which is the part where the sprint review is performed, and the increment pushed to the end-users to create instant business value. What then makes the difference to working with Scrum is the continuous repetition of this cycle, as illustrated in figure 2. The aim is to constantly improve and keep on track with requirements and priorities as they change. To gain a better understanding of the events and artifact, an explanation of each of them follow.		Project management, as presented by the PMBOK standard<ref name = "PMBOK" /> splits a project into 5 phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing. These phases can be compared to the way work is organized in the Scrum framework. Considering figure 2, the initiating phase can be compared to the process that will happen regarding the Backlog. In this process, the Product Owner will receive and gather inputs from the End-users, Customers, Team, and other relevant stakeholders. But instead of using these inputs to create the full plan of the project, the Product Owner will prioritize them in the product backlog. The product owner will then together with the development team begin the planning phase for the upcoming sprint; here the inputs will be further refined and receive a time estimate. This phase will also include a definition of a Sprint goal, the objective which the team aims to achieve during the sprint. Hereafter, the Executing process will follow; this will in Scrum terminology, be considered the sprint. This is the part where the actual work will be completed, and the sprint goal is hopefully obtained – the Scrum team is self-managed and will get the work done in the manner that works best for them. Considering the task of monitoring and controlling the progress, the Scrum team will benefit from the manageable number of tasks, as they only plan work for a short period of time and secondly a part of the sprint planning included the task of estimating time for the task, which can be used to make a burndown chart of keeping track of expected progress for the team. Lastly is the closing phase of the project, which is the part where the sprint review is performed, and the increment pushed to the end-users to create instant business value. What then makes the difference to working with Scrum is the continuous repetition of this cycle, as illustrated in figure 2. The aim is to constantly improve and keep on track with requirements and priorities as they change. To gain a better understanding of the events and artifact, an explanation of each of them follow.

	=== Artifacts & Events ===		=== Artifacts & Events ===

MadsH at 19:25, 28 February 2021

2021-02-28T19:25:33Z

← Older revision		Revision as of 19:25, 28 February 2021
Line 4:		Line 4:

	To overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly, the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.		To overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly, the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.
	=Application of Scrum =		==Application of Scrum ==
	=== The agile foundation for Scrum ===		=== The agile foundation for Scrum ===

MadsH at 19:25, 28 February 2021

2021-02-28T19:25:03Z

← Older revision		Revision as of 19:25, 28 February 2021
Line 1:		Line 1:
	''Developed by MH''		''Developed by Mads Hønberg''

	Scrum is an agile project management framework primarily used for software development. It is based on short work cycles of 2-4 weeks(sprints) to create incremental business value. The workforce is organized in small teams, with cross-disciplinary skills and knowledge, who receives continuous feedback from key stakeholders after each sprint. The constant feedback and dialogue with stakeholders are key to delivering true business value and keeping the project on track. Jeff Sutherland and Ken Schwaber created Scrum, both ex-soldiers from the Vietnam war, which later both became a part of the software industry and had a shared frustration with late deliveries, poor quality, and user dissatisfaction <ref> Scrumdesk: The history of Scrum https://www.scrumdesk.com/the-history-of-scrum-how-when-and-why/ (Visited 20/02/2021) </ref>. They were inspired to create Scrum by Hirotaka Takeuchi and Ikujiro Nonaka, who compared a new development approach to the movement of a rugby team, in their paper “The New New Product Development Game”<ref> The New New Product Development Game by Hirotaka Takeuchi and Ikujiro Nonaka https://hbr.org/1986/01/the-new-new-product-development-game (Visited 20/02/2021)</ref>, this became the inspiration for the roles and team. They found the inspiration for the values and management of the teams in the theory of Empirical Process Control<ref>Scrum.org: The Three Pillars of Empiricism by Hiren Doshi https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum (Visited 27/02/20) </ref>, which builds on Transparency, Inspection, and Adaptation. The article will focus on what Scrum is and why it can benefit software development compared to the traditional waterfall development framework. This will include an overview of Scrum roles, events & artifacts, followed by sections on benefits & limitations.		Scrum is an agile project management framework primarily used for software development. It is based on short work cycles of 2-4 weeks(sprints) to create incremental business value. The workforce is organized in small teams, with cross-disciplinary skills and knowledge, who receives continuous feedback from key stakeholders after each sprint. The constant feedback and dialogue with stakeholders are key to delivering true business value and keeping the project on track. Jeff Sutherland and Ken Schwaber created Scrum, both ex-soldiers from the Vietnam war, which later both became a part of the software industry and had a shared frustration with late deliveries, poor quality, and user dissatisfaction <ref> Scrumdesk: The history of Scrum https://www.scrumdesk.com/the-history-of-scrum-how-when-and-why/ (Visited 20/02/2021) </ref>. They were inspired to create Scrum by Hirotaka Takeuchi and Ikujiro Nonaka, who compared a new development approach to the movement of a rugby team, in their paper “The New New Product Development Game”<ref> The New New Product Development Game by Hirotaka Takeuchi and Ikujiro Nonaka https://hbr.org/1986/01/the-new-new-product-development-game (Visited 20/02/2021)</ref>, this became the inspiration for the roles and team. They found the inspiration for the values and management of the teams in the theory of Empirical Process Control<ref>Scrum.org: The Three Pillars of Empiricism by Hiren Doshi https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum (Visited 27/02/20) </ref>, which builds on Transparency, Inspection, and Adaptation. The article will focus on what Scrum is and why it can benefit software development compared to the traditional waterfall development framework. This will include an overview of Scrum roles, events & artifacts, followed by sections on benefits & limitations.

MadsH at 19:24, 28 February 2021

2021-02-28T19:24:51Z

← Older revision		Revision as of 19:24, 28 February 2021
Line 91:		Line 91:
	[[File:Incremental_mh.PNG\|50px\|frame\|Figure 3. Incremental deliveries vs. One Final Delivery. Illustrated with the example of a car, in reality, it would be very costly to develop a car with incremental deliveries – but it works nicely as an illustration for an incremental process. Inspired by Arijit Sarbagna, Dzone.com<ref>Dzone.com, Arijit Sarbagna. https://dzone.com/articles/scrum-is-not-mini-waterfall (Visited 21/02/2021) </ref>]]		[[File:Incremental_mh.PNG\|50px\|frame\|Figure 3. Incremental deliveries vs. One Final Delivery. Illustrated with the example of a car, in reality, it would be very costly to develop a car with incremental deliveries – but it works nicely as an illustration for an incremental process. Inspired by Arijit Sarbagna, Dzone.com<ref>Dzone.com, Arijit Sarbagna. https://dzone.com/articles/scrum-is-not-mini-waterfall (Visited 21/02/2021) </ref>]]

	At the end of the sprint, the scrum team has in the optimal scenario, completed all the tasks from the sprint backlog~~, even though~~ this is not the case, the sprint will still be complete as the timebox is coming to an end<ref name="scrum-guide" />. The tasks that have not been completed will have to become a part of the backlog and go through the prioritization phase again to make it to the next sprint's backlog. The tasks which have resulted in changes, new features, or other relevant software updates to present for the stakeholders will be presented on the Sprint Review. Increments are a part of the agile way of working, where the focus is to make constant improvements while stakeholders are informed and provide continuous feedback. This can be seen as a process where features are added after the software is already taken into use, this is also known as Continuous Development/Continuous Integration<ref>Infoworld: What is CI/CD https://www.infoworld.com/article/3271126/what-is-cicd-continuous-integration-and-continuous-delivery-explained.html (Visited 27/02/2021)</ref>. This is mainly used for software, but to make it more illustrative, it is showed with the example of car development in figure 3. Where incremental updates will focus on adding value, the first increment will be to make a product that can drive, then something more comfortable or faster, determined by what creates business value. In traditional waterfall development, the focus will often be to finish the wheels, then the cabin, and so on. This might seem more effective but have a high risk of not fulfilling the stakeholders' demand, as the solution cannot be adjusted while developed. Remember, the car example is only for illustrative matters; the focus is on software development.		At the end of the sprint, the scrum team has in the optimal scenario, completed all the tasks from the sprint backlog. If this is not the case, the sprint will still be complete as the timebox is coming to an end<ref name="scrum-guide" />. The tasks that have not been completed will have to become a part of the backlog and go through the prioritization phase again to make it to the next sprint's backlog. The tasks which have resulted in changes, new features, or other relevant software updates to present for the stakeholders will be presented on the Sprint Review. Increments are a part of the agile way of working, where the focus is to make constant improvements while stakeholders are informed and provide continuous feedback. This can be seen as a process where features are added after the software is already taken into use, this is also known as Continuous Development/Continuous Integration<ref>Infoworld: What is CI/CD https://www.infoworld.com/article/3271126/what-is-cicd-continuous-integration-and-continuous-delivery-explained.html (Visited 27/02/2021)</ref>. This is mainly used for software, but to make it more illustrative, it is showed with the example of car development in figure 3. Where incremental updates will focus on adding value, the first increment will be to make a product that can drive, then something more comfortable or faster, determined by what creates business value. In traditional waterfall development, the focus will often be to finish the wheels, then the cabin, and so on. This might seem more effective but have a high risk of not fulfilling the stakeholders' demand, as the solution cannot be adjusted while developed. Remember, the car example is only for illustrative matters; the focus is on software development.

	==== Sprint Review ====		==== Sprint Review ====

MadsH at 19:21, 28 February 2021

2021-02-28T19:21:23Z

Show changes

MadsH at 17:07, 28 February 2021

2021-02-28T17:07:13Z

← Older revision		Revision as of 17:07, 28 February 2021
Line 9:		Line 9:
	[[File:waterfall_mh.PNG\|x300px\|frame\|Figure 1. A comparison of the Waterfall and Scrum framework, showing the different approaches to delivering including the project phases. Inspired by pmi-macedonia.mk<ref>Project Management Institute, Macedonia: Scrum or waterfall what is the difference? https://pmi-macedonia.mk/event/scrum-or-waterfall-whats-the-difference/ (Visited 27/02/2020)</ref>]]		[[File:waterfall_mh.PNG\|x300px\|frame\|Figure 1. A comparison of the Waterfall and Scrum framework, showing the different approaches to delivering including the project phases. Inspired by pmi-macedonia.mk<ref>Project Management Institute, Macedonia: Scrum or waterfall what is the difference? https://pmi-macedonia.mk/event/scrum-or-waterfall-whats-the-difference/ (Visited 27/02/2020)</ref>]]

	Scrum is widely used due to its efficient framework for organizing a team and their tasks in order to deliver continuous business value. The implementation of Scrum is often driven by the wish to become more responsive to changing demands from stakeholders. With a technological scene changing faster than ever, there is an increasing need to use a development process where priorities and requirements can be changed during the development. Software development was previously often based on the linear waterfall model<ref> Bibik I. (2018) How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_1</ref> where everything is signed of and specified before the project is started, see figure 1. When developing software, the timeline will often be multiple years, in this period requirements and priorities will often change. In contrast to this approach, there is Scrum, which is based on short sprints, where the most value-adding tasks from the backlog are completed in self-organized teams and immediately shared with the end-user to get continuous feedback. Instead of one final delivery at the end, the idea of Scrum is to develop small incremental updates, with flexibility for changes, which in small steps will fulfill the scope. Scrum also includes the phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing, all known from the standard for project management, PMBOK Guide <ref name = "PMBOK"> Guide to the Project Management Body of Knowledge (PMBOK Guide) 6th edition</ref>. Instead of performing the phases one time like the waterfall model, the phases will be continuously repeated in each sprint, to make it possible for adjustments and reprioritization, this will often be considered as the ability to being agile.		Scrum is widely used due to its efficient framework for organizing a team and their tasks in order to deliver continuous business value. The implementation of Scrum is often driven by the wish to become more responsive to changing demands from stakeholders. With a technological scene changing faster than ever, there is an increasing need to use a development process where priorities and requirements can be changed during the development. Software development was previously often based on the linear waterfall model<ref> Bibik I. (2018) How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_1</ref> where everything is signed of and specified before the project is started, see figure 1. When developing software, the timeline will often be multiple years, in this period requirements and priorities will often change. In contrast to this approach, there is Scrum, which is based on short sprints, where the most value-adding tasks from the backlog are completed in self-organized teams and immediately shared with the end-user to get continuous feedback. Instead of one final delivery at the end, the idea of Scrum is to develop small incremental updates, with flexibility for changes, which in small steps will fulfill the scope. Scrum also includes the phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing, all known from the standard for project management, PMBOK Guide <ref name = "PMBOK"> Project Management Institute (2017) Guide to the Project Management Body of Knowledge (PMBOK Guide) 6th edition. Retrieved from https://app-knovel-com.proxy.findit.dtu.dk/s.v?4QJeKzna </ref>. Instead of performing the phases one time like the waterfall model, the phases will be continuously repeated in each sprint, to make it possible for adjustments and reprioritization, this will often be considered as the ability to being agile.

	The Scrum framework is based on the 12 agile principles, which were signed by the 2 founders of Scrum together with 15 other prominent individuals, all frustrated with traditional software development. The 12 Agile principles are based on 4 core values<ref name = "manifesto">Agilemanifesto: Values of Agile Software Development https://agilemanifesto.org/ (Visited 20/02/2021)</ref>:		The Scrum framework is based on the 12 agile principles, which were signed by the 2 founders of Scrum together with 15 other prominent individuals, all frustrated with traditional software development. The 12 Agile principles are based on 4 core values<ref name = "manifesto">Agilemanifesto: Values of Agile Software Development https://agilemanifesto.org/ (Visited 20/02/2021)</ref>:

MadsH at 17:02, 28 February 2021

2021-02-28T17:02:37Z

← Older revision		Revision as of 17:02, 28 February 2021
Line 30:		Line 30:
	====The Scrum Team====		====The Scrum Team====

	The implementation of Scrum will lead to a new way of organizing the staff in order to make sure the roles of the Scrum team can be fulfilled<ref> Atlassian: What is Scrum? https://www.atlassian.com/agile/scrum (Visited 21/02/2021)</ref>. The definition of the Scrum team follows the Scrum guide<ref name = "scrum-guide"> The ~~2020~~ Scrum Guide https://www.scrumguides.org/scrum-guide.html </ref>. A Scrum team is a small team of professionals, consisting of one Scrum Master, one Product Owner, and Developers, in total they should not exceed 10 individuals. The team has no sub-teams or hierarchy and works towards the same product goal. A Scrum team is self-managed and has cross-functional roles and knowledge to make sure the team has the skills to create business value in each sprint<ref name="scrum-guide"/>. In traditional software development, there is a Product Manager who will both be organizing and assigning the tasks among the developers, which also means the Product Manager will be held responsible for the results. In the Scrum framework, the team is self-managed and thereby responsible for both distributing the work among each other, but also for developing the right thing. In this way, the accountability is placed at the developers, which are also the ones with the capability of developing the software. The scrum framework trust that when the developers have the responsibility, they will produce a better product<ref name = "fowler"/>.		The implementation of Scrum will lead to a new way of organizing the staff in order to make sure the roles of the Scrum team can be fulfilled<ref> Atlassian: What is Scrum? https://www.atlassian.com/agile/scrum (Visited 21/02/2021)</ref>. The definition of the Scrum team follows the Scrum guide<ref name = "scrum-guide"> Schwaber K. & Sutherland J. (2020) The Scrum Guide. Retrived from https://www.scrumguides.org/scrum-guide.html </ref>. A Scrum team is a small team of professionals, consisting of one Scrum Master, one Product Owner, and Developers, in total they should not exceed 10 individuals. The team has no sub-teams or hierarchy and works towards the same product goal. A Scrum team is self-managed and has cross-functional roles and knowledge to make sure the team has the skills to create business value in each sprint<ref name="scrum-guide"/>. In traditional software development, there is a Product Manager who will both be organizing and assigning the tasks among the developers, which also means the Product Manager will be held responsible for the results. In the Scrum framework, the team is self-managed and thereby responsible for both distributing the work among each other, but also for developing the right thing. In this way, the accountability is placed at the developers, which are also the ones with the capability of developing the software. The scrum framework trust that when the developers have the responsibility, they will produce a better product<ref name = "fowler"/>.

	====Product Owner====		====Product Owner====

MadsH at 16:59, 28 February 2021

2021-02-28T16:59:41Z

← Older revision		Revision as of 16:59, 28 February 2021
Line 1:		Line 1:
	''Developed by MH''		''Developed by MH''

	Scrum is an agile project management framework especially popular for software development. It is based on short work cycles of 2-4 weeks(sprints) with the aim of creating incremental business value. The workforce is organized in small teams, with cross-disciplinary skills and knowledge, who receives continuous feedback from key stakeholders after each sprint. The constant feedback and dialogue with stakeholders are key to delivering true business value and keeping the project on track. Scrum was created by Jeff Sutherland and Ken Schwaber, both ex-soldiers from the Vietnam war, which later both became a part of the software industry and had a shared frustration with late deliveries, poor quality, and user dissatisfaction <ref> Scrumdesk: The history of Scrum https://www.scrumdesk.com/the-history-of-scrum-how-when-and-why/ (Visited 20/02/2021) </ref>. They were inspired to create Scrum by Hirotaka Takeuchi and Ikujiro Nonaka, who compared a new development approach to the movement of a rugby team, in their paper “The New New Product Development Game”<ref> The New New Product Development Game by Hirotaka Takeuchi and Ikujiro Nonaka https://hbr.org/1986/01/the-new-new-product-development-game (Visited 20/02/2021)</ref>, this became the inspiration for the roles and team. They found the inspiration for the values and management of the teams in the theory of Empirical Process Control<ref>Scrum.org: The Three Pillars of Empiricism by Hiren Doshi https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum (Visited 27/02/20) </ref>, which builds on Transparency, Inspection, and Adaptation. The article will focus on what scrum is and why it can be beneficial for software development compared to the traditional waterfall development method. This will include an overview of Scrum roles, events & artifacts, followed by sections on benefits & limitations.		Scrum is an agile project management framework especially popular for software development. It is based on short work cycles of 2-4 weeks(sprints) with the aim of creating incremental business value. The workforce is organized in small teams, with cross-disciplinary skills and knowledge, who receives continuous feedback from key stakeholders after each sprint. The constant feedback and dialogue with stakeholders are key to delivering true business value and keeping the project on track. Scrum was created by Jeff Sutherland and Ken Schwaber, both ex-soldiers from the Vietnam war, which later both became a part of the software industry and had a shared frustration with late deliveries, poor quality, and user dissatisfaction <ref> Scrumdesk: The history of Scrum https://www.scrumdesk.com/the-history-of-scrum-how-when-and-why/ (Visited 20/02/2021) </ref>. They were inspired to create Scrum by Hirotaka Takeuchi and Ikujiro Nonaka, who compared a new development approach to the movement of a rugby team, in their paper “The New New Product Development Game”<ref> The New New Product Development Game by Hirotaka Takeuchi and Ikujiro Nonaka https://hbr.org/1986/01/the-new-new-product-development-game (Visited 20/02/2021)</ref>, this became the inspiration for the roles and team. They found the inspiration for the values and management of the teams in the theory of Empirical Process Control<ref>Scrum.org: The Three Pillars of Empiricism by Hiren Doshi https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum (Visited 27/02/20) </ref>, which builds on Transparency, Inspection, and Adaptation. The article will focus on what scrum is and why it can be beneficial for software development compared to the traditional waterfall development method. This will include an overview of Scrum roles, events & artifacts, followed by sections on benefits & limitations.

	In order to overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.		In order to overcome the traditional challenges of software development, which builds on the assumption of constant demands and full sign of on requirements before beginning, a more agile approach, Scrum, has gained its justification. The ability of Scrum to cope with the reality of modern software development with ever-changing demands, the challenge of capturing all requirements from the beginning, the acceptance of failure, and the need for testing while developing, but most importantly the acceptance of changing preferences and requirements from the client as the development evolves, has made it a popular framework for software development.
Line 11:		Line 11:
	Scrum is widely used due to its efficient framework for organizing a team and their tasks in order to deliver continuous business value. The implementation of Scrum is often driven by the wish to become more responsive to changing demands from stakeholders. With a technological scene changing faster than ever, there is an increasing need to use a development process where priorities and requirements can be changed during the development. Software development was previously often based on the linear waterfall model<ref> Bibik I. (2018) How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_1</ref> where everything is signed of and specified before the project is started, see figure 1. When developing software, the timeline will often be multiple years, in this period requirements and priorities will often change. In contrast to this approach, there is Scrum, which is based on short sprints, where the most value-adding tasks from the backlog are completed in self-organized teams and immediately shared with the end-user to get continuous feedback. Instead of one final delivery at the end, the idea of Scrum is to develop small incremental updates, with flexibility for changes, which in small steps will fulfill the scope. Scrum also includes the phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing, all known from the standard for project management, PMBOK Guide <ref name = "PMBOK"> Guide to the Project Management Body of Knowledge (PMBOK Guide) 6th edition</ref>. Instead of performing the phases one time like the waterfall model, the phases will be continuously repeated in each sprint, to make it possible for adjustments and reprioritization, this will often be considered as the ability to being agile.		Scrum is widely used due to its efficient framework for organizing a team and their tasks in order to deliver continuous business value. The implementation of Scrum is often driven by the wish to become more responsive to changing demands from stakeholders. With a technological scene changing faster than ever, there is an increasing need to use a development process where priorities and requirements can be changed during the development. Software development was previously often based on the linear waterfall model<ref> Bibik I. (2018) How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_1</ref> where everything is signed of and specified before the project is started, see figure 1. When developing software, the timeline will often be multiple years, in this period requirements and priorities will often change. In contrast to this approach, there is Scrum, which is based on short sprints, where the most value-adding tasks from the backlog are completed in self-organized teams and immediately shared with the end-user to get continuous feedback. Instead of one final delivery at the end, the idea of Scrum is to develop small incremental updates, with flexibility for changes, which in small steps will fulfill the scope. Scrum also includes the phases: Initiating, Planning, Executing, Monitoring & Controlling, and Closing, all known from the standard for project management, PMBOK Guide <ref name = "PMBOK"> Guide to the Project Management Body of Knowledge (PMBOK Guide) 6th edition</ref>. Instead of performing the phases one time like the waterfall model, the phases will be continuously repeated in each sprint, to make it possible for adjustments and reprioritization, this will often be considered as the ability to being agile.

	The Scrum framework is based on the 12 agile principles, which were signed by the 2 founders of Scrum together with 15 other prominent individuals, all frustrated with traditional software development. The 12 Agile principles are based on 4 core values<ref name = "manifesto">Values of Agile Software Development https://agilemanifesto.org/ (Visited 20/02/2021)</ref>:		The Scrum framework is based on the 12 agile principles, which were signed by the 2 founders of Scrum together with 15 other prominent individuals, all frustrated with traditional software development. The 12 Agile principles are based on 4 core values<ref name = "manifesto">Agilemanifesto: Values of Agile Software Development https://agilemanifesto.org/ (Visited 20/02/2021)</ref>:

	; Individuals and Interactions over Processes and Tools		; Individuals and Interactions over Processes and Tools
Line 25:		Line 25:
	: Instead of seeing a change as an expense, changes should be welcomed and incorporated, to create additional business value.		: Instead of seeing a change as an expense, changes should be welcomed and incorporated, to create additional business value.

	The 12 principles can be read in full in the Agile Manifesto<ref> The 12 Agile Principles https://agilemanifesto.org/principles (Visited 20/02/2020) </ref>. Even though the founders of Scrum signed the agile manifesto, it is a common misunderstanding that Scrum and agile are the same thing. As mentioned above, agile is a set of values and principles. In order to adopt an agile way of working, the members of the scrum team will need to work under these principles and beliefs. The implementation of Scrum can push you towards a more agile way of working but cannot do it alone<ref name = "fowler"> Fowler. F. M. (2018) Navigating hybrid scrum environments, Apress, Sunnyvale, CA. Retrieved from https://doi.org/10.1007/978-1-4842-4164-6 </ref>.		The 12 principles can be read in full in the Agile Manifesto<ref>Agilemanifesto: The 12 Agile Principles https://agilemanifesto.org/principles (Visited 20/02/2020) </ref>. Even though the founders of Scrum signed the agile manifesto, it is a common misunderstanding that Scrum and agile are the same thing. As mentioned above, agile is a set of values and principles. In order to adopt an agile way of working, the members of the scrum team will need to work under these principles and beliefs. The implementation of Scrum can push you towards a more agile way of working but cannot do it alone<ref name = "fowler"> Fowler. F. M. (2018) Navigating hybrid scrum environments, Apress, Sunnyvale, CA. Retrieved from https://doi.org/10.1007/978-1-4842-4164-6 </ref>.

	==How to organize for Scrum==		==How to organize for Scrum==
Line 41:		Line 41:
	* Execution of Sprint planning and Sprint Review sessions		* Execution of Sprint planning and Sprint Review sessions

	The product owner will often be the “middleman” between the business and developers and must be able to find compromises. Strong communication skills, negotiation skills, proactivity, diplomatic, and result-driven will often be favorable personality traits for a product owner <ref> Advanz: Scrum Product Owner https://advanz.dk/blog/scrum-product-owner/ </ref>.		The product owner will often be the “middleman” between the business and developers and must be able to find compromises. Strong communication skills, negotiation skills, proactivity, diplomatic, and result-driven will often be favorable personality traits for a product owner <ref> Advanz: Scrum Product Owner https://advanz.dk/blog/scrum-product-owner/ (Visited 20/02/2021) </ref>.

	==== Developers ====		==== Developers ====

	The developers are the ones who will produce the real work of each sprint. Atlassian, a key tech provider for many software companies using Scrum, presents the typical skill-set of the developers, like design, UX, programming, testing, and deployment <ref> Atlassian: Scrum Roles https://www.atlassian.com/agile/scrum/roles </ref>. The developers hold the responsibility of estimating and planning the tasks for the sprint based on the sprint backlog. They make the definition of when a task can be considered “done”. Lastly, the developers are also accountable for daily adjustments of the sprint planning as they gain knowledge and learn about possible issues, in order to obtain the sprint goal <ref name="scrum-guide" />.		The developers are the ones who will produce the real work of each sprint. Atlassian, a key tech provider for many software companies using Scrum, presents the typical skill-set of the developers, like design, UX, programming, testing, and deployment <ref> Atlassian: Scrum Roles https://www.atlassian.com/agile/scrum/roles (Visited 20/02/2021) </ref>. The developers hold the responsibility of estimating and planning the tasks for the sprint based on the sprint backlog. They make the definition of when a task can be considered “done”. Lastly, the developers are also accountable for daily adjustments of the sprint planning as they gain knowledge and learn about possible issues, in order to obtain the sprint goal <ref name="scrum-guide" />.

	==== Scrum Master ====		==== Scrum Master ====
Line 129:		Line 129:
	: The Agile Manifesto is signed by 17 individuals frustrated with traditional software development, including Ken Schwaber and Jeff Sutherland the originators of Scrum. All 17 individuals working within or around software development. The agile manifesto includes 12 principles and 4 values, to reduce the challenges of software development by making it more agile. Values with are important to incorporate to obtain the full advantage of Scrum.		: The Agile Manifesto is signed by 17 individuals frustrated with traditional software development, including Ken Schwaber and Jeff Sutherland the originators of Scrum. All 17 individuals working within or around software development. The agile manifesto includes 12 principles and 4 values, to reduce the challenges of software development by making it more agile. Values with are important to incorporate to obtain the full advantage of Scrum.

	; Navigating Hybrid Scrum Environments< ref name = "fowler" />		; Navigating Hybrid Scrum Environments<ref name = "fowler"/>
	: There are many books describing Scrum, the roles, artifacts and events. This book takes is a steep deeper and tries to answer the question why. This will give you a much better understanding of the reasons for the different roles, artefacts and event. The highlight of the book is the focus on why the self-management and cross-disciplinary teams are so important for the success of Scrum and why it is challenging to scale these principles. The book is written by Frederik M. Fowler who have worked as software developer for more than 35 years and today is the highest-level certified Scrum Master.		: There are many books describing Scrum, the roles, artifacts and events. This book takes is a steep deeper and tries to answer the question why. This will give you a much better understanding of the reasons for the different roles, artefacts and event. The highlight of the book is the focus on why the self-management and cross-disciplinary teams are so important for the success of Scrum and why it is challenging to scale these principles. The book is written by Frederik M. Fowler who have worked as software developer for more than 35 years and today is the highest-level certified Scrum Master.

MadsH at 16:55, 28 February 2021

2021-02-28T16:55:08Z

← Older revision		Revision as of 16:55, 28 February 2021
Line 131:		Line 131:
	; Navigating Hybrid Scrum Environments< ref name = "fowler" />		; Navigating Hybrid Scrum Environments< ref name = "fowler" />
	: There are many books describing Scrum, the roles, artifacts and events. This book takes is a steep deeper and tries to answer the question why. This will give you a much better understanding of the reasons for the different roles, artefacts and event. The highlight of the book is the focus on why the self-management and cross-disciplinary teams are so important for the success of Scrum and why it is challenging to scale these principles. The book is written by Frederik M. Fowler who have worked as software developer for more than 35 years and today is the highest-level certified Scrum Master.		: There are many books describing Scrum, the roles, artifacts and events. This book takes is a steep deeper and tries to answer the question why. This will give you a much better understanding of the reasons for the different roles, artefacts and event. The highlight of the book is the focus on why the self-management and cross-disciplinary teams are so important for the success of Scrum and why it is challenging to scale these principles. The book is written by Frederik M. Fowler who have worked as software developer for more than 35 years and today is the highest-level certified Scrum Master.

			=== References ===

			<references />