SCRUM framework - Revision history

SanaIlyas: /* Limitations and challenges */

2021-02-28T09:16:27Z

Limitations and challenges

← Older revision		Revision as of 09:16, 28 February 2021
Line 148:		Line 148:

	Agile practices is becoming more and more popular and it is expected to grow in the future <ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>.		Agile practices is becoming more and more popular and it is expected to grow in the future <ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>.
	The reasons for adopting Agile were investigated in a survey conducted by Viosion One in 2020<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>. Here, the top ~~resaons~~ were: "Accelerate Software Delivery" (71%), "Enhance ability to manage changing priorities" (63%), "Increase productivity" (51%), and "Improve business/IT alignment" (47%). Likewise, the benefits of adopting agile were investigated among the respondants, giving the top benefits: "Ability to manage changing priorities" (70%), "Project visibility" (65%), "Business/IT alignment" (65%) and "Delivery speed/Time to market" (60%).		The reasons for adopting Agile were investigated in a survey conducted by Viosion One in 2020<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>. Here, the top reasons were: "Accelerate Software Delivery" (71%), "Enhance ability to manage changing priorities" (63%), "Increase productivity" (51%), and "Improve business/IT alignment" (47%). Likewise, the benefits of adopting agile were investigated among the respondants, giving the top benefits: "Ability to manage changing priorities" (70%), "Project visibility" (65%), "Business/IT alignment" (65%) and "Delivery speed/Time to market" (60%).

	However, here are some limitations and challenges related to the framework:		However, here are some limitations and challenges related to the framework:

SanaIlyas: /* References */

2021-02-28T09:15:06Z

References

← Older revision		Revision as of 09:15, 28 February 2021
Line 191:		Line 191:

	<ref name=Bianco> Bianco C, ''"Agile and SPICE Capability Levels".'' Communications in Computer and Information Science, Springer, vol 155 (2011) </ref>Bianco C. (2011) Agile and SPICE Capability Levels. In: O’Connor R.V., Rout T., McCaffery F., Dorling A. (eds) Software Process Improvement and Capability Determination. SPICE 2011. Communications in Computer and Information Science, vol 155. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21233-8_16		<ref name=Bianco> Bianco C, ''"Agile and SPICE Capability Levels".'' Communications in Computer and Information Science, Springer, vol 155 (2011) </ref>Bianco C. (2011) Agile and SPICE Capability Levels. In: O’Connor R.V., Rout T., McCaffery F., Dorling A. (eds) Software Process Improvement and Capability Determination. SPICE 2011. Communications in Computer and Information Science, vol 155. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21233-8_16

			<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref> Vision One,''"14th annual State of Agile Report"'', https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494 (2020)

	<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10		<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10

	<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref> Vision One,''"14th annual State of Agile Report"'', https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494 (2020)

SanaIlyas at 09:14, 28 February 2021

2021-02-28T09:14:05Z

← Older revision		Revision as of 09:14, 28 February 2021
Line 147:		Line 147:
	==Limitations and challenges==		==Limitations and challenges==

	~~Scrum has proven~~ to ~~be efficient~~ in ~~many ways~~		Agile practices is becoming more and more popular and it is expected to grow in the future <ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>.
			The reasons for adopting Agile were investigated in a survey conducted by Viosion One in 2020<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref>. Here, the top resaons were: "Accelerate Software Delivery" (71%), "Enhance ability to manage changing priorities" (63%), "Increase productivity" (51%), and "Improve business/IT alignment" (47%). Likewise, the benefits of adopting agile were investigated among the respondants, giving the top benefits: "Ability to manage changing priorities" (70%), "Project visibility" (65%), "Business/IT alignment" (65%) and "Delivery speed/Time to market" (60%).

	However, here are some limitations and challenges related to the framework:		However, here are some limitations and challenges related to the framework:
Line 192:		Line 193:

	<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10		<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10

			<ref name=AgileReport> Vision One, ''"14th annual State of Agile Report".'' https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494, (2020) </ref> Vision One,''"14th annual State of Agile Report"'', https://stateofagile.com/?_ga=2.1847793.1975269652.1614501418-1195485270.1614501418#ufh-i-615706098-14th-annual-state-of-agile-report/7027494 (2020)

SanaIlyas: /* Scrum Team and roles */

2021-02-27T13:36:17Z

Scrum Team and roles

