Rapid Application Development in Extreme Project Management - Revision history

S141926 at 21:45, 21 September 2015

2015-09-21T21:45:16Z

← Older revision		Revision as of 21:45, 21 September 2015
Line 98:		Line 98:
	*Appropriate managers for this uncertain atmosphere available. Due to the high trial-error it is important that the managers in charge of this sort of project are able to keep the employees motivated and ready for facing some sort of disappointments throughout the project. These managers must also possess innovation and quick reaction skills which make them effective and productive managers.		*Appropriate managers for this uncertain atmosphere available. Due to the high trial-error it is important that the managers in charge of this sort of project are able to keep the employees motivated and ready for facing some sort of disappointments throughout the project. These managers must also possess innovation and quick reaction skills which make them effective and productive managers.

	*Companies ~~must~~ help growing the knowledge of the employees and keep them updated with the new tools. The selection of these tools will be an important factor in terms of efficiency of the project~~. Frequent feedback is a must during all~~ the ~~project especially due to the constantly changing requirements that imply an extreme project~~.		*Companies help growing the knowledge of the employees and keep them updated with the new tools. The selection of these tools will be an important factor in terms of efficiency of the project and the employees will be given training on them.


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

S141926 at 21:43, 21 September 2015

2015-09-21T21:43:25Z

← Older revision		Revision as of 21:43, 21 September 2015
Line 90:		Line 90:
	==Discussion==		==Discussion==

	To success ~~managing an extreme project with~~ Rapid ~~Methodology~~, ~~it is vital that~~ the following characteristics apply:		The success of combining Extreme Project Management and Rapid Methods depends on a number of factors, but if most of the following characteristics apply to the project it will surely have been a good decision.

	*It is likely that the requirements will change during the project or that unexpected events occur that make the manager have to reschedule. In the kind of projects where the desired result is very clear but how to reach it is unclear as well as in projects where innovation is an everyday task and new methods and tools that can help the project are being developed as the project goes.		*It is likely that the requirements will change during the project or that unexpected events occur that make the manager have to reschedule. In the kind of projects where the desired result is very clear but how to reach it is unclear as well as in projects where innovation is an everyday task and new methods and tools that can help the project are being developed as the project goes.

S141926 at 21:37, 21 September 2015

2015-09-21T21:37:37Z

