The Agile methodology and its frameworks - Revision history

Tkokotas at 14:07, 18 December 2018

2018-12-18T14:07:41Z

← Older revision		Revision as of 14:07, 18 December 2018
Line 1:		Line 1:
			''Developed by Sofia Griggio''


	''Project management is the application of knowledge, skills, tools and techniques to project activities to meet the project requirement''. <ref> A Guide to the Project Management Body of Knowledge, Fifth edition, Project Management Institute </ref>		''Project management is the application of knowledge, skills, tools and techniques to project activities to meet the project requirement''. <ref> A Guide to the Project Management Body of Knowledge, Fifth edition, Project Management Institute </ref>
	Traditionally, in order to manage a project, the sequential methods were largely used. According to these models, all the stages in a product’s life cycle are sequential.		Traditionally, in order to manage a project, the sequential methods were largely used. According to these models, all the stages in a product’s life cycle are sequential.

SofiaGriggio: /* Limitations */

2016-09-26T21:44:06Z

Limitations

← Older revision		Revision as of 21:44, 26 September 2016
Line 225:		Line 225:

	*Deep customer involvement: while the client engagement can assure that the delivery matches the expectations and needs, in some cases it could be difficult to require the total devotion of the customer to the project		*Deep customer involvement: while the client engagement can assure that the delivery matches the expectations and needs, in some cases it could be difficult to require the total devotion of the customer to the project
	*Lack of proper documentation, that can create critical situations in case of new programmers		*Lack of proper documentation, that can create critical situations in case of new programmers and employees' turnover

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

SofiaGriggio: /* Limitations */

2016-09-26T21:43:30Z

Limitations

← Older revision		Revision as of 21:43, 26 September 2016
Line 210:		Line 210:
	''Scrum:''		''Scrum:''

	*Prioritization of short-term solutions		*Prioritization of short-term solutions through the use of sprints
	*Lack of future vision: developing large scale companies in a highly regulated environment (e.g. healthcare) need to provide accurate release forecasts		*Lack of future vision: developing large scale companies in a highly regulated environment (e.g. healthcare) need to provide accurate release forecasts
	*Lack of visibility		*Lack of visibility of the "big picture" and of the project in its entire complexity
	*Non conformance of large feature in one sprint <ref> Developer-driven big-bang process transition from Scrum to Kanban, Nikitina, N., Kajko-Mattson, M., International Conference on Software and Systems Process, 2011 </ref>		*Non conformance of large feature in one sprint <ref> Developer-driven big-bang process transition from Scrum to Kanban, Nikitina, N., Kajko-Mattson, M., International Conference on Software and Systems Process, 2011 </ref>

Line 218:		Line 218:

	*There could be bottlenecks due to the absence of regular deadlines		*There could be bottlenecks due to the absence of regular deadlines
	*Not enough control over the release		*Not enough control over the release, in fact feedback and evaluation are not included in the process
	*Big features are not split into smaller ones so it might take long time to be developed		*Big features are not split into smaller ones so it might take long time to be developed
	*Training and education must be carefully managed <ref> Developer-driven big-bang process transition from Scrum to Kanban, Nikitina, N., Kajko-Mattson, M., International Conference on Software and Systems Process, 2011 </ref>		*Training and education must be carefully managed <ref> Developer-driven big-bang process transition from Scrum to Kanban, Nikitina, N., Kajko-Mattson, M., International Conference on Software and Systems Process, 2011 </ref>

SofiaGriggio: /* Limitations */

2016-09-26T21:41:03Z

Limitations

← Older revision		Revision as of 21:41, 26 September 2016
Line 205:		Line 205:
	==Limitations==		==Limitations==

	Agile frameworks are not suitable for the application in certain ~~enginnering~~ contexts that do not allow continuous iterations, such as the automotive industry.		Agile frameworks are not suitable for the application in certain engineering contexts that do not allow continuous iterations, such as the automotive industry.
	Scrum, Kanban and Extreme programming are extremely useful to manage a project, but their application includes some limitations, here sorted according to the different tools.		Scrum, Kanban and Extreme programming are extremely useful to manage a project, but their application includes some limitations, here sorted according to the different tools.

SofiaGriggio: /* Comparison */

2016-09-26T21:40:39Z

Comparison

← Older revision		Revision as of 21:40, 26 September 2016
Line 201:		Line 201:
	Extreme programming is deeply focused on delivering a high-quality output to the customer through a set of core engineering practices that guarantee simplicity but also customer satisfaction.		Extreme programming is deeply focused on delivering a high-quality output to the customer through a set of core engineering practices that guarantee simplicity but also customer satisfaction.

	Scrum, Kanban and Extreme programming can be applied to different contexts, but they can be also adapted to specific needs and mixed in order to obtain customised tools that are more useful than a simple strict application of the principles.		Scrum, Kanban and Extreme programming can be applied to different contexts, but they can be also adapted to specific needs and mixed in order to obtain customised tools that are more useful than a simple, strict and one-size-fits-all application of the principles.

	==Limitations==		==Limitations==

SofiaGriggio: /* Teams and roles */

2016-09-26T21:32:12Z

Teams and roles