← Older revision		Revision as of 13:36, 27 February 2021
Line 62:		Line 62:
	The development team responsibilities can be summarized as follows:		The development team responsibilities can be summarized as follows:
	*Owns the Sprint Backlog: The development team is self-organized and accountable for creating an execution plan for user stories in the Sprint backlog and adapting their plan if necessary in order to reach Sprint goal while bringing value and quality in their tasks<ref name=Guide>Ken Schwaber & Jeff Sutherland, ''"The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game - 2020 edition".'' (2020) </ref>.		*Owns the Sprint Backlog: The development team is self-organized and accountable for creating an execution plan for user stories in the Sprint backlog and adapting their plan if necessary in order to reach Sprint goal while bringing value and quality in their tasks<ref name=Guide>Ken Schwaber & Jeff Sutherland, ''"The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game - 2020 edition".'' (2020) </ref>.
	*Defining the "Definition of done" (DoD): The Definition of Done can be viewed as a formal agreement between the developers and PO that states ''"what requirements, in addition to the user story's acceptance criteria, you need to fulfill to be done with the story"''<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref>. In other words, it describes the requirements for when an user story in the backlog is completed and ready to be delivered to the customer <ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref>		*Defining the "Definition of done" (DoD): The Definition of Done can be viewed as a formal agreement between the developers and PO that states ''"what requirements, in addition to the user story's acceptance criteria, you need to fulfill to be done with the story"''<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref>. In other words, it describes the requirements for when an user story in the backlog is completed and ready to be delivered to the customer <ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref>
	* Work cross-functional: It is encouraged that developers do not claim an area of expertise and stick to that. Ideally, every developer should be able to perform different tasks thus being involved in every aspect of the development process. This will prevent bottlenecks and hierachies in the team<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref>		* Work cross-functional: It is encouraged that developers do not claim an area of expertise and stick to that. Ideally, every developer should be able to perform different tasks thus being involved in every aspect of the development process. This will prevent bottlenecks and hierachies in the team<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref>

SanaIlyas: /* Scrum Team and roles */

2021-02-27T13:33:56Z

Scrum Team and roles

← Older revision		Revision as of 13:33, 27 February 2021
Line 62:		Line 62:
	The development team responsibilities can be summarized as follows:		The development team responsibilities can be summarized as follows:
	*Owns the Sprint Backlog: The development team is self-organized and accountable for creating an execution plan for user stories in the Sprint backlog and adapting their plan if necessary in order to reach Sprint goal while bringing value and quality in their tasks<ref name=Guide>Ken Schwaber & Jeff Sutherland, ''"The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game - 2020 edition".'' (2020) </ref>.		*Owns the Sprint Backlog: The development team is self-organized and accountable for creating an execution plan for user stories in the Sprint backlog and adapting their plan if necessary in order to reach Sprint goal while bringing value and quality in their tasks<ref name=Guide>Ken Schwaber & Jeff Sutherland, ''"The Scrum Guide - The Definitive Guide to Scrum: The Rules of the Game - 2020 edition".'' (2020) </ref>.
	*Defining the "Definition of done" (DoD): The Definition of Done can be viewed as a formal agreement between the developers and PO that states ''"what requirements, in addition to the user story's acceptance criteria, you need to fulfill to be done with the story"''<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref>. In other words, it describes the requirements for when an user story in the backlog is completed and ready to be delivered to the customer <ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref>		*Defining the "Definition of done" (DoD): The Definition of Done can be viewed as a formal agreement between the developers and PO that states ''"what requirements, in addition to the user story's acceptance criteria, you need to fulfill to be done with the story"''<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref>. In other words, it describes the requirements for when an user story in the backlog is completed and ready to be delivered to the customer <ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref>
	* Work cross-functional: It is encouraged that developers do not claim an area of expertise and stick to that. Ideally, every developer should be able to perform different tasks thus being involved in every aspect of the development process. This will prevent bottlenecks and hierachies in the team<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref>		* Work cross-functional: It is encouraged that developers do not claim an area of expertise and stick to that. Ideally, every developer should be able to perform different tasks thus being involved in every aspect of the development process. This will prevent bottlenecks and hierachies in the team<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref>

SanaIlyas: /* References */

2021-02-27T13:29:43Z

References

← Older revision		Revision as of 13:29, 27 February 2021
Line 191:		Line 191:
	<ref name=Bianco> Bianco C, ''"Agile and SPICE Capability Levels".'' Communications in Computer and Information Science, Springer, vol 155 (2011) </ref>Bianco C. (2011) Agile and SPICE Capability Levels. In: O’Connor R.V., Rout T., McCaffery F., Dorling A. (eds) Software Process Improvement and Capability Determination. SPICE 2011. Communications in Computer and Information Science, vol 155. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21233-8_16		<ref name=Bianco> Bianco C, ''"Agile and SPICE Capability Levels".'' Communications in Computer and Information Science, Springer, vol 155 (2011) </ref>Bianco C. (2011) Agile and SPICE Capability Levels. In: O’Connor R.V., Rout T., McCaffery F., Dorling A. (eds) Software Process Improvement and Capability Determination. SPICE 2011. Communications in Computer and Information Science, vol 155. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-21233-8_16

	<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10		<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016)</ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10

SanaIlyas: /* References */

2021-02-27T13:29:02Z

References