← Older revision		Revision as of 21:37, 21 September 2015
Line 1:		Line 1:
			== Background ==
	Extreme Project Management is a modern approach to [https://en.wikipedia.org/wiki/Project_management Project Management] that differs from other traditional methods for its ability to have new or changing requirements throughout the project. This has become especially interesting in today’s projects, where, they tend to require changes very frequently, due to a number of reasons such as Stakeholders changing their mind often, news about economical/environmental concerns, unexpected successes in the construction site and so on.		Extreme Project Management is a modern approach to [https://en.wikipedia.org/wiki/Project_management Project Management] that differs from other traditional methods for its ability to have new or changing requirements throughout the project. This has become especially interesting in today’s projects, where, they tend to require changes very frequently, due to a number of reasons such as Stakeholders changing their mind often, news about economical/environmental concerns, unexpected successes in the construction site and so on.

Line 49:		Line 49:
	The method is based on meeting the requirements of the desired result involving the stakeholders from the start and focusing all the way on their need managing risks in order to avoid setbacks. The approach focuses on adjusting requirements as the user earns knowledge as the project progresses which makes this method especially interesting for extreme projects. It is also a very flexible method so it is adapted to the changes easily, which is not the case for traditional approaches where the requirements are rigorously defined from the start.		The method is based on meeting the requirements of the desired result involving the stakeholders from the start and focusing all the way on their need managing risks in order to avoid setbacks. The approach focuses on adjusting requirements as the user earns knowledge as the project progresses which makes this method especially interesting for extreme projects. It is also a very flexible method so it is adapted to the changes easily, which is not the case for traditional approaches where the requirements are rigorously defined from the start.
	In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.		In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.
	~~Main~~ factors and ~~common issues associated~~ to ~~rapid methods.~~
			==== The four main factors, their problems and how to overcome them ====
	There are a number of factors associated to Rapid methods that will lead to the success or failure of the project. Those factors were summarized to four by the Rapid Development and Project Management expert Steve McConell: <ref name=mc> "McConell, S. (1996). Rapid development: Taming wild software schedules. Redmond, Washington: Microsoft Press." </ref> People, Process, Product and Technology. The mistakes associated to those factors will be the trigger for slow development and likely failure, as it will be discussed after defining the four factors.		There are a number of factors associated to Rapid methods that will lead to the success or failure of the project. Those factors were summarized to four by the Rapid Development and Project Management expert Steve McConell: <ref name=mc> "McConell, S. (1996). Rapid development: Taming wild software schedules. Redmond, Washington: Microsoft Press." </ref> People, Process, Product and Technology. The mistakes associated to those factors will be the trigger for slow development and likely failure, as it will be discussed after defining the four factors.

Line 63:		Line 64:
	! scope="row"\| PEOPLE		! scope="row"\| PEOPLE
	\|Clearly, employees taking part in the project play an important role in the success of the project, basically they are thee one in charge of transforming the knowledge into products or whatever is the desired result. Therefore companies have to find ways to increase the skills, knowledge and level of proficiency of their employees in order to be competitive and also try to maintain them happy so they continue growing the company’s potential		\|Clearly, employees taking part in the project play an important role in the success of the project, basically they are thee one in charge of transforming the knowledge into products or whatever is the desired result. Therefore companies have to find ways to increase the skills, knowledge and level of proficiency of their employees in order to be competitive and also try to maintain them happy so they continue growing the company’s potential
	\| It has been proven <ref name="oth”> " DeMarco, T. a. (1999). Peopleware: Productive projects and teams. New York, US: Dorset House Publishing."</ref> that issues concerning people have the highest impact on both productivity and quality. Some common scenarios are project managers with highly technical backgrounds with poor people management knowledge leading to a high employee turnover. This turnover along with contracting new people once the project is started pretending to meet an unlikely deadline cause a decrease in productivity as well as frustration on all people involved		\| It has been proven <ref name="oth”> " DeMarco, T. a. (1999). Peopleware: Productive projects and teams. New York, US: Dorset House Publishing."</ref> that issues concerning people have the highest impact on both productivity and quality. Some common scenarios are project managers with highly technical backgrounds with poor people management knowledge leading to a high employee turnover. This turnover along with contracting new people once the project is started pretending to meet an unlikely deadline cause a decrease in productivity as well as frustration on all people involved
	\| Provide guidance to working with teams and enhancing group dynamics to all the employees as well as train project managers to effectively manage their team members.		\| Provide guidance to working with teams and enhancing group dynamics to all the employees as well as train project managers to effectively manage their team members.
	\|-		\|-
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
Line 71:		Line 72:
	Improving the process the amount of rework will be reduced which leads to increased control of costs as well as the ability to make risk management decisions based on real data.		Improving the process the amount of rework will be reduced which leads to increased control of costs as well as the ability to make risk management decisions based on real data.
	\| Poorly defined procedures, guidelines and plans are usually the cause of slow development causing a waste of time of the employees. Also, over optimistic schedules increasing the risk of failure as well as poorly defined or changing standards of quality.		\| Poorly defined procedures, guidelines and plans are usually the cause of slow development causing a waste of time of the employees. Also, over optimistic schedules increasing the risk of failure as well as poorly defined or changing standards of quality.
	\| It is critical to identify, address and eliminate the sources of risk before they threat the project so a proper risk management analysis must be done.		\| It is critical to identify, address and eliminate the sources of risk before they threat the project so a proper risk management analysis must be done. <ref name=mc/>
	In order to fulfil the aimed standards of quality, Quality Assurance fundamentals with quality plans must be considered to ensure that the project is developed according to the defined processes and it also provides feedback about how effective the processes which can be a very useful information for the project managers.		In order to fulfil the aimed standards of quality, Quality Assurance fundamentals with quality plans must be considered to ensure that the project is developed according to the defined processes and it also provides feedback about how effective the processes which can be a very useful information for the project managers.
	\|-		\|-
Line 86:		Line 87:
	\| Software tools and other technology are constantly changing so it might be difficult to totally avoid the problems related to technology, especially in long projects where the implementation of a new tool in the medium of the project could be very beneficial at long term. It is therefore advisable to incorporate additional time for training the employees in the new technology		\| Software tools and other technology are constantly changing so it might be difficult to totally avoid the problems related to technology, especially in long projects where the implementation of a new tool in the medium of the project could be very beneficial at long term. It is therefore advisable to incorporate additional time for training the employees in the new technology
	\|}		\|}

			==Discussion==

			To success managing an extreme project with Rapid Methodology, it is vital that the following characteristics apply:

			*It is likely that the requirements will change during the project or that unexpected events occur that make the manager have to reschedule. In the kind of projects where the desired result is very clear but how to reach it is unclear as well as in projects where innovation is an everyday task and new methods and tools that can help the project are being developed as the project goes.

			*Meetings among stakeholders and managers can be carried out regularly during all the stages of the project. In the early state it is critical to fully agree and discuss all the details and requirements of the project to start in the best direction possible while later at the project if some unexpected event comes up, disagreement could happen and it becomes very important that the implied parties can be gathered together quickly and are willing to discuss in a collaborative manner.

			*Appropriate managers for this uncertain atmosphere available. Due to the high trial-error it is important that the managers in charge of this sort of project are able to keep the employees motivated and ready for facing some sort of disappointments throughout the project. These managers must also possess innovation and quick reaction skills which make them effective and productive managers.

			*Companies must help growing the knowledge of the employees and keep them updated with the new tools. The selection of these tools will be an important factor in terms of efficiency of the project. Frequent feedback is a must during all the project especially due to the constantly changing requirements that imply an extreme project.


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

