SCRUM Method - Revision history

Tkokotas at 15:42, 18 December 2018

2018-12-18T15:42:41Z

← Older revision		Revision as of 15:42, 18 December 2018
Line 1:		Line 1:
			''Developed by Nataliia Kulikova''

	== Introduction ==		== Introduction ==
	SCRUM is a one of the most used agile methodologies focusing on organizing and project management. The method’s foundation inheres the commercial product development work in 1986 elaborated by Hirotaka Takaeuchi and Ikujiro Nonaka and officially defined in a paper written by Jeff Sutherland and Ken Schwaber in 1995. The Agile Manifesto for software development published 1991 broadened usage of the technique aiming to continuous development of valuable software. <ref> ''http://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum'' The Roots of Scrum</ref>		SCRUM is a one of the most used agile methodologies focusing on organizing and project management. The method’s foundation inheres the commercial product development work in 1986 elaborated by Hirotaka Takaeuchi and Ikujiro Nonaka and officially defined in a paper written by Jeff Sutherland and Ken Schwaber in 1995. The Agile Manifesto for software development published 1991 broadened usage of the technique aiming to continuous development of valuable software. <ref> ''http://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum'' The Roots of Scrum</ref>

S140767: /* Annotated bibliography */

2015-09-28T23:58:56Z

Annotated bibliography