← Older revision		Revision as of 13:29, 27 February 2021
Line 182:		Line 182:

	<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref> Troels Jakobsen, ''"Scrum Done Right - Learn Agile Software Development".'' Lean Agile Ltd, 1st edition (2019)		<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref> Troels Jakobsen, ''"Scrum Done Right - Learn Agile Software Development".'' Lean Agile Ltd, 1st edition (2019)


	<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref> Rossberg J. (2019) Introduction to Scrum and Agile Concepts. In: Agile Project Management with Azure DevOps. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4483-8_3		<ref name=Rossberg> Rossberg J., ''"Introduction to Scrum and Agile Concepts".'' Agile Project Management with Azure DevOps, Berkeley (2019) </ref> Rossberg J. (2019) Introduction to Scrum and Agile Concepts. In: Agile Project Management with Azure DevOps. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4483-8_3

SanaIlyas: /* References */

2021-02-27T13:28:47Z

References

← Older revision		Revision as of 13:28, 27 February 2021
Line 193:		Line 193:

	<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10		<ref name=Lárusdóttir> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J, ''"Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?".'' Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer,(2016) </ref> Lárusdóttir M., Cajander Å., Erlingsdottir G., Lind T., Gulliksen J. (2016) Challenges from Integrating Usability Activities in Scrum: Why Is Scrum so Fashionable?. In: Cockton G., Lárusdóttir M., Gregory P., Cajander Å. (eds) Integrating User-Centred Design in Agile Development. Human–Computer Interaction Series. Springer, Cham. https://doi.org/10.1007/978-3-319-32165-3_10

	<ref name=PMBOK> Project Management Institute, Inc., ''"Guide to the Project Management Body of Knowledge".'' Project Management Institute, Inc (PMI), 6. edition (2017) </ref> Project Management Institute, Inc., ''"Guide to the Project Management Body of Knowledge".'' Project Management Institute, Inc (PMI), 6. edition (2017)

SanaIlyas: /* References */

2021-02-27T13:28:02Z

References

← Older revision		Revision as of 13:28, 27 February 2021
Line 178:		Line 178:

	<ref name=Castillo> F. Castillo, ''"Agile-Scrum Project Management".'' Managing Information Technology, Springer (2016) </ref>Castillo F. (2016) Agile-Scrum Project Management. In: Managing Information Technology. Springer, Cham. https://doi.org/10.1007/978-3-319-38891-5_8		<ref name=Castillo> F. Castillo, ''"Agile-Scrum Project Management".'' Managing Information Technology, Springer (2016) </ref>Castillo F. (2016) Agile-Scrum Project Management. In: Managing Information Technology. Springer, Cham. https://doi.org/10.1007/978-3-319-38891-5_8

			<ref name=PMBOK> Project Management Institute, Inc., ''"Guide to the Project Management Body of Knowledge".'' Project Management Institute, Inc (PMI), 6. edition (2017) </ref> Project Management Institute, Inc., ''"Guide to the Project Management Body of Knowledge".'' Project Management Institute, Inc (PMI), 6. edition (2017)

	<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref> Troels Jakobsen, ''"Scrum Done Right - Learn Agile Software Development".'' Lean Agile Ltd, 1st edition (2019)		<ref name=Troels> Troels Jakobsen, ''"Scrum Done Right".'' Lean Agile Ltd, 1st edition(2019) </ref> Troels Jakobsen, ''"Scrum Done Right - Learn Agile Software Development".'' Lean Agile Ltd, 1st edition (2019)

SanaIlyas at 13:25, 27 February 2021

2021-02-27T13:25:32Z

← Older revision		Revision as of 13:25, 27 February 2021
Line 160:		Line 160:

	This guide provide an excellent description and overview of all the artifacts, roles and activities in Scrum and were especially developed for Scrum Masters as reference work.		This guide provide an excellent description and overview of all the artifacts, roles and activities in Scrum and were especially developed for Scrum Masters as reference work.

			'''Hanslo R., Vahed A., Mnkandla E. (2020) Quantitative Analysis of the Scrum Framework. In: Przybyłek A., Morales-Trujillo M. (eds) Advances in Agile and User-Centred Software Engineering. LASD 2019, MIDI 2019. Lecture Notes in Business Information Processing, vol 376. Springer'''

			This study performs a quantitative analysis of the Scrum Framework using The Spearman collerelation analysis in South African organizations. Of the 14 factors studied, the 3 factors: Sprint Management, Complexity and Relative advantage have shown to have a statistically significant relation with Scrum adoption. This study can be used to gain more knowledge about factors that affect Scrum adoption.

			'''Hron, M., and Obwegeser N., (2018) Scrum in practice: an overview of Scrum adaptions. 51st Hawaii International Conference on System Sciences (HICSS 2018), Curran Associates, Inc., p. 5445-5454.'''

			This study provide an overview of the proposed adaptions and their implications by augmenting or combining the Agile software development practices with other tools and methods. However, this study only covers 31 studies after a filtering process.

	==References==		==References==