S141926 at 18:33, 21 September 2015

2015-09-21T18:33:43Z

← Older revision		Revision as of 18:33, 21 September 2015
Line 39:		Line 39:


	==Managing extreme projects with rapid ~~methods~~==		==Managing extreme projects with rapid methodology==

	===Overview===		===Overview===
Line 46:		Line 46:
	It focuses on gathering all the requirements for the project itself at the very beginning. The project manager must identify the stakeholders and along with the team members undertake the planning process in an open and collaborative manner. <ref name=jak>"Jakobsen, C. M. (2001). XPM from idea to realization. Synopsis" </ref> . This process implies that the stakeholders that might be in disagreement are together and open for discussion. It is a key point getting the stakeholders on agreement on the scope, goals and procedure which might be challenging task sometimes.		It focuses on gathering all the requirements for the project itself at the very beginning. The project manager must identify the stakeholders and along with the team members undertake the planning process in an open and collaborative manner. <ref name=jak>"Jakobsen, C. M. (2001). XPM from idea to realization. Synopsis" </ref> . This process implies that the stakeholders that might be in disagreement are together and open for discussion. It is a key point getting the stakeholders on agreement on the scope, goals and procedure which might be challenging task sometimes.

	===~~How the application~~ of ~~rapid models benefit extreme projects~~===		===Use of Rapid Methodology to manage Extreme Projects ===
	The method is based on meeting the requirements of the desired result involving the stakeholders from the start and focusing all the way on their need managing risks in order to avoid setbacks. The approach focuses on adjusting requirements as the user earns knowledge as the project progresses which makes this method especially interesting for extreme projects. It is also a very flexible method so it is adapted to the changes easily, which is not the case for traditional approaches where the requirements are rigorously defined from the start.		The method is based on meeting the requirements of the desired result involving the stakeholders from the start and focusing all the way on their need managing risks in order to avoid setbacks. The approach focuses on adjusting requirements as the user earns knowledge as the project progresses which makes this method especially interesting for extreme projects. It is also a very flexible method so it is adapted to the changes easily, which is not the case for traditional approaches where the requirements are rigorously defined from the start.
	In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.		In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.
Line 55:		Line 55:
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\|-		\|-
	! scope="col"\| ~~Factor~~		! scope="col"\|
	! scope="col"\| Overview		! scope="col"\| Overview
	! scope="col"\| Common issues		! scope="col"\| Common issues
	! scope="col"\| ~~Recommendations~~		! scope="col"\| How to avoid them
	\|-		\|-
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"

S141926: /* Traditional approach overview */

2015-09-21T16:44:32Z

Traditional approach overview

