Agile & Traditional PM cocktail - Revision history

Tkokotas at 17:35, 16 November 2018

2018-11-16T17:35:13Z

← Older revision		Revision as of 17:35, 16 November 2018
Line 1:		Line 1:
			''Developed by Benedek Zajkas''


	== Abstract ==		== Abstract ==

Benedek Zajkas: /* Limitations */

2018-02-27T19:35:31Z

Limitations

← Older revision		Revision as of 19:35, 27 February 2018
Line 135:		Line 135:
	== Limitations ==		== Limitations ==

	The above proposed project management cocktail can serve as a high-level, initial guideline for projects combining elements from the agile and traditional approach. However it is very important to note that this framework is a mixture of theories, on a theoretical level. It is usually emphasized in the literature that learning project management can be best by doing projects <ref name="Doing"> Joana Geraldi, Christian Thuesen, Josef Oehmen, & Verena Stingl (2017) ‘How to DO projects’</ref>.. Therefore particular project characteristics and real life circumstances define what methodology can be best used for managing a specific project.		The above proposed project management cocktail can serve as a high-level, initial guideline for projects combining elements from the agile and traditional approach. However, it is very important to note that this framework is a mixture of theories, on a theoretical level. It is usually emphasized in the literature that learning project management can be best by ''doing'' projects <ref name="Doing"> Joana Geraldi, Christian Thuesen, Josef Oehmen, & Verena Stingl (2017) ‘How to DO projects’</ref>. Therefore particular project characteristics and real life circumstances define what methodology can be best used for managing a specific project.

	The proposed blended approach puts a great focus on people, their motivation and the way they work in small organizations with small teams. Large, complex organizations are not considered in this methodology and it certainly gives limitations to the blended approach. Furthermore it doesn’t reflect on those situations in which individuals live in different countries forming virtual teams, or because of organizational reasons other projects demand their part time work making them unable to work full-time.		The proposed blended approach puts a great focus on people, their motivation and the way they work in small organizations with small teams. Large, complex organizations are not considered in this methodology and it certainly gives limitations to the blended approach. Furthermore it doesn’t reflect on those situations in which individuals live in different countries forming virtual teams, or because of organizational reasons other projects demand their part time work making them unable to work full-time.
	Moreover the implementation of the blended approach can be difficult considering the organizational environment and culture as key factors. The organization can be unwilling to implement new approaches changing their best practices because of the intrinsic level of uncertainty and ambiguity relating to iterative processes (for example transition from traditional towards agile). Similarly team members and stakeholders might not be aligned with the chosen approach because of their personal biases, different backgrounds.		Moreover the implementation of the blended approach can be difficult considering the organizational environment and culture as key factors. The organization can be unwilling to implement new approaches changing their best practices because of the intrinsic level of uncertainty and ambiguity relating to iterative processes (for example transition from traditional towards agile). Similarly team members and stakeholders might not be aligned with the chosen approach because of their personal biases, different backgrounds.

	In most cases it is easier to choose an existing methodology than create a novel, own model. Existing methodologies have already been applied on different projects so the advantages of these previous experiences can be utilized. The goal of the project management methodology is to increase efficiency and effectiveness in order to promote project success. An inappropriate methodology can have negative impact on project success or at least make managing project harder. Hence it is very crucial to consider the specific project characteristics when choosing methodologies.		In most cases it is easier to choose an existing methodology than create a novel, own model. Existing methodologies have already been applied on different projects so the advantages of these previous experiences can be utilized. The goal of the project management methodology is to increase efficiency and effectiveness in order to promote project success. An inappropriate methodology can have negative impact on project success or at least make managing project harder. Hence it is very crucial to consider the specific project characteristics when choosing methodologies.



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

Benedek Zajkas: /* Application of the blended approach */

2018-02-27T19:30:56Z

Application of the blended approach

← Older revision		Revision as of 19:30, 27 February 2018
Line 68:		Line 68:
	=== Application of the blended approach ===		=== Application of the blended approach ===

	A hybrid method ~~was~~ developed by establishing correlation between the processes and the APs (Agile Principles). The resulting hybrid approach aims to combine the strengths of both approaches.		In the followings a hybrid method is developed by establishing correlation between the processes and the APs (Agile Principles). The resulting hybrid approach aims to combine the strengths of both approaches.

	==== Integration subject group ====		==== Integration subject group ====

Benedek Zajkas: /* Application of the agile approach */

2018-02-27T19:27:57Z

Application of the agile approach