← Older revision		Revision as of 21:32, 26 September 2016
Line 53:		Line 53:
	The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic is the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.		The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic is the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.


	The '''scrum master''' is engaged in ensuring that the scrum theory and principles are fully understood and that everyone is behaving and working in compliance to them. Moreover, he has the role to identify the not really helpful interactions and processes and to correct them.		The '''scrum master''' is engaged in ensuring that the scrum theory and principles are fully understood and that everyone is behaving and working in compliance to them. Moreover, he has the role to identify the not really helpful interactions and processes and to correct them.

SofiaGriggio: /* Teams and roles */

2016-09-26T21:31:54Z

Teams and roles

← Older revision		Revision as of 21:31, 26 September 2016
Line 51:		Line 51:
	The '''product owner''' is in charge of maximizing the value of the product and the work of the development team. This process may differ, depending on the company, the scrum teams and the people. More precisely, the product owner is responsible for the management of the product backlog (the list of all the desired features of the output), which includes the following activities: listing all the product backlog items, ordering the items of the product backlog in order to facilitate the achievement of the goals, optimising the work performed by the development team, ensuring visibility, transparency and clearness of the product backlog, making sure the development team understands the items in the product backlog.		The '''product owner''' is in charge of maximizing the value of the product and the work of the development team. This process may differ, depending on the company, the scrum teams and the people. More precisely, the product owner is responsible for the management of the product backlog (the list of all the desired features of the output), which includes the following activities: listing all the product backlog items, ordering the items of the product backlog in order to facilitate the achievement of the goals, optimising the work performed by the development team, ensuring visibility, transparency and clearness of the product backlog, making sure the development team understands the items in the product backlog.

	The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic ~~inìs~~ the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.		The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic is the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.
	~~All the team members are at the same level and no sub-groups can be formed. The different participants may have their own area of expertise but all of them are responsible for the group outcome.~~

	The '''scrum master''' is engaged in ensuring that the scrum theory and principles are fully understood and that everyone is behaving and working in compliance to them. Moreover, he has the role to identify the not really helpful interactions and processes and to correct them.		The '''scrum master''' is engaged in ensuring that the scrum theory and principles are fully understood and that everyone is behaving and working in compliance to them. Moreover, he has the role to identify the not really helpful interactions and processes and to correct them.

SofiaGriggio: /* Teams and roles */

2016-09-26T21:29:59Z

Teams and roles

← Older revision		Revision as of 21:29, 26 September 2016
Line 49:		Line 49:
	According to this methodology, the Scrum team consists of three roles: the product owner, the development team and the scrum master.		According to this methodology, the Scrum team consists of three roles: the product owner, the development team and the scrum master.

	The '''product owner''' is in charge of maximizing the value of the product and the work of the development team. This process may differ, depending on the company, the scrum teams and the people. More precisely, the product owner is responsible for the management of the product backlog, which includes the following activities: listing all the product backlog items, ordering the items of the product backlog in order to facilitate the achievement of the goals, optimising the work performed by the development team, ensuring visibility, transparency and clearness of the product backlog, making sure the development team understands the items in the product backlog.		The '''product owner''' is in charge of maximizing the value of the product and the work of the development team. This process may differ, depending on the company, the scrum teams and the people. More precisely, the product owner is responsible for the management of the product backlog (the list of all the desired features of the output), which includes the following activities: listing all the product backlog items, ordering the items of the product backlog in order to facilitate the achievement of the goals, optimising the work performed by the development team, ensuring visibility, transparency and clearness of the product backlog, making sure the development team understands the items in the product backlog.

	The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic inìs the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.		The '''development team''' is formed by experts with the role of developing the Increment that is released at the end of each sprint. These participants are the only one who can decide and manage the way to deliver their own work, which means that the teams are self-organizing. Another characteristic inìs the cross-functionality: it is decisive that the members have different backgrounds, skills and knowledge, in order to develop a complete Increment.

SofiaGriggio: /* Teams and roles */

2016-09-26T21:28:40Z

Teams and roles

← Older revision		Revision as of 21:28, 26 September 2016
Line 45:		Line 45:
	=====Teams and roles=====		=====Teams and roles=====

	The employees involved are organized in small teams which are cross- functional and self- organizing. The size of the teams is limited, the optimal number is approximately seven people.		The employees involved are organized in small teams which are cross-functional -the members have different backgrounds and skills- and self-organizing -the members organise their own work. The size of the teams is limited, the optimal number is approximately seven people.

	According to this methodology, the Scrum team consists of three roles: the product owner, the development team and the scrum master.		According to this methodology, the Scrum team consists of three roles: the product owner, the development team and the scrum master.

SofiaGriggio at 21:24, 26 September 2016

2016-09-26T21:24:15Z

← Older revision		Revision as of 21:24, 26 September 2016
Line 15:		Line 15:
	These three tools represent an important support for project management as they provide a valid guidance for the application of the Agile methodology in different contexts.		These three tools represent an important support for project management as they provide a valid guidance for the application of the Agile methodology in different contexts.

	After a short introduction regarding the Agile movement, each tool will be discussed both theoretically and in ~~the context of~~ a business example of real case; they will be compared and critically evaluated.		After a short introduction regarding the Agile movement, each tool will be discussed both theoretically and in connection with a business example of real case; they will be compared and critically evaluated.

	== Introduction to the Agile movement ==		== Introduction to the Agile movement ==