← Older revision		Revision as of 16:44, 21 September 2015
Line 16:		Line 16:
	The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable <ref name=kli> "Kliem, R. (1997). Project Management Methodology: a practical quide for the next millenium. New York ,NY, US: Marcel Dekker." </ref>. By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.		The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable <ref name=kli> "Kliem, R. (1997). Project Management Methodology: a practical quide for the next millenium. New York ,NY, US: Marcel Dekker." </ref>. By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.

	The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out.<ref name=wyssecond> "Wysocki, R. K. (2010). Adaptative Project Framework. Managing complexity in the face of uncertainty. Pearson Eduation, Inc~~." </ref>. Effective Project Management: Traditional, Agile, Extreme. Indiniapolis: Wiley Publishing~~." </ref>. So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.		The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out.<ref name=wyssecond> "Wysocki, R. K. (2010). Adaptative Project Framework. Managing complexity in the face of uncertainty. Pearson Eduation, Inc." </ref>.So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.

	== Extreme Project Management ==		== Extreme Project Management ==

S141926 at 16:41, 21 September 2015

2015-09-21T16:41:42Z

← Older revision		Revision as of 16:41, 21 September 2015
Line 29:		Line 29:

	===Extreme projects are demanding===		===Extreme projects are demanding===
	They require a high degree of speed and innovation due to the constantly changing requirements. The former is important due to the fact that if one spends too much time studying the project and considering what next step to take by the time the plan is ready it might be irrelevant and not useful anymore. While the latter, innovation, is probably what extreme management is all about. It is what makes the difference and what makes a project manager to be effective and productive. One cannot shorten the project time line in half by working twice as hard but working efficiently innovating for each of the single and unique projects.		They require a high degree of speed and innovation due to the constantly changing requirements. The former is important due to the fact that if one spends too much time studying the project and considering what next step to take by the time the plan is ready it might be irrelevant and not useful anymore. While the latter, innovation, is probably what extreme management is all about. It is what makes the difference and what makes a project manager to be effective and productive. One cannot shorten the project time line in half by working twice as hard but working efficiently innovating for each of the single and unique projects. [[File:drawing.jpg \|thumb\|\|right\|\|300px\|Approaches representation]]
	Extreme projects require discovering what is truly necessary for the plan to proceed and succeed by a sort of trial-error process, day by day. Like Doug DeCarlo defines extreme project; “An extreme project is complex, self-correcting venture in search of a desirable result”.<ref name=decar />		Extreme projects require discovering what is truly necessary for the plan to proceed and succeed by a sort of trial-error process, day by day. Like Doug DeCarlo defines extreme project; “An extreme project is complex, self-correcting venture in search of a desirable result”.<ref name=decar />

Line 38:		Line 38:
	It has been previously mentioned that extreme projects are messy and chaotic and this is not anybody’s fault, it is how it is. Things happen while plans are being made without anything one can do but responding to it as good as possible. For this reason an Extreme Project does not follow the Traditional Project Model which is based on the waterfall model, a sequential process in which progress is shown as a flowing steadily downwards through different phases that lead to a well-defined goal with a proven path to get to the objective. Instead, XPM even though that has a clear goal it has a more undefined path which is said not to be straight but redirected every time that something new comes up, which is frequent. An example used in a number of management books is that extreme managing is shooting a gun towards a goal and throughout the process the “bullet” is redirected several times.		It has been previously mentioned that extreme projects are messy and chaotic and this is not anybody’s fault, it is how it is. Things happen while plans are being made without anything one can do but responding to it as good as possible. For this reason an Extreme Project does not follow the Traditional Project Model which is based on the waterfall model, a sequential process in which progress is shown as a flowing steadily downwards through different phases that lead to a well-defined goal with a proven path to get to the objective. Instead, XPM even though that has a clear goal it has a more undefined path which is said not to be straight but redirected every time that something new comes up, which is frequent. An example used in a number of management books is that extreme managing is shooting a gun towards a goal and throughout the process the “bullet” is redirected several times.

	~~[[File:drawing.jpg]]~~
	==Managing extreme projects with rapid methods==		==Managing extreme projects with rapid methods==

S141926 at 16:22, 21 September 2015

2015-09-21T16:22:10Z

S141926 at 16:00, 21 September 2015

2015-09-21T16:00:14Z

Show changes

S141926 at 14:50, 21 September 2015

2015-09-21T14:50:44Z

