SCRUM - A Project Management Framework - Revision history

S165111: /* References */

2021-02-28T17:58:05Z

References

← Older revision		Revision as of 17:58, 28 February 2021
Line 180:		Line 180:

	[[Category:Project Management]]		[[Category:Project Management]]
	~~[[Category:Agile]]~~

S165111: /* References */

2021-02-28T17:57:58Z

References

← Older revision		Revision as of 17:57, 28 February 2021
Line 180:		Line 180:

	[[Category:Project Management]]		[[Category:Project Management]]
	[[Category:~~Scrum~~]]		[[Category:Agile]]

S165111: /* References */

2021-02-28T17:57:33Z

References

← Older revision		Revision as of 17:57, 28 February 2021
Line 179:		Line 179:
	<references/>		<references/>

	[[Category:Project Management,Scrum]]		[[Category:Project Management]]
			[[Category:Scrum]]

S165111: /* References */

2021-02-28T17:57:10Z

References

← Older revision		Revision as of 17:57, 28 February 2021
Line 179:		Line 179:
	<references/>		<references/>

	[[Category:Project Management~~][Category:~~Scrum~~][Category:Agile~~]]		[[Category:Project Management,Scrum]]

S165111: /* References */

2021-02-28T17:56:53Z

References

← Older revision		Revision as of 17:56, 28 February 2021
Line 179:		Line 179:
	<references/>		<references/>

	[[Category:Project Management]]		[[Category:Project Management][Category:Scrum][Category:Agile]]

S165111: /* Scrum Artifacts */

2021-02-28T17:54:26Z

Scrum Artifacts

← Older revision		Revision as of 17:54, 28 February 2021
Line 120:		Line 120:
	[[File:Kanban1.png]] [[File:Burndown1.png]]		[[File:Kanban1.png]] [[File:Burndown1.png]]

	''Figure 2: A Kanban board to keep track of work tasks in each Sprint (own figure based on ~~Porter2017~~<ref name="kanban"></ref>).'' ''Figure 3: A Burndown Chart to visualize the remaining work in the Sprint (own figure based on McKenna, Dave<ref name="ArtofScrum"> </ref>(p.86))		''Figure 2: A Kanban board to keep track of work tasks in each Sprint (own figure based on Porter (2017)<ref name="kanban"></ref>).'' ''Figure 3: A Burndown Chart to visualize the remaining work in the Sprint (own figure based on McKenna, Dave<ref name="ArtofScrum"> </ref>(p.86))

	'''Increment'''		'''Increment'''

S165111: /* Annotated Bibliography */

2021-02-28T17:53:04Z

Annotated Bibliography

← Older revision		Revision as of 17:53, 28 February 2021
Line 169:		Line 169:
	'''3. The Art of Scrum (2016) How Scrum Masters Bind Dev Teams and Unleash Agility. Dave McKenna, Apress, Berkeley, CA. Retrieved from https://doi-org.proxy.findit.dtu.dk/10.1007/978-1-4842-2277-5'''		'''3. The Art of Scrum (2016) How Scrum Masters Bind Dev Teams and Unleash Agility. Dave McKenna, Apress, Berkeley, CA. Retrieved from https://doi-org.proxy.findit.dtu.dk/10.1007/978-1-4842-2277-5'''

	Dave McKenna is an experienced Scrum Master and has written this book with focus on the Scrum Master's perspective. It gives valuable and practical insights into how Scrum is applied in real life. This reference is relevant for both new users of Scrum to get a practical understanding of Scrum but also for more experienced individuals who wish to broaden their knowledge. It is written with a focus on story telling from McKenna’s own life and he provides down to earth examples from his everyday life. This makes it less academic to read but still provides a lot of valuable insights.		Dave McKenna is an experienced Scrum Master and has written this book with focus on the Scrum Master's perspective. It gives valuable and practical insights into how Scrum is applied in real life. This reference is relevant for both new users of Scrum to get a practical understanding of Scrum but also for more experienced individuals who wish to broaden their knowledge. It is written with a focus on story telling from McKenna’s own life and he provides down-to-earth examples from his everyday life. This makes it less academic to read but still provides a lot of valuable insights.

	'''4. Schmidt, Tobias Sebastian et al (2017): AGILE DEVELOPMENT AND THE CONSTRAINTS OF PHYSICALITY: A NETWORK THEORY-BASED CAUSE-AND EFFECT ANALYSIS. In: Proceedings of the 21st International Conference on Engineering Design (ICED17), Vol. 4: Design Methods and Tools, Vancouver, Canada, 21.-25.08.2017.'''		'''4. Schmidt, Tobias Sebastian et al (2017): AGILE DEVELOPMENT AND THE CONSTRAINTS OF PHYSICALITY: A NETWORK THEORY-BASED CAUSE-AND EFFECT ANALYSIS. In: Proceedings of the 21st International Conference on Engineering Design (ICED17), Vol. 4: Design Methods and Tools, Vancouver, Canada, 21.-25.08.2017.'''

S165111: /* Application */

2021-02-28T17:49:31Z

Application

