Agile Scrum Methodology - Revision history

S212838: /* Limitations & Challenges */

2022-03-20T10:13:34Z

Limitations & Challenges

← Older revision		Revision as of 10:13, 20 March 2022
Line 154:		Line 154:
	*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging. <ref name="avetdis" />		*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging. <ref name="avetdis" />

	*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict final deadline~~. Indeed, using Scrum method implies that there is no specific final deadline for the project~~. This could not fit with a lot of clients' expectations. <ref name="avetdis" />		*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict final deadline. This could not fit with a lot of clients' expectations. <ref name="avetdis" />

	*The use of Scrum method does not satisfy top management's need for budget, scope and schedule control. Indeed, the client will get what he asked for at the end but before beginning the project the client will not know how much it will cost, how long the project will last and what will the final product look like. To deal with this, some companies define a maximum budget not to be exceeded during the development of the product. This reduces the level of uncertainty. <ref name="umsl">University of Missouri–St. Louis, ''Scrum limitations and concern'', external link: [https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Egbuchiri/index2.html#ExecSumm] </ref>		*The use of Scrum method does not satisfy top management's need for budget, scope and schedule control. Indeed, the client will get what he asked for at the end but before beginning the project the client will not know how much it will cost, how long the project will last and what will the final product look like. To deal with this, some companies define a maximum budget not to be exceeded during the development of the product. This reduces the level of uncertainty. <ref name="umsl">University of Missouri–St. Louis, ''Scrum limitations and concern'', external link: [https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Egbuchiri/index2.html#ExecSumm] </ref>

S212838: /* Limitations & Challenges */

2022-03-20T10:13:05Z

Limitations & Challenges

← Older revision		Revision as of 10:13, 20 March 2022
Line 154:		Line 154:
	*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging. <ref name="avetdis" />		*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging. <ref name="avetdis" />

	*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict deadline. Indeed, using Scrum method implies that there is no specific final deadline for the project. This could not fit with a lot of clients' expectations. <ref name="avetdis" />		*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict final deadline. Indeed, using Scrum method implies that there is no specific final deadline for the project. This could not fit with a lot of clients' expectations. <ref name="avetdis" />

	*The use of Scrum method does not satisfy top management's need for budget, scope and schedule control. Indeed, the client will get what he asked for at the end but before beginning the project the client will not know how much it will cost, how long the project will last and what will the final product look like. To deal with this, some companies define a maximum budget not to be exceeded during the development of the product. This reduces the level of uncertainty. <ref name="umsl">University of Missouri–St. Louis, ''Scrum limitations and concern'', external link: [https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Egbuchiri/index2.html#ExecSumm] </ref>		*The use of Scrum method does not satisfy top management's need for budget, scope and schedule control. Indeed, the client will get what he asked for at the end but before beginning the project the client will not know how much it will cost, how long the project will last and what will the final product look like. To deal with this, some companies define a maximum budget not to be exceeded during the development of the product. This reduces the level of uncertainty. <ref name="umsl">University of Missouri–St. Louis, ''Scrum limitations and concern'', external link: [https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Egbuchiri/index2.html#ExecSumm] </ref>


	== Annotated Bibliography ==		== Annotated Bibliography ==

S212838 at 10:05, 20 March 2022

2022-03-20T10:05:52Z

← Older revision		Revision as of 10:05, 20 March 2022
Line 7:		Line 7:

	Scrum is based on the division of a project into "time boxes", called sprints that typically last one to three weeks. <ref name="longueur">Viter I.,''Everything You Need to Know About Sprint Planning'', in: ''Forecast'', 2020, external link: [https://www.forecast.app/blog/sprint-planning#:~:text=1%2Dweek%20sprint%3A%20For%20teams,to%20fast%2Dpaced%20structured%20work]</ref> The team is composed of a Product Owner, a Scrum Master and a small team of developers. <ref>Uzility, ''Introduction to Scrum - 7 Minutes'', 2014, external link: [https://www.youtube.com/watch?v=9TycLR0TqFA]</ref> Before each sprint, the Product Owner writes the “Product Backlog”, a prioritized list of features known as user stories that could go into the product. Each sprint starts with a Sprint Planning Meeting where all the members of the Scrum team can commit to the number of tasks they will be able to perform, as well as the creation of the “Sprint Backlog”, which is the overall list of tasks to be carried out during the sprint.		Scrum is based on the division of a project into "time boxes", called sprints that typically last one to three weeks. <ref name="longueur">Viter I.,''Everything You Need to Know About Sprint Planning'', in: ''Forecast'', 2020, external link: [https://www.forecast.app/blog/sprint-planning#:~:text=1%2Dweek%20sprint%3A%20For%20teams,to%20fast%2Dpaced%20structured%20work]</ref> The team is composed of a Product Owner, a Scrum Master and a small team of developers. <ref>Uzility, ''Introduction to Scrum - 7 Minutes'', 2014, external link: [https://www.youtube.com/watch?v=9TycLR0TqFA]</ref> Before each sprint, the Product Owner writes the “Product Backlog”, a prioritized list of features known as user stories that could go into the product. Each sprint starts with a Sprint Planning Meeting where all the members of the Scrum team can commit to the number of tasks they will be able to perform, as well as the creation of the “Sprint Backlog”, which is the overall list of tasks to be carried out during the sprint.
	During the sprint, the Scrum Master hosts daily 15-minute Stand-up Meetings where all members of the developer team can share what they did the day before, what they are working on today and identify any difficulties encountered that could hinder the smooth running of the sprint. Each sprint ends with a Sprint review, which consists of a demonstration of what has been completed and a discussion of what could be improved. Before starting a new sprint, a Retrospective Meeting takes place where all the Scrum team members work on what they can do to improve their process. By working incrementally, the team can learn from previous sprints to optimize the next. <ref name="slides">Lopez A., Milmine L., ''Agile Implementation Lessons Learned from Practical Application'', 2012, external link: [https://www.slideshare.net/nmtechcouncil/practical-application-of-scrum-final]</ref>		During the sprint, the Scrum Master hosts daily 15-minute Stand-up Meetings where all members of the developer team can share what they did the day before, what they are working on today and identify any difficulties encountered that could hinder the smooth running of the sprint. Each sprint ends with a Sprint review, which consists of a demonstration of what has been completed and a discussion of what could be improved. Before starting a new sprint, a Retrospective Meeting takes place where all the Scrum team members work on what they can do to improve their process. By working incrementally, the team can learn from previous sprints to optimize the next one. <ref name="slides">Lopez A., Milmine L., ''Agile Implementation Lessons Learned from Practical Application'', 2012, external link: [https://www.slideshare.net/nmtechcouncil/practical-application-of-scrum-final]</ref>

	Even though the efficiency of this method had been proved by its important use in different companies, implementing it for the first time is challenging. It beyond others requires extensive training and major changes within the organization. <ref name="avetdis">Indeed Editorial Team, ''List of Scrum Advantages and Disadvantages'', in: ''indeed'', 2021, external link: [https://www.indeed.com/career-advice/career-development/disadvantages-of-scrum]</ref>		Even though the efficiency of this method had been proved by its important use in different companies, implementing it for the first time is challenging. It beyond others requires extensive training and major changes within the organization. <ref name="avetdis">Indeed Editorial Team, ''List of Scrum Advantages and Disadvantages'', in: ''indeed'', 2021, external link: [https://www.indeed.com/career-advice/career-development/disadvantages-of-scrum]</ref>

S212838 at 10:02, 20 March 2022

2022-03-20T10:02:30Z

← Older revision		Revision as of 10:02, 20 March 2022
Line 1:		Line 1:
	''Written by Océane Haddad''		''Written by Océane Haddad''


	'''Abstract'''		'''Abstract'''

S212838 at 10:02, 20 March 2022

2022-03-20T10:02:21Z

← Older revision		Revision as of 10:02, 20 March 2022
Line 1:		Line 1:
			''Written by Océane Haddad''

	'''Abstract'''		'''Abstract'''

S212838 at 10:00, 20 March 2022

2022-03-20T10:00:49Z

S212838 at 09:44, 20 March 2022

2022-03-20T09:44:50Z

← Older revision		Revision as of 09:44, 20 March 2022
Line 12:		Line 12:
	=== Definition ===		=== Definition ===

	Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" /> Agility is "the ability to both create and respond to change in order to profit in a turbulent business environment." <ref name="agile">~~Jim~~ Highsmith, <u>What is Agility?</u>, in: ''thoughtworks'', 2012, external link: [https://www.thoughtworks.com/en-gb/insights/blog/what-agility]</ref>		Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" /> Agility is "the ability to both create and respond to change in order to profit in a turbulent business environment." <ref name="agile">Highsmith J., <u>What is Agility?</u>, in: ''thoughtworks'', 2012, external link: [https://www.thoughtworks.com/en-gb/insights/blog/what-agility]</ref>

	Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />		Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />
Line 143:		Line 143:
	== Limitations & Challenges ==		== Limitations & Challenges ==

	Despite all the advantages that provide this method, Scrum is not used in all companies. Indeed, implementing Scrum method in a company remains challenging and this method has several disadvantages: ~~<ref name="avetdis" />~~		Despite all the advantages that provide this method, Scrum is not used in all companies. Indeed, implementing Scrum method in a company remains challenging and this method has several disadvantages:

	*It requires extensive training and a well-trained and skillful team to be well implemented and efficient. It can take months and maybe even years to be efficient. The team has to understand and recognize the benefits and advantages of using this kind of method. The efficiency of this method in a specific team is then not guaranteed and can take a lot of time, sometimes leading the team to be discouraged.		*It requires extensive training and a well-trained and skillful team to be well implemented and efficient. It can take months and maybe even years to be efficient. The team has to understand and recognize the benefits and advantages of using this kind of method. The efficiency of this method in a specific team is then not guaranteed and can take a lot of time, sometimes leading the team to be discouraged. <ref name="avetdis" />

	*Scrum is more adapted for small to medium projects. Using this method for large projects can be really challenging. Indeed, large projects require extensive training and precise coordination. On the other hand, small projects can enable the company to be close to their customer and be efficient in the use of Scrum method.		*Scrum is more adapted for small to medium projects. Using this method for large projects can be really challenging. Indeed, large projects require extensive training and precise coordination. On the other hand, small projects can enable the company to be close to their customer and be efficient in the use of Scrum method. <ref name="avetdis" />

	*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging.		*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging. <ref name="avetdis" />

	*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict deadline. Indeed, using Scrum method implies that there is no specific final deadline for the project. This could not fit with a lot of clients' expectations.		*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict deadline. Indeed, using Scrum method implies that there is no specific final deadline for the project. This could not fit with a lot of clients' expectations. <ref name="avetdis" />

			*The use of Scrum method does not satisfy top management's need for budget, scope and schedule control. Indeed, the client will get what he asked for at the end but before beginning the project the client will not know how much it will cost, how long the project will last and what will the final product look like. To deal with this, some companies define a maximum budget not to be exceeded during the development of the product. This reduces the level of uncertainty. <ref name="umsl">University of Missouri–St. Louis, ''Scrum limitations and concern'', external link: [https://www.umsl.edu/~sauterv/analysis/Fall2013Papers/Egbuchiri/index2.html#ExecSumm] </ref>

S212838 at 09:32, 20 March 2022

2022-03-20T09:32:33Z

← Older revision		Revision as of 09:32, 20 March 2022
Line 143:		Line 143:
	== Limitations & Challenges ==		== Limitations & Challenges ==

	~~Implementing~~ Scrum method in a company remains challenging and this method has several disadvantages: <ref name="avetdis" />		Despite all the advantages that provide this method, Scrum is not used in all companies. Indeed, implementing Scrum method in a company remains challenging and this method has several disadvantages: <ref name="avetdis" />

	*It requires extensive training and a well-trained and skillful team to be well implemented and efficient. The team has to understand and recognize the benefits and advantages of using this kind of method.		*It requires extensive training and a well-trained and skillful team to be well implemented and efficient. It can take months and maybe even years to be efficient. The team has to understand and recognize the benefits and advantages of using this kind of method. The efficiency of this method in a specific team is then not guaranteed and can take a lot of time, sometimes leading the team to be discouraged.

	*Scrum is more adapted for small to medium projects. Using this method for large projects can be really challenging.		*Scrum is more adapted for small to medium projects. Using this method for large projects can be really challenging. Indeed, large projects require extensive training and precise coordination. On the other hand, small projects can enable the company to be close to their customer and be efficient in the use of Scrum method.

	*Major transformations within the organization can be required, which complicates even more the implementation of Scrum.		*Major transformations within the organization can be required, which complicates even more the implementation of Scrum. Indeed, it is never easy to implement a major organizational change in a company that has been functioning a certain way for years. Convincing the team of the efficiency and relevance of making these changes can be very challenging.

	*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability.		*Scrum might not be suitable for projects with very specific and defined deadlines and milestones and that require predictability. Using this method also implies that the project doesn’t have a strict deadline. Indeed, using Scrum method implies that there is no specific final deadline for the project. This could not fit with a lot of clients' expectations.

	*Using this method implies that the project doesn’t have a strict deadline.

S212838 at 09:06, 20 March 2022

2022-03-20T09:06:53Z

← Older revision		Revision as of 09:06, 20 March 2022
Line 12:		Line 12:
	=== Definition ===		=== Definition ===

	Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" />		Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" /> Agility is "the ability to both create and respond to change in order to profit in a turbulent business environment." <ref name="agile">Jim Highsmith, <u>What is Agility?</u>, in: ''thoughtworks'', 2012, external link: [https://www.thoughtworks.com/en-gb/insights/blog/what-agility]</ref>

	Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />		Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />

S212838 at 20:02, 7 March 2022

2022-03-07T20:02:54Z

← Older revision		Revision as of 20:02, 7 March 2022
Line 1:		Line 1:
	~~''Written by Océane Haddad - s212838''~~

	'''Abstract'''		'''Abstract'''

← Older revision		Revision as of 10:00, 20 March 2022
Line 3:		Line 3:
	Scrum is an agile method that was invented in the early 1990s by Ken Schwaber & Jeff Sutherland that aims at developing complex products in a different way than the classic Waterfall Method. <ref>Schwaber K., ''SCRUM Development Process'', 1995, external link: [https://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=9A8D9D71EE2E5E2567828E162B77D44E?doi=10.1.1.86.4164&rep=rep1&type=pdf] </ref> <ref name="guide">Schwaber K., Sutherland J., ''The Scrum Guide'', 2020, external link: [https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf]</ref>		Scrum is an agile method that was invented in the early 1990s by Ken Schwaber & Jeff Sutherland that aims at developing complex products in a different way than the classic Waterfall Method. <ref>Schwaber K., ''SCRUM Development Process'', 1995, external link: [https://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=9A8D9D71EE2E5E2567828E162B77D44E?doi=10.1.1.86.4164&rep=rep1&type=pdf] </ref> <ref name="guide">Schwaber K., Sutherland J., ''The Scrum Guide'', 2020, external link: [https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf]</ref>

	Scrum is based on the division of a project into "time boxes", called sprints that typically last one to three weeks. <ref name="longueur">Viter I.,~~<u>~~Everything You Need to Know About Sprint Planning~~</u>~~, in: ''Forecast'', 2020, external link: [https://www.forecast.app/blog/sprint-planning#:~:text=1%2Dweek%20sprint%3A%20For%20teams,to%20fast%2Dpaced%20structured%20work]</ref> The team is composed of a Product Owner, a Scrum Master and a small team of developers. <ref>Uzility, ''Introduction to Scrum - 7 Minutes'', 2014, external link: [https://www.youtube.com/watch?v=9TycLR0TqFA]</ref> Before each sprint, the Product Owner writes the “Product Backlog”, a prioritized list of features known as user stories that could go into the product. Each sprint starts with a Sprint Planning Meeting where all the members of the Scrum team can commit to the number of tasks they will be able to perform, as well as the creation of the “Sprint Backlog”, which is the overall list of tasks to be carried out during the sprint.		Scrum is based on the division of a project into "time boxes", called sprints that typically last one to three weeks. <ref name="longueur">Viter I.,''Everything You Need to Know About Sprint Planning'', in: ''Forecast'', 2020, external link: [https://www.forecast.app/blog/sprint-planning#:~:text=1%2Dweek%20sprint%3A%20For%20teams,to%20fast%2Dpaced%20structured%20work]</ref> The team is composed of a Product Owner, a Scrum Master and a small team of developers. <ref>Uzility, ''Introduction to Scrum - 7 Minutes'', 2014, external link: [https://www.youtube.com/watch?v=9TycLR0TqFA]</ref> Before each sprint, the Product Owner writes the “Product Backlog”, a prioritized list of features known as user stories that could go into the product. Each sprint starts with a Sprint Planning Meeting where all the members of the Scrum team can commit to the number of tasks they will be able to perform, as well as the creation of the “Sprint Backlog”, which is the overall list of tasks to be carried out during the sprint.
	During the sprint, the Scrum Master hosts daily 15-minute Stand-up Meetings where all members of the developer team can share what they did the day before, what they are working on today and identify any difficulties encountered that could hinder the smooth running of the sprint. Each sprint ends with a Sprint review, which consists of a demonstration of what has been completed and a discussion of what could be improved. Before starting a new sprint, a Retrospective Meeting takes place where all the Scrum team members work on what they can do to improve their process. By working incrementally, the team can learn from previous sprints to optimize the next. <ref name="slides">Lopez A., Milmine L., ''Agile Implementation Lessons Learned from Practical Application'', 2012, external link: [https://www.slideshare.net/nmtechcouncil/practical-application-of-scrum-final]</ref>		During the sprint, the Scrum Master hosts daily 15-minute Stand-up Meetings where all members of the developer team can share what they did the day before, what they are working on today and identify any difficulties encountered that could hinder the smooth running of the sprint. Each sprint ends with a Sprint review, which consists of a demonstration of what has been completed and a discussion of what could be improved. Before starting a new sprint, a Retrospective Meeting takes place where all the Scrum team members work on what they can do to improve their process. By working incrementally, the team can learn from previous sprints to optimize the next. <ref name="slides">Lopez A., Milmine L., ''Agile Implementation Lessons Learned from Practical Application'', 2012, external link: [https://www.slideshare.net/nmtechcouncil/practical-application-of-scrum-final]</ref>

	Even though the efficiency of this method had been proved by its important use in different companies, implementing it for the first time is challenging. It beyond others requires extensive training and major changes within the organization. <ref name="avetdis">Indeed Editorial Team, ~~<u>~~List of Scrum Advantages and Disadvantages~~</u>~~, in: ''indeed'', 2021, external link: [https://www.indeed.com/career-advice/career-development/disadvantages-of-scrum]</ref>		Even though the efficiency of this method had been proved by its important use in different companies, implementing it for the first time is challenging. It beyond others requires extensive training and major changes within the organization. <ref name="avetdis">Indeed Editorial Team, ''List of Scrum Advantages and Disadvantages'', in: ''indeed'', 2021, external link: [https://www.indeed.com/career-advice/career-development/disadvantages-of-scrum]</ref>

	== Scrum methodology ==		== Scrum methodology ==
Line 12:		Line 12:
	=== Definition ===		=== Definition ===

	Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" /> Agility is "the ability to both create and respond to change in order to profit in a turbulent business environment." <ref name="agile">Highsmith J., ~~<u>~~What is Agility?~~</u>~~, in: ''thoughtworks'', 2012, external link: [https://www.thoughtworks.com/en-gb/insights/blog/what-agility]</ref>		Scum is an agile method “that helps people, teams and organizations generate value through adaptive solutions for complex problems.” <ref name="guide" /> Agility is "the ability to both create and respond to change in order to profit in a turbulent business environment." <ref name="agile">Highsmith J., ''What is Agility?'', in: ''thoughtworks'', 2012, external link: [https://www.thoughtworks.com/en-gb/insights/blog/what-agility]</ref>

	Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />		Scrum method was invented in the early 1990s by Ken Schwaber & Jeff Sutherland, influenced by Hirotaka Takeuchi and Ikujiro Nonaka ideas. <ref>Sutherland J., ''Takeuchi and Nonaka: The Roots of Scrum'', 2011, external link: [https://www.scruminc.com/takeuchi-and-nonaka-roots-of-scrum/]</ref> The term “scrum” comes from the rugby vocabulary, a sport in which the team performs a scrum that allows a project, product or feature to be delivered and modified very quickly. Each player has a specific role in the scrum, and sprints during rugby matches are really important and decisive for the game. Comparatively to rugby, Scrum method is based on “sprints”, small time boxes of a few weeks where a team of about 8 people deliver a product. <ref name="guide" />
Line 26:		Line 26:
	The Scrum method is based on a team with specific roles.		The Scrum method is based on a team with specific roles.

	'''The Product Owner:''' <ref name="allemand"> Gonçalves L., ~~<u>~~Scrum : The methodology to become more agile~~</u>~~, in: ''Zeitschrift Für Controlling Und Management'', 2018</ref> The Product Owner is responsible for defining the features that are needed in the product. He is the key stakeholder who provides direction to the team for each sprint. He represents the client’s needs and wishes. He is also the one that establish the list of priorities of what should be developed and he validates the functionalities. Therefore, the Product Owner is responsible for the success and business value of the project.		'''The Product Owner:''' <ref name="allemand"> Gonçalves L., ''Scrum : The methodology to become more agile'', in: ''Zeitschrift Für Controlling Und Management'', 2018</ref> The Product Owner is responsible for defining the features that are needed in the product. He is the key stakeholder who provides direction to the team for each sprint. He represents the client’s needs and wishes. He is also the one that establish the list of priorities of what should be developed and he validates the functionalities. Therefore, the Product Owner is responsible for the success and business value of the project.

	'''The Scrum Master:''' <ref name="allemand" /> The Scrum Master is responsible for the smooth running of the Scrum process. He is totally focused on the process. He is the one running the meeting and keeping things going, assuring that there is a good communication between all team members. This way, he can be described as a process facilitator but not as a project or people manager. His role is to help team focus on value.		'''The Scrum Master:''' <ref name="allemand" /> The Scrum Master is responsible for the smooth running of the Scrum process. He is totally focused on the process. He is the one running the meeting and keeping things going, assuring that there is a good communication between all team members. This way, he can be described as a process facilitator but not as a project or people manager. His role is to help team focus on value.
Line 45:		Line 45:
	[[File:Sprint backlog.png \|thumb\|center\|500px\|Figure 1: Sprint Backlog <ref name="figures">Visual Paradigm, "What is Sprint Backlog in Scrum?", external link: [https://www.visual-paradigm.com/scrum/what-is-sprint-backlog-in-scrum/]</ref>]]		[[File:Sprint backlog.png \|thumb\|center\|500px\|Figure 1: Sprint Backlog <ref name="figures">Visual Paradigm, "What is Sprint Backlog in Scrum?", external link: [https://www.visual-paradigm.com/scrum/what-is-sprint-backlog-in-scrum/]</ref>]]

	'''User stories:''' <ref>Rehkopf M., ~~<u>~~User stories avec des exemples et un modèle~~</u>~~, in: ''ATLASSIAN'', external link: [https://www.atlassian.com/fr/agile/project-management/user-stories]</ref> A User story is a description of the user experience using the language, vocabulary and terminology of the user. Each user story has an identifier (a name that succinctly describes the function of the product), the importance (a value that defines the priority of the story), an estimate of the work required, a demonstration (a simple test of the story that will have to be validated) and the notes which include all the information necessary for the realization of the story.		'''User stories:''' <ref>Rehkopf M., ''User stories avec des exemples et un modèle'', in: ''ATLASSIAN'', external link: [https://www.atlassian.com/fr/agile/project-management/user-stories]</ref> A User story is a description of the user experience using the language, vocabulary and terminology of the user. Each user story has an identifier (a name that succinctly describes the function of the product), the importance (a value that defines the priority of the story), an estimate of the work required, a demonstration (a simple test of the story that will have to be validated) and the notes which include all the information necessary for the realization of the story.

	The User stories are described as follow: "As a ... (user), I need ... (something), so that ... (reason)". This way of phrasing allows the Product Owner to specify the right amount of detail for the team to estimate the size of a task.		The User stories are described as follow: "As a ... (user), I need ... (something), so that ... (reason)". This way of phrasing allows the Product Owner to specify the right amount of detail for the team to estimate the size of a task.
Line 110:		Line 110:
	=== Convince the team ===		=== Convince the team ===

	This part and the next one will rely on a success story of Bharath Malaivaiyavur, Scrum Master, that he shared in 2014. <ref>Malaivaiyavur B., ~~<u>~~Success Story: Transition from Agile-cum-Waterfall to Scrum~~</u>~~, in: ''ScrumAlliance'', 2014, external link: [https://www.scrumalliance.org/community/member-articles/586]</ref>		This part and the next one will rely on a success story of Bharath Malaivaiyavur, Scrum Master, that he shared in 2014. <ref>Malaivaiyavur B., ''Success Story: Transition from Agile-cum-Waterfall to Scrum'', in: ''ScrumAlliance'', 2014, external link: [https://www.scrumalliance.org/community/member-articles/586]</ref>

	Bharath Malaivaiyavur had about 13 years of experience in software services when he was trained as a Scrum Master. His mission was to implement Scrum at Global Products, the team that developed Internet products for their customer.		Bharath Malaivaiyavur had about 13 years of experience in software services when he was trained as a Scrum Master. His mission was to implement Scrum at Global Products, the team that developed Internet products for their customer.
Line 166:		Line 166:
	It is a presentation made by two certified Scrum Masters presented to NM Women in Technology. They start by explaining what is an Agile method before presenting the basics of the Scrum method as well as discussing their lessons learnt and giving a few recommendations for future Scrum Masters.		It is a presentation made by two certified Scrum Masters presented to NM Women in Technology. They start by explaining what is an Agile method before presenting the basics of the Scrum method as well as discussing their lessons learnt and giving a few recommendations for future Scrum Masters.

	*Malaivaiyavur B., ~~<u>~~Success Story: Transition from Agile-cum-Waterfall to Scrum~~</u>~~, in: ''ScrumAlliance'', 2014		*Malaivaiyavur B., ''Success Story: Transition from Agile-cum-Waterfall to Scrum'', in: ''ScrumAlliance'', 2014

	This is a success story written by a Certified Scrum Master about how he implemented for the first time Scrum method in a company. He explains the barriers he had to face with the client as well as how he convinced the team of the efficiency of this method.		This is a success story written by a Certified Scrum Master about how he implemented for the first time Scrum method in a company. He explains the barriers he had to face with the client as well as how he convinced the team of the efficiency of this method.