← Older revision		Revision as of 14:50, 21 September 2015
Line 1:		Line 1:
	== Abstract ==		== Abstract ==
	Extreme Project Management is a modern approach to project management that differs from other traditional methods for its ability to have new or changing requirements throughout the project. This has become especially interesting in today’s projects, where, they tend to require changes very frequently, due to a number of reasons such as Stakeholders changing their mind often, news about economical/environmental concerns, unexpected successes in the construction site and so on.		Extreme Project Management is a modern approach to project management that differs from other traditional methods for its ability to have new or changing requirements throughout the project. This has become especially interesting in today’s projects, where, they tend to require changes very frequently, due to a number of reasons such as Stakeholders changing their mind often, news about economical/environmental concerns, unexpected successes in the construction site and so on.

	Those arisen problems during the execution of the project are one of the main challenges of the traditional project management methods. In the extreme approach, a project has no fixed project phases nor set of guidelines on how the activities should be executed but it adapts to the current situation and performs the best way possible. In contrast with the step-by-step workflow that characterizes the traditional model and its strict requirements the extreme method is more suitable to face the common unexpected changes that come up during today’s projects.		Those arisen problems during the execution of the project are one of the main challenges of the traditional project management methods. In the extreme approach, a project has no fixed project phases nor set of guidelines on how the activities should be executed but it adapts to the current situation and performs the best way possible. In contrast with the step-by-step workflow that characterizes the traditional model and its strict requirements the extreme method is more suitable to face the common unexpected changes that come up during today’s projects.

	While the traditional approaches are characterized for a sequential design process known as the Waterfall Model, where the process takes the form of a linear-sequential model so each phase must be fully completed before the next one can start, the Extreme Project Management uses a different concept based on Rapid Application Development (RAD) called Rapid Planning which focuses more on development rather than planning.		While the traditional approaches are characterized for a sequential design process known as the Waterfall Model, where the process takes the form of a linear-sequential model so each phase must be fully completed before the next one can start, the Extreme Project Management uses a different concept based on Rapid Application Development (RAD) called Rapid Planning which focuses more on development rather than planning.

	In the present article the Extreme Project Management will be described and its main differences with the traditional approach highlighted. It will follow how to deal with XPM by means of Rapid Planning.		In the present article the Extreme Project Management will be described and its main differences with the traditional approach highlighted. It will follow how to deal with XPM by means of Rapid Planning.

	__TOC__		__TOC__



	== Overview of Project Management ==		== Overview of Project Management ==
Line 12:		Line 14:
	The way that project managers deal with projects nowadays has not only changed totally during the last decades but also irreversibly (DeCarlo, 2004).		The way that project managers deal with projects nowadays has not only changed totally during the last decades but also irreversibly (DeCarlo, 2004).
	The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable (Kliem, 1997). By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.		The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable (Kliem, 1997). By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.

	The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out. (Wysocki, Adaptative Project Framework. Managing complexity in the face of uncertainty, 2010) So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.		The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out. (Wysocki, Adaptative Project Framework. Managing complexity in the face of uncertainty, 2010) So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.

Line 19:		Line 22:

	In the Traditional approach there was generally rejection of a change throughout the project. This was viewed as an anomaly, so even though it was not acceptable had to be managed somehow and here is where the problems rose. The inflexibility surrounding this approach often led to create an uncomfortable atmosphere on the team where the main attention was put on meeting deadlines regardless the consequences. (Kliem, 1997). Generally speaking, the basis of the traditional approach is managing the known.		In the Traditional approach there was generally rejection of a change throughout the project. This was viewed as an anomaly, so even though it was not acceptable had to be managed somehow and here is where the problems rose. The inflexibility surrounding this approach often led to create an uncomfortable atmosphere on the team where the main attention was put on meeting deadlines regardless the consequences. (Kliem, 1997). Generally speaking, the basis of the traditional approach is managing the known.

	The opposite definition applies for Extreme Project Management, where “Extreme Project Managers are required to manage the unknown” (DeCarlo, 2004), characterizing this sort of projects for being besides unpredictable also messy and chaotic where innovation is crucial due to the constantly changing environment. Those changes are not only a result of the uncertainty surrounding the project itself but also due to external factors such as new technology, changes in regulations, requirements, moves of the competitors, unexpected results during testing, political decisions that might affect, economic crisis, change in the customer needs and so on and so forth.		The opposite definition applies for Extreme Project Management, where “Extreme Project Managers are required to manage the unknown” (DeCarlo, 2004), characterizing this sort of projects for being besides unpredictable also messy and chaotic where innovation is crucial due to the constantly changing environment. Those changes are not only a result of the uncertainty surrounding the project itself but also due to external factors such as new technology, changes in regulations, requirements, moves of the competitors, unexpected results during testing, political decisions that might affect, economic crisis, change in the customer needs and so on and so forth.

	Professor Robert K. Wysocki refers to this change of attitude from the traditional approach giving the following suggestion that reflects the above explained: (Wysocki, 2010)		Professor Robert K. Wysocki refers to this change of attitude from the traditional approach giving the following suggestion that reflects the above explained: (Wysocki, 2010)
	~~“Forget~~ about a formal change-management process in which the change request is documented, reviewed by the portfolio committee (…) Extreme projects can’t wait that long. Another approach is ~~needed”~~		<nowiki> “</nowiki>''Forget about a formal change-management process in which the change request is documented, reviewed by the portfolio committee (…) Extreme projects can’t wait that long. Another approach is needed'' <nowiki> “</nowiki>

	===Extreme projects are demanding===		===Extreme projects are demanding===