← Older revision		Revision as of 19:27, 27 February 2018
Line 46:		Line 46:
	The agile approach and agile principles work very well within a single organization with smaller, standalone projects and can be used best for innovative, creative projects such as research projects, new product development projects and process improvement projects. These projects are characterized by a clear business need and vision, but on the other hand unclear project goals, high level of uncertainty, incomplete and unpredictable requests that can significantly change during the life cycle of the projects <ref name="agilemethodology"> [http://agilemethodology.org/ Agile Methodology website].</ref>. In case of the agile approach the emphasis is on execution and the project knowledge is mainly tacit without an accent on extensive documentation.		The agile approach and agile principles work very well within a single organization with smaller, standalone projects and can be used best for innovative, creative projects such as research projects, new product development projects and process improvement projects. These projects are characterized by a clear business need and vision, but on the other hand unclear project goals, high level of uncertainty, incomplete and unpredictable requests that can significantly change during the life cycle of the projects <ref name="agilemethodology"> [http://agilemethodology.org/ Agile Methodology website].</ref>. In case of the agile approach the emphasis is on execution and the project knowledge is mainly tacit without an accent on extensive documentation.

	One of the most common agile methodology is Scrum, which has an emphasis on software development. As it can be seen from figure xx the project lifecycle is divided into iteration cycles that are called sprints. All iterations contain a Planning, Design, Build, Test and Review phase <ref name="agilemethodology"> </ref>. These phases are similar to those seen in the waterfall model.		One of the most common agile methodology is Scrum, which has an emphasis on software development. As it can be seen from figure 2 the project lifecycle is divided into iteration cycles that are called sprints. All iterations contain a Planning, Design, Build, Test and Review phase <ref name="agilemethodology"> </ref>. These phases are similar to those seen in the waterfall model.

Benedek Zajkas at 19:24, 27 February 2018

2018-02-27T19:24:45Z

← Older revision		Revision as of 19:24, 27 February 2018
Line 29:		Line 29:
	One of the methodologies that is derived from the traditional approach is the waterfall methodology. As it is a sequential, linear model, it has a relatively simple application. Each phase is accomplished in a defined set of time that makes the planning and controlling easier. The distinct phases are Requirement analysis, System design, Implementation, Testing (verification) and Maintenance <ref name="Comparison"> Ms.Akshita Dubey, Ms.Amisha Jain, Ms.Aditi Mantri (2015) ‘COMPARATIVE STUDY: WATERFALL V/S AGILE MODEL’</ref>. The sequential process can be seen in Figure 1.		One of the methodologies that is derived from the traditional approach is the waterfall methodology. As it is a sequential, linear model, it has a relatively simple application. Each phase is accomplished in a defined set of time that makes the planning and controlling easier. The distinct phases are Requirement analysis, System design, Implementation, Testing (verification) and Maintenance <ref name="Comparison"> Ms.Akshita Dubey, Ms.Amisha Jain, Ms.Aditi Mantri (2015) ‘COMPARATIVE STUDY: WATERFALL V/S AGILE MODEL’</ref>. The sequential process can be seen in Figure 1.

	[[File:Waterfall1.jpg\|thumb\|center\|600px\|Figure 1: The waterfall model]]		[[File:Waterfall1.jpg\|thumb\|center\|600px\|Figure 1: The waterfall model <ref name="Comparison"> </ref>]]

	== Agile project management approach ==		== Agile project management approach ==

Benedek Zajkas at 19:23, 27 February 2018

2018-02-27T19:23:51Z

← Older revision		Revision as of 19:23, 27 February 2018
Line 49:		Line 49:


	[[File:Agileexam01.jpg\|thumb\|center\|900px\|Figure 2: The Scrum methodology]]		[[File:Agileexam01.jpg\|thumb\|center\|900px\|Figure 2: The Scrum methodology <ref name="agilemethodology"> </ref>]]

	== Comparison of the agile and traditional approach ==		== Comparison of the agile and traditional approach ==

Benedek Zajkas at 19:23, 27 February 2018

2018-02-27T19:23:13Z

← Older revision		Revision as of 19:23, 27 February 2018
Line 55:		Line 55:
	In the following table, the comparison of the agile and traditional project management approaches can be seen.		In the following table, the comparison of the agile and traditional project management approaches can be seen.

	[[File:Zbedi005.jpg\|1450px\|thumb\|center\|Table 2: Comparison of agile and traditional project management approach]]		[[File:Zbedi005.jpg\|1450px\|thumb\|center\|Table 2: Comparison of agile and traditional project management approach <ref name="Mix"> </ref>]]

	== A novel project management methodology: “the traditional and agile cocktail” ==		== A novel project management methodology: “the traditional and agile cocktail” ==

Benedek Zajkas at 19:19, 27 February 2018

2018-02-27T19:19:20Z

← Older revision		Revision as of 19:19, 27 February 2018
Line 40:		Line 40:
	The agile principles (AP) can be seen in the following table.		The agile principles (AP) can be seen in the following table.

	[[File:APprinc.jpg\|1450px\|thumb\|center\|Table 1: The agile principles]]		[[File:APprinc.jpg\|1450px\|thumb\|center\|Table 1: The agile principles <ref name="Manifesto"> </ref>]]

	=== Application of the agile approach ===		=== Application of the agile approach ===

Benedek Zajkas: /* Comparison of the agile and traditional approach */

2018-02-27T19:18:10Z

Comparison of the agile and traditional approach

← Older revision		Revision as of 19:18, 27 February 2018
Line 55:		Line 55:
	In the following table, the comparison of the agile and traditional project management approaches can be seen.		In the following table, the comparison of the agile and traditional project management approaches can be seen.

	[[File:Zbedi005.jpg\|1450px\|thumb\|center\|Table 1: Comparison of agile and traditional project management approach]]		[[File:Zbedi005.jpg\|1450px\|thumb\|center\|Table 2: Comparison of agile and traditional project management approach]]

	== A novel project management methodology: “the traditional and agile cocktail” ==		== A novel project management methodology: “the traditional and agile cocktail” ==

Benedek Zajkas: /* The agile principles (AP) and the agile manifesto */

2018-02-27T19:17:58Z

The agile principles (AP) and the agile manifesto

← Older revision		Revision as of 19:17, 27 February 2018
Line 40:		Line 40:
	The agile principles (AP) can be seen in the following table.		The agile principles (AP) can be seen in the following table.

	[[File:APprinc.jpg\|1450px\|thumb\|center\|Table 1: ~~Comparison of~~ agile ~~and traditional project management approach~~]]		[[File:APprinc.jpg\|1450px\|thumb\|center\|Table 1: The agile principles]]

	=== Application of the agile approach ===		=== Application of the agile approach ===