The Scrum framework - Revision history

S200165: /* Limitations of Scrum */

2021-02-28T22:29:07Z

Limitations of Scrum

← Older revision		Revision as of 22:29, 28 February 2021
Line 118:		Line 118:
	Team members have to be cooperative, self organising and willing to follow the Scrum framework. Getting into this framework and starting to use it can take time, as it is important to implement it in its entirety to get the full benefits (''Page 13'') <ref name="Guide"/>. There are frequent meetings so the team members have to be willing to engage in. A problem could arise when a team member decides to quit during the project as each member of the team has their specific role and is very valuable. Another issue can be to manage the budget as you are working with a flexible scope. However the customers have a fixed budget and time frame. Another disadvantage identified being the visibility of the project progress <ref name="Miller"> Miller, G. J. (2013). Agile problems, challenges, & failures. Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA. Newtown Square, PA: Project Management Institute.,</ref> this can be more clear where deterministic project management approaches are used with detailed plans using e.g. [[Gantt]] charts and work schedules.		Team members have to be cooperative, self organising and willing to follow the Scrum framework. Getting into this framework and starting to use it can take time, as it is important to implement it in its entirety to get the full benefits (''Page 13'') <ref name="Guide"/>. There are frequent meetings so the team members have to be willing to engage in. A problem could arise when a team member decides to quit during the project as each member of the team has their specific role and is very valuable. Another issue can be to manage the budget as you are working with a flexible scope. However the customers have a fixed budget and time frame. Another disadvantage identified being the visibility of the project progress <ref name="Miller"> Miller, G. J. (2013). Agile problems, challenges, & failures. Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA. Newtown Square, PA: Project Management Institute.,</ref> this can be more clear where deterministic project management approaches are used with detailed plans using e.g. [[Gantt]] charts and work schedules.

	PMI members were concerned when they downloaded the new edition of the PMBOK guide, as they noticed that at the same time they received a copy of the Agile Practice Guide[https://www.pmi.org/pmbok-guide-standards/practice-guides/agile]. Some asking if now everything should turn Agile<ref name="Fewell"/>. However it needs to be acknowledged that you shouldn't make all projects agile, you need to evaluate what approach fits best. In cases where you are working with a predictable environment, where you know how the timeline will evolve then Agile Project Management methodologies like Scrum aren't the way to go. ~~Some even going so far as stating~~ that for construction ~~work Scrum isn't ideal~~. However at the same time others ~~claiming~~ that it could be used for construction<ref name="Straçusser"> Straçusser, G. (2015). ''Agile project management concepts applied to construction and other non-IT fields.'' Paper presented at PMI® Global Congress 2015—North America, Orlando, FL. Newtown Square, PA: Project Management Institute.</ref>. So it can only be emphasised once more that each case has to be evaluated and from that the best approach defined.		PMI members were concerned when they downloaded the new edition of the PMBOK guide, as they noticed that at the same time they received a copy of the Agile Practice Guide[https://www.pmi.org/pmbok-guide-standards/practice-guides/agile]. Some asking if now everything should turn Agile<ref name="Fewell"/>. However it needs to be acknowledged that you shouldn't make all projects agile, you need to evaluate what approach fits best. In cases where you are working with a predictable environment, where you know how the timeline will evolve then Agile Project Management methodologies like Scrum aren't the way to go. When trying to identify some type of projects that are not effectively managed with Agile Project Management methodologies some have pointed out construction projects. The reason for that being that in construction changes are expensive and construction projects tend to be sequential. However at the same time others claim that it could be used for construction when applied correctly<ref name="Straçusser"> Straçusser, G. (2015). ''Agile project management concepts applied to construction and other non-IT fields.'' Paper presented at PMI® Global Congress 2015—North America, Orlando, FL. Newtown Square, PA: Project Management Institute.</ref>. So it can only be emphasised once more that each case has to be evaluated and from that the best approach defined.

	== Annotated bibliography ==		== Annotated bibliography ==

S200165: /* Big idea */

2021-02-28T21:07:14Z

Big idea

← Older revision		Revision as of 21:07, 28 February 2021
Line 19:		Line 19:
	*'''Working software''' over comprehensive documentation		*'''Working software''' over comprehensive documentation
	*'''Customer collaboration''' over contract negotiation		*'''Customer collaboration''' over contract negotiation
	*'''Responding to change''' over following a plan "<ref name=''Manifesto1''>, Agilemanifesto.org (2001) ''Principles behind the Agile Manifesto''~~, (Accessed on 12th of February),~~ </ref>.		*'''Responding to change''' over following a plan "<ref name=''Manifesto1''>, Agilemanifesto.org (2001) ''Principles behind the Agile Manifesto''. https://Agilemanifesto.Org/. https://agilemanifesto.org/principles.html </ref>.

	However it was in the early 90s when members of the ''Agile Alliance'' Ken Schwaber & Jeff Sutherland started developing the Scrum framework (''Page 1'')<ref name="Scrum.org">, Scrum.org (2021) ''About Scrum.org'', (Accessed on 15th of February), </ref>, with the first publication 1990 in the book ''Wicked Problems, Righteous Solutions'' (''Page 526'')<ref name="Kousholt"> Kousholt, B. (2012). '' Project Management; Theory and practice'' (2nd ed.). Nyt Teknisk Forlag.</ref>. In addition to the values from the Agile Manifesto Scrum also highlights the following values: ''Commitment'', ''Focus'', ''Openness'', ''Respect'' and ''Courage'' (''Page 4'')<ref name="Guide"/>. Since 2001 [[Agile Project Management]] has grown in popularity and in 2009 more organisation were using Agile than Waterfall processes. From those Agile processes the majority was using the Scrum framework or 84%. In 2009 Ken Schwaber created an organisation Scrum.org [www.scrum.org], reaching a broader audience and providing access to materials and courses. There you can access the ''Scrum Guide'' that Ken Schwaber and Jeff Sutherland published in 2010, which gives great overview of the Scrum framework and its application <ref name="Scrum.org"/>. As previously mentioned this popularity is also reflected in the [[Project Management Body of Knowledge \| PMI standards]]		However it was in the early 90s when members of the ''Agile Alliance'' Ken Schwaber & Jeff Sutherland started developing the Scrum framework (''Page 1'')<ref name="Scrum.org">, Scrum.org (2021) ''About Scrum.org'', (Accessed on 15th of February), </ref>, with the first publication 1990 in the book ''Wicked Problems, Righteous Solutions'' (''Page 526'')<ref name="Kousholt"> Kousholt, B. (2012). '' Project Management; Theory and practice'' (2nd ed.). Nyt Teknisk Forlag.</ref>. In addition to the values from the Agile Manifesto Scrum also highlights the following values: ''Commitment'', ''Focus'', ''Openness'', ''Respect'' and ''Courage'' (''Page 4'')<ref name="Guide"/>. Since 2001 [[Agile Project Management]] has grown in popularity and in 2009 more organisation were using Agile than Waterfall processes. From those Agile processes the majority was using the Scrum framework or 84%. In 2009 Ken Schwaber created an organisation Scrum.org [www.scrum.org], reaching a broader audience and providing access to materials and courses. There you can access the ''Scrum Guide'' that Ken Schwaber and Jeff Sutherland published in 2010, which gives great overview of the Scrum framework and its application <ref name="Scrum.org"/>. As previously mentioned this popularity is also reflected in the [[Project Management Body of Knowledge \| PMI standards]]

S200165: /* Big idea */

2021-02-28T21:05:42Z

Big idea

← Older revision		Revision as of 21:05, 28 February 2021
Line 14:		Line 14:

	== Big idea ==		== Big idea ==
	In 2001 a group called the ''The Agile Alliance'' published the ''Manifesto for Agile Software Development''[https://agilemanifesto.org/] "<ref name=''Manifesto''>, ~~''Agilemanifesto.org ''~~Highsmith, J. (2001) ''History: The Agile Manifesto''~~, (Accessed on 12th of February),~~ </ref>. It can be said that this group started an Agile movement. Even though it started as a movement to help software development Agile Project Management is now being used in many other industries and projects. The following bullets are taken from the Agile Manifesto and highlight that people practicing Agile methods value:		In 2001 a group called the ''The Agile Alliance'' published the ''Manifesto for Agile Software Development''[https://agilemanifesto.org/] "<ref name=''Manifesto''>, Highsmith, J. (2001). ''History: The Agile Manifesto''. https://Agilemanifesto.Org/. https://agilemanifesto.org/history.html </ref>. It can be said that this group started an Agile movement. Even though it started as a movement to help software development Agile Project Management is now being used in many other industries and projects. The following bullets are taken from the Agile Manifesto and highlight that people practicing Agile methods value:

	*'''Individuals and interactions''' over processes and tools		*'''Individuals and interactions''' over processes and tools

S200165 at 21:01, 28 February 2021

2021-02-28T21:01:46Z

← Older revision		Revision as of 21:01, 28 February 2021
Line 4:		Line 4:
	This article will focus on the Scrum framework from a project management perspective, even though the topic is also relevant for program and portfolio management. This article aims to describe the Scrum framework and its application in a simple way, where figures are used to support the understanding. It is aimed at readers interested in knowing the basics of the Scrum framework as well as beginners using Scrum. The annotated bibliography gives some good example for further knowledge as for example Ken Schwaber's book ''Agile Project Management with Scrum''[https://www.amazon.com/Agile-Project-Management-Developer-Practices/dp/073561993X]. Furthermore it is highly recommended to take a look at scrum.org[http://www.scrum.org] where a lot of material and videos on the topic have been gathered.		This article will focus on the Scrum framework from a project management perspective, even though the topic is also relevant for program and portfolio management. This article aims to describe the Scrum framework and its application in a simple way, where figures are used to support the understanding. It is aimed at readers interested in knowing the basics of the Scrum framework as well as beginners using Scrum. The annotated bibliography gives some good example for further knowledge as for example Ken Schwaber's book ''Agile Project Management with Scrum''[https://www.amazon.com/Agile-Project-Management-Developer-Practices/dp/073561993X]. Furthermore it is highly recommended to take a look at scrum.org[http://www.scrum.org] where a lot of material and videos on the topic have been gathered.

	The article will zoom in on how the Scrum framework relates to the project and development life cycles presented in the [[Project Management Body of Knowledge \| PMI standards]]<ref name="PMBOK"> Project Management Institute, Inc.. (2017). ''A Guide to the Project Management Body of Knowledge (PMBOK Guide)''(6th ed.). Project Management Institute, Inc (PMI).</ref>. Where it will be compared to the Waterfall model, as that model can be considered the most traditional project management model <ref name="WaterfallProj"> What ~~is waterfall project management~~'' ~~Accessible: ref~~ https://www.wrike.com/project-management-guide/faq/what-is-waterfall-project-management/.</ref>. Furthermore benefits and limitations of the Scrum framework will be addressed from for example a risk management and customer involvement perspective.		The article will zoom in on how the Scrum framework relates to the project and development life cycles presented in the [[Project Management Body of Knowledge \| PMI standards]]<ref name="PMBOK"> Project Management Institute, Inc.. (2017). ''A Guide to the Project Management Body of Knowledge (PMBOK Guide)''(6th ed.). Project Management Institute, Inc (PMI).</ref>. Where it will be compared to the Waterfall model[https://www.wrike.com/project-management-guide/faq/what-is-waterfall-project-management/], as that model can be considered the most traditional project management model <ref name="WaterfallProj"> ''What Is Waterfall in Project Management?''- Wrike. (2021). Wrike.Com. https://www.wrike.com/project-management-guide/faq/what-is-waterfall-project-management/</ref>. Furthermore benefits and limitations of the Scrum framework will be addressed from for example a risk management and customer involvement perspective.


	== Abstract ==		== Abstract ==

S200165: /* Scrum vs Traditional Project Management (Waterfall) */

2021-02-28T20:51:30Z

Scrum vs Traditional Project Management (Waterfall)

← Older revision		Revision as of 20:51, 28 February 2021
Line 77:		Line 77:
	Scrum has an adaptive life cycle that is agile, where a scope is defined and approved before the start of each sprint. Adaptive life cycles are also often called change-driven life cycles (''Pages 18-19'')<ref name="PMBOK"/>. The latter emphasises that Agile methodologies like the Scrum framework welcomes changes. As an iterative model Scrum starts small and then adds on throughout the project. Figure 5. gives an overview of the difference between the project life cycle for Scrum and Waterfall projects.		Scrum has an adaptive life cycle that is agile, where a scope is defined and approved before the start of each sprint. Adaptive life cycles are also often called change-driven life cycles (''Pages 18-19'')<ref name="PMBOK"/>. The latter emphasises that Agile methodologies like the Scrum framework welcomes changes. As an iterative model Scrum starts small and then adds on throughout the project. Figure 5. gives an overview of the difference between the project life cycle for Scrum and Waterfall projects.

	[[File:WaterVsScrum.jpg\|frame\|center\|Figure 5: Project life cycle: ~~Water~~ vs Scrum Adapted from the article''Scrum vs Waterfall vs Agile vs Lean vs Kanban'' bu Visual Paradigm accessible at:https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-]]		[[File:WaterVsScrum.jpg\|frame\|center\|Figure 5: Project life cycle: Waterfall vs Scrum Adapted from the article''Scrum vs Waterfall vs Agile vs Lean vs Kanban'' bu Visual Paradigm accessible at:https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-]]

	For each project the project management needs to consider what approach fits best<ref name="PMBOK"/>. For that purpose the following table will give a short overview of the differences between the Scrum framework and the Waterfall model.		For each project the project management needs to consider what approach fits best<ref name="PMBOK"/>. For that purpose the following table will give a short overview of the differences between the Scrum framework and the Waterfall model.

S200165: /* Annotated bibliography */

2021-02-28T20:49:54Z

Annotated bibliography

← Older revision		Revision as of 20:49, 28 February 2021
Line 125:		Line 125:
	*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This guide is written by the founders of the Scrum framework. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors emphasise that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.		*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This guide is written by the founders of the Scrum framework. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors emphasise that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.

	*Project Management Institute, Inc. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum ~~Framework~~, an adaptive, Agile Project Management Framework.		*Project Management Institute, Inc. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum framework, an adaptive, Agile Project Management Framework.

	*Sliger, M. (2011). ''Agile project management with Scrum''. Paper presented at PMI® Global Congress 2011—North America, Dallas, TX. Newtown Square, PA: Project Management Institute: This is a short article that gives good overview of the Scrum ~~Framework~~, in particular the application. The article uses relevant figures to support the text. It introduces the relevant tools for Scrum like for example the Scrum Board and Burndown charts. Furthermore it brings up good questions, provides good examples as well as comparison between the Scrum ~~Framework~~ and more traditional approaches.		*Sliger, M. (2011). ''Agile project management with Scrum''. Paper presented at PMI® Global Congress 2011—North America, Dallas, TX. Newtown Square, PA: Project Management Institute: This is a short article that gives good overview of the Scrum framework, in particular the application. The article uses relevant figures to support the text. It introduces the relevant tools for Scrum like for example the Scrum Board and Burndown charts. Furthermore it brings up good questions, provides good examples as well as comparison between the Scrum framework and more traditional approaches.

	== References ==		== References ==
	<references />		<references />

S200165: /* Annotated bibliography */

2021-02-28T20:49:22Z

Annotated bibliography

← Older revision		Revision as of 20:49, 28 February 2021
Line 121:		Line 121:
	== Annotated bibliography ==		== Annotated bibliography ==

	*Schwaber, K. (2004). ''Agile Project Management with Scrum (Developer Best Practices)'' (1st ed.). Microsoft Press: This book is written by one of the founders of the Scrum ~~Framework~~ Ken Schwaber. It provides you with a good overview of the Scrum framework, roles, artifacts and events. Ken also introduces good cases that have both been successful and failed, furthermore he provides good recommendations. This book is well structured, easy to read and the appendixes are very helpful, like for example the Definition table which lists key words used in the Scrum Framework. This book would be suitable for beginners as well as experts. However it can be recommended for beginners to start by reading the Scrum Guide, which is listed here below.		*Schwaber, K. (2004). ''Agile Project Management with Scrum (Developer Best Practices)'' (1st ed.). Microsoft Press: This book is written by one of the founders of the Scrum framework Ken Schwaber. It provides you with a good overview of the Scrum framework, roles, artifacts and events. Ken also introduces good cases that have both been successful and failed, furthermore he provides good recommendations. This book is well structured, easy to read and the appendixes are very helpful, like for example the Definition table which lists key words used in the Scrum Framework. This book would be suitable for beginners as well as experts. However it can be recommended for beginners to start by reading the Scrum Guide, which is listed here below.

	*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This guide is written by the founders of the Scrum ~~Framework~~. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors emphasise that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.		*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This guide is written by the founders of the Scrum framework. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors emphasise that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.

	*Project Management Institute, Inc. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum Framework, an adaptive, Agile Project Management Framework.		*Project Management Institute, Inc. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum Framework, an adaptive, Agile Project Management Framework.

S200165: /* Scrum vs Traditional Project Management (Waterfall) */

2021-02-28T20:48:45Z

Scrum vs Traditional Project Management (Waterfall)

← Older revision		Revision as of 20:48, 28 February 2021
Line 75:		Line 75:
	The Waterfall Model has a predictive life cycle, where time, cost and the project scope are well defined early on in the life cycle. Where changes have to be managed well (''Pages 18-19'')<ref name="PMBOK"/> and can be costly. The Waterfall projects begin at one place and then similar to a waterfall cascade down to the end of the project in a forward direction.		The Waterfall Model has a predictive life cycle, where time, cost and the project scope are well defined early on in the life cycle. Where changes have to be managed well (''Pages 18-19'')<ref name="PMBOK"/> and can be costly. The Waterfall projects begin at one place and then similar to a waterfall cascade down to the end of the project in a forward direction.

	Scrum has an adaptive life cycle that is agile, where a scope is defined and approved before the start of each sprint. Adaptive life cycles are also often called change-driven life cycles (''Pages 18-19'')<ref name="PMBOK"/>. The latter emphasises that Agile methodologies like the Scrum ~~Framework~~ welcomes changes. As an iterative model Scrum starts small and then adds on throughout the project. Figure 5. gives an overview of the difference between the project life cycle for Scrum and Waterfall projects.		Scrum has an adaptive life cycle that is agile, where a scope is defined and approved before the start of each sprint. Adaptive life cycles are also often called change-driven life cycles (''Pages 18-19'')<ref name="PMBOK"/>. The latter emphasises that Agile methodologies like the Scrum framework welcomes changes. As an iterative model Scrum starts small and then adds on throughout the project. Figure 5. gives an overview of the difference between the project life cycle for Scrum and Waterfall projects.

	[[File:WaterVsScrum.jpg\|frame\|center\|Figure 5: Project life cycle: Water vs Scrum Adapted from the article''Scrum vs Waterfall vs Agile vs Lean vs Kanban'' bu Visual Paradigm accessible at:https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-]]		[[File:WaterVsScrum.jpg\|frame\|center\|Figure 5: Project life cycle: Water vs Scrum Adapted from the article''Scrum vs Waterfall vs Agile vs Lean vs Kanban'' bu Visual Paradigm accessible at:https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-]]

S200165 at 20:48, 28 February 2021

2021-02-28T20:48:13Z

Show changes

S200165: /* Annotated bibliography */

2021-02-28T20:32:51Z

Annotated bibliography

← Older revision		Revision as of 20:32, 28 February 2021
Line 123:		Line 123:
	*Schwaber, K. (2004). ''Agile Project Management with Scrum (Developer Best Practices)'' (1st ed.). Microsoft Press: This book is written by one of the founders of the Scrum Framework Ken Schwaber. It provides you with a good overview of the Scrum framework, roles, artifacts and events. Ken also introduces good cases that have both been successful and failed, furthermore he provides good recommendations. This book is well structured, easy to read and the appendixes are very helpful, like for example the Definition table which lists key words used in the Scrum Framework. This book would be suitable for beginners as well as experts. However it can be recommended for beginners to start by reading the Scrum Guide, which is listed here below.		*Schwaber, K. (2004). ''Agile Project Management with Scrum (Developer Best Practices)'' (1st ed.). Microsoft Press: This book is written by one of the founders of the Scrum Framework Ken Schwaber. It provides you with a good overview of the Scrum framework, roles, artifacts and events. Ken also introduces good cases that have both been successful and failed, furthermore he provides good recommendations. This book is well structured, easy to read and the appendixes are very helpful, like for example the Definition table which lists key words used in the Scrum Framework. This book would be suitable for beginners as well as experts. However it can be recommended for beginners to start by reading the Scrum Guide, which is listed here below.

	*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This ~~book or~~ guide is written by the founders of the Scrum Framework. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors ~~emphasis~~ that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.		*Schwaber, K & Sutherland, J (November 2020) ''The Scrum Guide; The Definitive Guide to Scrum: The Rules of the Game'': This guide is written by the founders of the Scrum Framework. The guide is short (13 pages), on point and can be considered a quick read. It can be said that this book describes Scrum in simple words. When you have finished reading it you should have a good understanding of the definition of Scrum. In the guide the authors emphasise that the Scrum Framework is free and all you need to know is provided in this guide. However it must be said that this guide gives quite high-level overview of the Scrum Framework. Therefore it would be recommended to read books that are more specific about the topic, like the previously mentioned book by Ken Schwaber to gain deeper understanding.

	*Project Management Institute, Inc.. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum Framework, an adaptive, Agile Project Management Framework.		*Project Management Institute, Inc. (2017). ''A Guide to the Project Management Body of Knowledge'' (PMBOK Guide)(6th ed.). Project Management Institute, Inc (PMI): This book provides a set of standard terminology and guidelines for project management. So everything you need to now in regards to project management and topics relevant to that. This book is reviewed frequently so it is kept up to date. What is great about this newest edition from 2017 is that there is additional input on adaptive project management methodologies. Where they have taken into consideration adaptive environment which is highly relevant to individuals wanting to inform themselves about the Scrum Framework, an adaptive, Agile Project Management Framework.

	*Sliger, M. (2011). ''Agile project management with Scrum''. Paper presented at PMI® Global Congress 2011—North America, Dallas, TX. Newtown Square, PA: Project Management Institute: This is a short article that gives good overview of the Scrum Framework, in particular the application. The article uses relevant figures to support the text. It introduces the relevant tools for Scrum like ~~e.g.~~ Scrum Board and Burndown charts. Furthermore it brings up good questions, provides good examples as well as comparison between the Scrum Framework and more traditional approaches.		*Sliger, M. (2011). ''Agile project management with Scrum''. Paper presented at PMI® Global Congress 2011—North America, Dallas, TX. Newtown Square, PA: Project Management Institute: This is a short article that gives good overview of the Scrum Framework, in particular the application. The article uses relevant figures to support the text. It introduces the relevant tools for Scrum like for example the Scrum Board and Burndown charts. Furthermore it brings up good questions, provides good examples as well as comparison between the Scrum Framework and more traditional approaches.

	== References ==		== References ==
	<references />		<references />