← Older revision		Revision as of 17:49, 28 February 2021
Line 29:		Line 29:
	With this in mind, the application of Scrum is presented below.		With this in mind, the application of Scrum is presented below.

	== Application ==		== Application and Implementation of Scrum ==
	Scrum is applied as a framework for managing the project life cycle development from idea to finished product. Figure 1 provides an overview of the Scrum Framework consisting of the roles, events and artifacts. Literature on Scrum implementation in software projects incorporates further roles in the framework<ref name="ArtofScrum"> McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA. Retrieved from https://doi-org.proxy.findit.dtu.dk/10.1007/978-1-4842-2277-5 </ref><ref name="SCRUMDeepdive"> Bibik I. (2018) Agile Scrum Deep Dive. In: How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_3</ref>(p.35-55 and p.16-18) than illustrated in Figure 1, though the figure explains how the Scrum Framework can be implemented in any project regardless of type. The figure is based on the Scrum Framework Poster from Home of Scrum<ref name="SCRUM.org"> The Home of Scrum. Retrieved from https://www.scrum.org/resources/what-is-scrum</ref>. Based on this figure, the framework will be described in the following section, focusing on how to implement Scrum.		Scrum is applied as a framework for managing the project life cycle development from idea to finished product. Figure 1 provides an overview of the Scrum Framework consisting of the roles, events and artifacts. Literature on Scrum implementation in software projects incorporates further roles in the framework<ref name="ArtofScrum"> McKenna, Dave (2016): The Art of Scrum. How Scrum Masters Bind Dev Teams and Unleash Agility. Apress, Berkeley, CA. Retrieved from https://doi-org.proxy.findit.dtu.dk/10.1007/978-1-4842-2277-5 </ref><ref name="SCRUMDeepdive"> Bibik I. (2018) Agile Scrum Deep Dive. In: How to Kill the Scrum Monster. Apress, Berkeley, CA. Retrieved from https://doi.org/10.1007/978-1-4842-3691-8_3</ref>(p.35-55 and p.16-18) than illustrated in Figure 1, though the figure explains how the Scrum Framework can be implemented in any project regardless of type. The figure is based on the Scrum Framework Poster from Home of Scrum<ref name="SCRUM.org"> The Home of Scrum. Retrieved from https://www.scrum.org/resources/what-is-scrum</ref>. Based on this figure, the framework will be described in the following section, focusing on how to implement Scrum.

S165111: /* Abstract */

2021-02-28T17:48:16Z

Abstract

← Older revision		Revision as of 17:48, 28 February 2021
Line 7:		Line 7:
	In an ever-changing world that is getting more and more complex, the art of project management is becoming harder to control due to uncertainty and the speed in which requirements and demand change. Standard ways of planning a project, such as the Waterfall model, may not be applicable in some cases. To accommodate this issue, the adaptive project management framework, Scrum, can be used because it embraces agility and fast project deliveries. Scrum relates to the project and development life cycles in the PMI standard. Even though Scrum is applicable for both project, program and portfolio management, this article will focus solely on Scrum as a project management framework and the implementation of Scrum.		In an ever-changing world that is getting more and more complex, the art of project management is becoming harder to control due to uncertainty and the speed in which requirements and demand change. Standard ways of planning a project, such as the Waterfall model, may not be applicable in some cases. To accommodate this issue, the adaptive project management framework, Scrum, can be used because it embraces agility and fast project deliveries. Scrum relates to the project and development life cycles in the PMI standard. Even though Scrum is applicable for both project, program and portfolio management, this article will focus solely on Scrum as a project management framework and the implementation of Scrum.

	The Scrum framework was developed in the early 1990's by Ken Schwaber & Jeff Sutherland and is a framework based on empiricism and lean thinking and has its roots in software development<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref> (p.1). Today, Scrum is one of the most popular ways of becoming agile and is widely used for various projects. Benefits of utilizing the Scrum Framework to structure the development life cycles are continuous improvements, transparency, early adoption, and embracing change, which is a great advantage compared to the classic Waterfall model. The process of Scrum is to first create the product backlog and then define the sprint by creating the sprint backlog and then performing development resulting in an increment. By working incrementally, the team can learn from previous sprints to optimize the next and the product may be ready for release earlier than first anticipated~~<ref name="SCRUM.org"> The Home of Scrum. Retrieved from https://www.scrum.org/resources/what-is-scrum</ref>~~. The Scrum Framework creates value in an adaptive and agile way through the ''Scrum values'', the ''Scrum team'', ''events'' and ''artifacts''. The values focus on Commitment, Focus, Openness, Respect, and Courage. The team consists of the Product Owner (PO), the Scrum master (SM) and, lastly, the self-organizing Development Team (DT). Furthermore, the framework consists of events such as Sprints, Sprint Planning and Sprint Retrospective, and artifacts which are the product backlog, sprint backlog and burndown chart~~<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref>(p.1-12)~~. Scrum has limitations by being non-applicable to 'business-as-usual' projects, constraint of physicality, potential scope creep due to an indefinite end-date etc.		The Scrum framework was developed in the early 1990's by Ken Schwaber & Jeff Sutherland and is a framework based on empiricism and lean thinking and has its roots in software development<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref> (p.1). Today, Scrum is one of the most popular ways of becoming agile and is widely used for various projects. Benefits of utilizing the Scrum Framework to structure the development life cycles are continuous improvements, transparency, early adoption, and embracing change, which is a great advantage compared to the classic Waterfall model. The process of Scrum is to first create the product backlog and then define the sprint by creating the sprint backlog and then performing development resulting in an increment. By working incrementally, the team can learn from previous sprints to optimize the next and the product may be ready for release earlier than first anticipated. The Scrum Framework creates value in an adaptive and agile way through the ''Scrum values'', the ''Scrum team'', ''events'' and ''artifacts''. The values focus on Commitment, Focus, Openness, Respect, and Courage. The team consists of the Product Owner (PO), the Scrum master (SM) and, lastly, the self-organizing Development Team (DT). Furthermore, the framework consists of events such as Sprints, Sprint Planning and Sprint Retrospective, and artifacts which are the product backlog, sprint backlog and burndown chart. Scrum has limitations by being non-applicable to 'business-as-usual' projects, constraint of physicality, potential scope creep due to an indefinite end-date etc.

	== Why use Scrum? ==		== Why use Scrum? ==