Line 35:		Line 40:
	FIGURE HERE		FIGURE HERE

	=~~MANAGING EXTREME PROJECTS WITH RAPID PLANNING~~=		=Managing extreme projects with rapid methods=

	==Overview==		==Overview==

S141926 at 14:43, 21 September 2015

2015-09-21T14:43:30Z

← Older revision		Revision as of 14:43, 21 September 2015
Line 6:		Line 6:
	__TOC__		__TOC__

	~~=== XPM vs. Traditional approach ===~~
	~~=== When should XPM be used? ===~~
	~~=== Change of mentality of the users ===~~
	~~== Rapid Application Development Concept ==~~
	~~=== Definition ===~~
	~~=== Application of RAD on XPM ===~~
	~~=== Limitations ===~~
	~~== References ==~~

	== Overview of Project Management ==		== Overview of Project Management ==
Line 89:		Line 82:
	\| Software tools and other technology are constantly changing so it might be difficult to totally avoid the problems related to technology, especially in long projects where the implementation of a new tool in the medium of the project could be very beneficial at long term. It is therefore advisable to incorporate additional time for training the employees in the new technology		\| Software tools and other technology are constantly changing so it might be difficult to totally avoid the problems related to technology, especially in long projects where the implementation of a new tool in the medium of the project could be very beneficial at long term. It is therefore advisable to incorporate additional time for training the employees in the new technology
	\|}		\|}


			== References ==

← Older revision		Revision as of 16:22, 21 September 2015
Line 16:		Line 16:
	The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable <ref name=kli> "Kliem, R. (1997). Project Management Methodology: a practical quide for the next millenium. New York ,NY, US: Marcel Dekker." </ref>. By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.		The traditional approach was characterized for being rather rigid and structured under the assumption that the future was predictable <ref name=kli> "Kliem, R. (1997). Project Management Methodology: a practical quide for the next millenium. New York ,NY, US: Marcel Dekker." </ref>. By studying the project, with deep analysis of risks and scheduling a proper forecast with a good degree of confidence was reachable. This approach was highly focused on efficiency, e.g. minimizing cost and time was vital. Another aspect of interest was finding a good balance among cost, schedule and quality. Most of the times it was considered it to be a zero-sum game where from achieving one of them project managers often had to sacrifice one, or two, of the rest.

	The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out. (Wysocki, Adaptative Project Framework. Managing complexity in the face of uncertainty, ~~2010)~~ So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.		The traditional project management life cycle is defined by five phases: Definition, Detailed Plan, Launch plan, Monitoring Progress and Closing out.<ref name=wyssecond> "Wysocki, R. K. (2010). Adaptative Project Framework. Managing complexity in the face of uncertainty. Pearson Eduation, Inc." </ref>. Effective Project Management: Traditional, Agile, Extreme. Indiniapolis: Wiley Publishing." </ref>. So the project manager is given a clear statement from the customer of what is wanted and when as well as how much is the customer willing to pay for it so there is no much room for changes. It is also expected that the customer will not change his mind throughout the process and that no external factors will have a big impact on it.

	== Extreme Project Management ==		== Extreme Project Management ==