← Older revision		Revision as of 23:58, 28 September 2015
Line 105:		Line 105:
	Agile Product Management with Scrum. Roman Pichler. (2010): This book focuses on the role of the product owner and the challenges he/she faces in agile project management with Scrum. The book presents examples on how to take an advantage of emerging requirements, receive customer feedback in time, and how to ensure close collaboration within the development team. It facilitates the practitioner to fully understand possible challenges, how to avoid them, explains the structure and key elements within Scrum product management.		Agile Product Management with Scrum. Roman Pichler. (2010): This book focuses on the role of the product owner and the challenges he/she faces in agile project management with Scrum. The book presents examples on how to take an advantage of emerging requirements, receive customer feedback in time, and how to ensure close collaboration within the development team. It facilitates the practitioner to fully understand possible challenges, how to avoid them, explains the structure and key elements within Scrum product management.

	[http://proquestcombo.safaribooksonline.com.proxy.findit.dtu.dk/book/software-engineering-and-development/agile-development/9780321660534/introduction/pref05#X2ludGVybmFsX0h0bWxWaWV3P3htbGlkPTk3ODAzMjE2NjA1MzQlMkZwYXJ0MDMmcXVlcnk9 Succeeding with Agile. Mike Cohn (2009)]: The main objectives of the book is both - the introduction of the scrum for the beginners and implementing improvements into teamwork, test-driven development, quality and the management process itself.		Succeeding with Agile. Mike Cohn (2009): The main objectives of the book is both - the introduction of the scrum for the beginners and implementing improvements into teamwork, test-driven development, quality and the management process itself.

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

S140767: /* Artifacts */

2015-09-28T23:06:53Z

Artifacts

← Older revision		Revision as of 23:06, 28 September 2015
Line 54:		Line 54:

	=== Artifacts ===		=== Artifacts ===
	'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product ~~(features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated.~~ [[File:Sprint Burndown Chart.png\| thumb\| right\| 400px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]		'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product [[File:Sprint Burndown Chart.png\| thumb\| right\| 400px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]] (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated.
	The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.		The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.

S140767: /* Artifacts */

2015-09-28T23:06:31Z

Artifacts

← Older revision		Revision as of 23:06, 28 September 2015
Line 54:		Line 54:

	=== Artifacts ===		=== Artifacts ===
	'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.		'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. [[File:Sprint Burndown Chart.png\| thumb\| right\| 400px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]
	[[File:Sprint Burndown Chart.png\| thumb\| right\| 400px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]		The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.

	'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.		'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.

S140767: /* Artifacts */

2015-09-28T23:05:50Z

Artifacts

← Older revision		Revision as of 23:05, 28 September 2015
Line 55:		Line 55:
	=== Artifacts ===		=== Artifacts ===
	'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.		'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.
	[[File:Sprint Burndown Chart.png\| thumb\| right\| ~~200px~~\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]		[[File:Sprint Burndown Chart.png\| thumb\| right\| 400px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]
	'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.		'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.

S140767: /* Artifacts */

2015-09-28T23:05:41Z

Artifacts

← Older revision		Revision as of 23:05, 28 September 2015
Line 55:		Line 55:
	=== Artifacts ===		=== Artifacts ===
	'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.		'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.
	[[File:Sprint Burndown Chart.png\| thumb\| right\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]		[[File:Sprint Burndown Chart.png\| thumb\| right\| 200px\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]
	'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.		'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.

S140767: /* Artifacts */

2015-09-28T23:05:22Z

Artifacts

← Older revision		Revision as of 23:05, 28 September 2015
Line 55:		Line 55:
	=== Artifacts ===		=== Artifacts ===
	'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.		'''Product Backlog''' is a list of all tasks needed to develop a product including the requirements for the product (features, functions, technologies, and improvements) development and change. In other words, it is a To-Do list for the entire project, where the User Stories are estimated. The list is dynamic and changes along with customer’s requirements for the product. The responsible body for the Product Backlog is a Product Owner, who ensures that the changes in business requirements, market conditions, or technology are reflected and stored in a list. The latter incorporates items information about description, order, estimate, and value.
	[[File:Sprint Burndown Chart.png\| thumb\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]		[[File:Sprint Burndown Chart.png\| thumb\| right\| '''Figure 3:''' [http://blogs.atlassian.com/2014/02/evaluating-jira-agile-scrum-masters/ Sprint Burndown Chart.]Note, the guideline for the progress assuming that all tasks will be completed within the sprint is a ''grey line'', the remaining effort on daily basis is a ''red line'', ''X axis'' displays working days, ''Y axis'' displays Story Points]]
	'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.		'''Release Burndown Chart''' – is a graphical representation of the planned and remaining part of the project. It reflects the monitoring of the process and executed by the Product Owner in order to assess how the project aligns with the goal and desired time.

S140767: /* Advantages and pitfalls */

2015-09-28T23:04:42Z

Advantages and pitfalls

← Older revision		Revision as of 23:04, 28 September 2015
Line 96:		Line 96:
	*Another difficulty in managing scrum projects appears when customers do not understand the agile methodology and/or have difficulties with accepting the Scrum. In order to cope with this issue, an effective training and coaching have to be introduced.		*Another difficulty in managing scrum projects appears when customers do not understand the agile methodology and/or have difficulties with accepting the Scrum. In order to cope with this issue, an effective training and coaching have to be introduced.
	*Scrum agile methodology can also be problematic for companies who want to adopt and implement it. Moving from yearly or semi-annual releases to weekly iterations is very, very hard. And very easy to fail at. MOreover, the transit from individual contribution to the teamwork implies group conflicts and poor outcome.		*Scrum agile methodology can also be problematic for companies who want to adopt and implement it. Moving from yearly or semi-annual releases to weekly iterations is very, very hard. And very easy to fail at. MOreover, the transit from individual contribution to the teamwork implies group conflicts and poor outcome.
	*When the company adopting the scrum methodology ignores the philosophical principles of scrum, the organization may face the consequences of losing high productivity, great software quality, and happy customers.<ref> ''http://www.agileconnection.com/article/five-common-pitfalls-when-organizations-neglect-agile-values?page=0%2C0'' Five Common Pitfalls When Organizations Neglect Agile Values</ref>		*When the company adopting the scrum methodology ignores the philosophical principles of scrum, the organization may face the consequences of losing high productivity, great software quality, and happy customers.<ref> ''http://www.agileconnection.com/article/five-common-pitfalls-when-organizations-neglect-agile-values?page=0%2C0'' Five Common Pitfalls When Organizations Neglect Agile Values</ref><ref> ''https://communities.bmc.com/groups/india-user-group/blog/2012/08/05/challenges-and-opportunities-in-agilescrum'' Challenges and Opportunities in Agile/Scrum</ref><ref name="agile">Agile Product Manageement with Scrum. Roman Pichler. (2010). Addison-Wesley Professional </ref>
	<ref> ''https://communities.bmc.com/groups/india-user-group/blog/2012/08/05/challenges-and-opportunities-in-agilescrum'' Challenges and Opportunities in Agile/Scrum</ref> <ref name="agile">Agile Product Manageement with Scrum. Roman Pichler. (2010). Addison-Wesley Professional </ref>

	==Conclusion ==		==Conclusion ==

S140767: /* Advantages and pitfalls */

2015-09-28T23:04:07Z

Advantages and pitfalls

← Older revision		Revision as of 23:04, 28 September 2015
Line 86:		Line 86:
	*Development of team centric approach to software development rather that individual approach. Performance and productivity reflects the team’s collective efforts.		*Development of team centric approach to software development rather that individual approach. Performance and productivity reflects the team’s collective efforts.
	*The incremental delivery of the project developed during each Sprint enable some functionality to be ready to be delivered to the customer in a shorter time. Thus, customer satisfaction and high quality to be emphasized.		*The incremental delivery of the project developed during each Sprint enable some functionality to be ready to be delivered to the customer in a shorter time. Thus, customer satisfaction and high quality to be emphasized.
	*In contrast with the waterfall project management methodology, scrum process is characterised with absence of exhausting, costly documentation covering all aspects of a software project. ~~<ref>~~		*In contrast with the waterfall project management methodology, scrum process is characterised with absence of exhausting, costly documentation covering all aspects of a software project.
	*All functionalities are tested during the sprint due to a continuous review and changes’ adoption that takes place during during each sprint. Frequent testing enables receiving a prompt feedback from the customer that ensure in-time correction of uncovered mistakes.		*All functionalities are tested during the sprint due to a continuous review and changes’ adoption that takes place during during each sprint. Frequent testing enables receiving a prompt feedback from the customer that ensure in-time correction of uncovered mistakes.
	The aforementioned advantages may finally imply cost reduction within the organization and quality increase of the deliverables.<ref> ''https://www.exin.com/assets/exin/frameworks/124/whitepaper/Flyer-Agile-Scrum-EN.pdf'' AGILE SCRUM: the flexible and adaptable approach to any project</ref>		The aforementioned advantages may finally imply cost reduction within the organization and quality increase of the deliverables.<ref> ''https://www.exin.com/assets/exin/frameworks/124/whitepaper/Flyer-Agile-Scrum-EN.pdf'' AGILE SCRUM: the flexible and adaptable approach to any project</ref>

S140767: /* Advantages and pitfalls */

2015-09-28T23:03:46Z

Advantages and pitfalls

← Older revision		Revision as of 23:03, 28 September 2015
Line 88:		Line 88:
	*In contrast with the waterfall project management methodology, scrum process is characterised with absence of exhausting, costly documentation covering all aspects of a software project. <ref>		*In contrast with the waterfall project management methodology, scrum process is characterised with absence of exhausting, costly documentation covering all aspects of a software project. <ref>
	*All functionalities are tested during the sprint due to a continuous review and changes’ adoption that takes place during during each sprint. Frequent testing enables receiving a prompt feedback from the customer that ensure in-time correction of uncovered mistakes.		*All functionalities are tested during the sprint due to a continuous review and changes’ adoption that takes place during during each sprint. Frequent testing enables receiving a prompt feedback from the customer that ensure in-time correction of uncovered mistakes.
	The aforementioned advantages may finally imply cost reduction within the organization and quality increase of the deliverables.''https://www.exin.com/assets/exin/frameworks/124/whitepaper/Flyer-Agile-Scrum-EN.pdf'' AGILE SCRUM: the flexible and adaptable		The aforementioned advantages may finally imply cost reduction within the organization and quality increase of the deliverables.<ref> ''https://www.exin.com/assets/exin/frameworks/124/whitepaper/Flyer-Agile-Scrum-EN.pdf'' AGILE SCRUM: the flexible and adaptable approach to any project</ref>
	approach to any project</ref>

	Despite the simplicity and growing popularity of the method, there are some '''pitfalls''' while using the scrum methodology.		Despite the simplicity and growing popularity of the method, there are some '''pitfalls''' while using the scrum methodology.
Line 97:		Line 96:
	*Another difficulty in managing scrum projects appears when customers do not understand the agile methodology and/or have difficulties with accepting the Scrum. In order to cope with this issue, an effective training and coaching have to be introduced.		*Another difficulty in managing scrum projects appears when customers do not understand the agile methodology and/or have difficulties with accepting the Scrum. In order to cope with this issue, an effective training and coaching have to be introduced.
	*Scrum agile methodology can also be problematic for companies who want to adopt and implement it. Moving from yearly or semi-annual releases to weekly iterations is very, very hard. And very easy to fail at. MOreover, the transit from individual contribution to the teamwork implies group conflicts and poor outcome.		*Scrum agile methodology can also be problematic for companies who want to adopt and implement it. Moving from yearly or semi-annual releases to weekly iterations is very, very hard. And very easy to fail at. MOreover, the transit from individual contribution to the teamwork implies group conflicts and poor outcome.
	*When the company adopting the scrum methodology ignores the philosophical principles of scrum, the organization may face the consequences of losing high productivity, great software quality, and happy customers.		*When the company adopting the scrum methodology ignores the philosophical principles of scrum, the organization may face the consequences of losing high productivity, great software quality, and happy customers.<ref> ''http://www.agileconnection.com/article/five-common-pitfalls-when-organizations-neglect-agile-values?page=0%2C0'' Five Common Pitfalls When Organizations Neglect Agile Values</ref>
	<ref> ''http://www.agileconnection.com/article/five-common-pitfalls-when-organizations-neglect-agile-values?page=0%2C0'' Five Common Pitfalls When Organizations Neglect Agile Values</ref>
	<ref> ''https://communities.bmc.com/groups/india-user-group/blog/2012/08/05/challenges-and-opportunities-in-agilescrum'' Challenges and Opportunities in Agile/Scrum</ref> <ref name="agile">Agile Product Manageement with Scrum. Roman Pichler. (2010). Addison-Wesley Professional </ref>		<ref> ''https://communities.bmc.com/groups/india-user-group/blog/2012/08/05/challenges-and-opportunities-in-agilescrum'' Challenges and Opportunities in Agile/Scrum</ref> <ref name="agile">Agile Product Manageement with Scrum. Roman Pichler. (2010). Addison-Wesley Professional </ref>