S165111: /* Why use Scrum? */

2021-02-28T17:47:18Z

Why use Scrum?

← Older revision		Revision as of 17:47, 28 February 2021
Line 13:		Line 13:
	''Adaptive life cycles are agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.''		''Adaptive life cycles are agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.''
	''Adaptive life cycles are also referred to as agile or change-driven life cycle'' (The PMI standard, p19)		''Adaptive life cycles are also referred to as agile or change-driven life cycle'' (The PMI standard, p19)
	Agility and Scrum are strong drivers for simplicity in a complex environment especially within the project management knowledge areas; project integration management, scope management, schedule management and risk management<ref name="HBTS"></ref>(p.23-25) to name a few. For scope and schedule management, Scrum is a strong framework because it is possible to adapt to unforeseen changes as the business environment evolves due to the iterative nature of the framework. For risk management, Scrum is usable based on, again, the iterative nature but also continuous contact to project stakeholders<ref name="HBTS"></ref>(Appendix X3). This, together with other knowledge areas, all adds up to a strong framework for excellent integration management throughout the project life cycle.		Agility and Scrum are strong drivers for simplicity in a complex environment especially within the project management knowledge areas; project integration management, scope management, schedule management and risk management<ref name="HBTS"></ref>(p.23-25) to name a few. For scope and schedule management, Scrum is a strong framework because it is possible to adapt to unforeseen changes as the business environment evolves due to the iterative nature of the framework. For risk management, Scrum is usable based on, again, the iterative nature but also continuous contact to project stakeholders<ref name="HBTS"></ref>(Appendix X3). This, together with other knowledge areas, all adds up to a strong framework for excellent integration management throughout the project life cycle. By structuring the development life cycles according to the Scrum Framework, benefits such as continuous improvements, transparency, early adoption, and embracing change are met.

	Scrum theory<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref>(p.3) explains how the agile framework from the 1990's is based on empiricism, which means that knowledge comes with experience and decision making should be based on what is observable and lean thinking which seeks to eliminate waste and focus on what is value-adding. The empirical pillars of Scrum are transparency, inspection and adaptation<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref>(p.3). Scrum improves predictability and the act of controlling risk, which is driven by transparency in the project management process. Having high transparency also implies a need for inspection to ensure progress and identify problems during the process. The inspection process is handled during the Scrum events. Lastly, having inspections without adaptation and learning is pointless which is why the Scrum team must work empirically. Scrum is highly relevant in today's vibrating business environment because it creates a framework able to handle unpredictability and complexity in a project and makes teams able to create higher value more frequently, ultimatly resulting in higher customer satisfaction<ref name="SCRUM.org"> The Home of Scrum. Retrieved from https://www.scrum.org/resources/what-is-scrum</ref>.		Scrum theory<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref>(p.3) explains how the agile framework from the 1990's is based on empiricism, which means that knowledge comes with experience and decision making should be based on what is observable and lean thinking which seeks to eliminate waste and focus on what is value-adding. The empirical pillars of Scrum are transparency, inspection and adaptation<ref name="Scrumguide"> Sutherland Ph.D, Jeff; Schwaber, Ken(2020): The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. Retrieved from https://www.scrumguides.org/</ref>(p.3). Scrum improves predictability and the act of controlling risk, which is driven by transparency in the project management process. Having high transparency also implies a need for inspection to ensure progress and identify problems during the process. The inspection process is handled during the Scrum events. Lastly, having inspections without adaptation and learning is pointless which is why the Scrum team must work empirically. Scrum is highly relevant in today's vibrating business environment because it creates a framework able to handle unpredictability and complexity in a project and makes teams able to create higher value more frequently, ultimatly resulting in higher customer satisfaction<ref name="SCRUM.org"> The Home of Scrum. Retrieved from https://www.scrum.org/resources/what-is-scrum</ref>.