Line 26:		Line 26:
	The opposite definition applies for Extreme Project Management, where “Extreme Project Managers are required to manage the unknown” <ref name=decar /> , characterizing this sort of projects for being besides unpredictable also messy and chaotic where innovation is crucial due to the constantly changing environment. Those changes are not only a result of the uncertainty surrounding the project itself but also due to external factors such as new technology, changes in regulations, requirements, moves of the competitors, unexpected results during testing, political decisions that might affect, economic crisis, change in the customer needs and so on and so forth.		The opposite definition applies for Extreme Project Management, where “Extreme Project Managers are required to manage the unknown” <ref name=decar /> , characterizing this sort of projects for being besides unpredictable also messy and chaotic where innovation is crucial due to the constantly changing environment. Those changes are not only a result of the uncertainty surrounding the project itself but also due to external factors such as new technology, changes in regulations, requirements, moves of the competitors, unexpected results during testing, political decisions that might affect, economic crisis, change in the customer needs and so on and so forth.

	Professor Robert K. Wysocki refers to this change of attitude from the traditional approach giving the following suggestion that reflects the above explained: (Wysocki, ~~2010~~) <nowiki> “</nowiki>''Forget about a formal change-management process in which the change request is documented, reviewed by the portfolio committee (…) Extreme projects can’t wait that long. Another approach is needed'' <nowiki> “</nowiki>		Professor Robert K. Wysocki refers to this change of attitude from the traditional approach giving the following suggestion that reflects the above explained: <ref name=wys> "Wysocki, R. K. (2009). Effective Project Management: Traditional, Agile, Extreme. Indiniapolis: Wiley Publishing." </ref> <nowiki> “</nowiki>''Forget about a formal change-management process in which the change request is documented, reviewed by the portfolio committee (…) Extreme projects can’t wait that long. Another approach is needed'' <nowiki> “</nowiki>

	===Extreme projects are demanding===		===Extreme projects are demanding===
Line 38:		Line 38:
	It has been previously mentioned that extreme projects are messy and chaotic and this is not anybody’s fault, it is how it is. Things happen while plans are being made without anything one can do but responding to it as good as possible. For this reason an Extreme Project does not follow the Traditional Project Model which is based on the waterfall model, a sequential process in which progress is shown as a flowing steadily downwards through different phases that lead to a well-defined goal with a proven path to get to the objective. Instead, XPM even though that has a clear goal it has a more undefined path which is said not to be straight but redirected every time that something new comes up, which is frequent. An example used in a number of management books is that extreme managing is shooting a gun towards a goal and throughout the process the “bullet” is redirected several times.		It has been previously mentioned that extreme projects are messy and chaotic and this is not anybody’s fault, it is how it is. Things happen while plans are being made without anything one can do but responding to it as good as possible. For this reason an Extreme Project does not follow the Traditional Project Model which is based on the waterfall model, a sequential process in which progress is shown as a flowing steadily downwards through different phases that lead to a well-defined goal with a proven path to get to the objective. Instead, XPM even though that has a clear goal it has a more undefined path which is said not to be straight but redirected every time that something new comes up, which is frequent. An example used in a number of management books is that extreme managing is shooting a gun towards a goal and throughout the process the “bullet” is redirected several times.

	~~FIGURE HERE~~		[[File:drawing.jpg]]

	==Managing extreme projects with rapid methods==		==Managing extreme projects with rapid methods==

Line 51:		Line 50:
	In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.		In order to fully benefit from this methods it is vital to get a deep understanding of the client’s needs and all the implied parties to avoid misunderstanding that can lead to setbacks and disputes. Frequent checking and updated feedback of the process to let the client know the current situation and redirect as soon as possible if the process is getting out of the scope.
	Main factors and common issues associated to rapid methods.		Main factors and common issues associated to rapid methods.
	There are a number of factors associated to Rapid methods that will lead to the success or failure of the project. Those factors were summarized to four by the Rapid Development and Project Management expert Steve McConell: (McConell, 1996) People, Process, Product and Technology. The mistakes associated to those factors will be the trigger for slow development and likely failure, as it will be discussed after defining the four factors.		There are a number of factors associated to Rapid methods that will lead to the success or failure of the project. Those factors were summarized to four by the Rapid Development and Project Management expert Steve McConell: <ref name=mc> "McConell, S. (1996). Rapid development: Taming wild software schedules. Redmond, Washington: Microsoft Press." </ref> People, Process, Product and Technology. The mistakes associated to those factors will be the trigger for slow development and likely failure, as it will be discussed after defining the four factors.

	{\| class="wikitable" style="text-align:left;"		{\| class="wikitable" style="text-align:left;"