Risk - Revision history

Shakila: /* When to use the tool */

2021-02-28T13:56:52Z

When to use the tool

← Older revision		Revision as of 13:56, 28 February 2021
Line 122:		Line 122:

	==== When to use the tool ====		==== When to use the tool ====
	The PPR tool is useful for large projects especially within IT as IT companies usually need formalized innovation strategy. The tool avoids uncertainties and duplications as using the tool lead to decreasing in prework. Furthermore, it makes sure that failures from previous projects don’t appear again in future projects.		The PPR tool is useful for large projects especially within IT as IT companies usually need formalized innovation strategy. The tool can be used in international IT companies that have implemented an IT solution or system in one country that must also be implemented in another country.
			The tool avoids uncertainties and duplications as using the tool lead to decreasing in prework. Furthermore, it makes sure that failures from previous projects don’t appear again in future projects.

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

Shakila: /* Pros and Cons */

2021-02-28T13:50:27Z

Pros and Cons

← Older revision		Revision as of 13:50, 28 February 2021
Line 118:		Line 118:
	==== Pros and Cons ====		==== Pros and Cons ====

	There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as money.		There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as money. In addition, all prework is done so there is no need to make duplications. This makes it possible to spend time researching what, where and why the previous project failed and thus improve it in the new project. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation but just copy the previous project. Another con is that project managers are often not prepared for unseen events in the project as they just follow the previous project.
	~~Moreover~~, all prework ~~are~~ done where
	Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.
	<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>		<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>

Shakila: /* Pros and Cons */

2021-02-28T13:44:53Z

Pros and Cons

← Older revision		Revision as of 13:44, 28 February 2021
Line 118:		Line 118:
	==== Pros and Cons ====		==== Pros and Cons ====

	There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as ~~duplications~~. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.		There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as money.
			Moreover, all prework are done where
			Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.
	<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>		<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>

Shakila: /* Proc and Cons */

2021-02-28T13:34:18Z

Proc and Cons

← Older revision		Revision as of 13:34, 28 February 2021
Line 116:		Line 116:


	==== ~~Proc~~ and Cons ====		==== Pros and Cons ====

	There are both ~~proc~~ and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as duplications. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.		There are both pros and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as duplications. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.
	<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>		<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>

Shakila: /* Proc and Cons */

2021-02-28T13:30:08Z

Proc and Cons

← Older revision		Revision as of 13:30, 28 February 2021
Line 118:		Line 118:
	==== Proc and Cons ====		==== Proc and Cons ====

	There are both proc and cons associated with this tool. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as duplications. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.		There are both proc and cons associated with this tool as with all other tools. For structured frameworks, the tool is fantastic as it is possible to use it slavishly and thus save time as well as duplications. Furthermore, it can be seen what went well and what could be improved. On the other hand, some of the cons are that the previous projects are followed too much that the managers don’t think about improvements, changes or innovation. Another con is that project managers are often not prepared for unseen events in the project.
	<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>		<ref name="eight"> http://www.innovation-portal.info/toolkits/post-project-reviews/ </ref>


	==== When to use the tool ====		==== When to use the tool ====

Shakila: /* Post-project review (PPR) */

2021-02-28T13:29:17Z

Post-project review (PPR)

← Older revision		Revision as of 13:29, 28 February 2021
Line 113:		Line 113:
	Post-project review is a management tool that gives the opportunity to learn from previous projects. The purpose of the tool PPR is to analyze potential failures and successes of a project or process. It simplifies what went well and what could be better in a project. It minimizes risks and uncertainties as it is possible to learn from previous experiences and failures to improve future projects.		Post-project review is a management tool that gives the opportunity to learn from previous projects. The purpose of the tool PPR is to analyze potential failures and successes of a project or process. It simplifies what went well and what could be better in a project. It minimizes risks and uncertainties as it is possible to learn from previous experiences and failures to improve future projects.

	First and foremost, the scope of the project must be defined. Then it must be examined whether a similar project has been carried out. If this has been the case, the knowledge and experiences from the previous project must be used, investigated and implemented in the project. However, if a similar project has not been performed before, then prework must be done. The project can then be implemented. Lastly, it is important to share the experiences and knowledge of the system, what went well and what didn’t and why. Otherwise, future projects may not benefit from the PPR tool and therefore are no reason to use the tool.		First and foremost, the scope of the project must be defined. Then it must be examined whether a similar project has been carried out. If this has been the case, the knowledge and experiences from the previous project must be used, investigated and implemented in the project. However, if a similar project has not been performed before, then prework must be done. The project can then be implemented. Lastly, it is important to share the experiences and knowledge of the system, what went well and what didn’t and why. Otherwise, future projects may not benefit from the PPR tool and therefore there are no reason to use the tool.

Shakila: /* Post-project review (PPR) */

2021-02-28T13:28:26Z

Post-project review (PPR)

← Older revision		Revision as of 13:28, 28 February 2021
Line 112:		Line 112:

	Post-project review is a management tool that gives the opportunity to learn from previous projects. The purpose of the tool PPR is to analyze potential failures and successes of a project or process. It simplifies what went well and what could be better in a project. It minimizes risks and uncertainties as it is possible to learn from previous experiences and failures to improve future projects.		Post-project review is a management tool that gives the opportunity to learn from previous projects. The purpose of the tool PPR is to analyze potential failures and successes of a project or process. It simplifies what went well and what could be better in a project. It minimizes risks and uncertainties as it is possible to learn from previous experiences and failures to improve future projects.

	First and foremost, the scope of the project must be defined. Then it must be examined whether a similar project has been carried out. If this has been the case, the knowledge and experiences from the previous project must be used, investigated and implemented in the project. However, if a similar project has not been performed before, then prework must be done. The project can then be implemented. Lastly, it is important to share the experiences and knowledge of the system, what went well and what didn’t and why. Otherwise, future projects may not benefit from the PPR tool and therefore are no reason to use the tool.		First and foremost, the scope of the project must be defined. Then it must be examined whether a similar project has been carried out. If this has been the case, the knowledge and experiences from the previous project must be used, investigated and implemented in the project. However, if a similar project has not been performed before, then prework must be done. The project can then be implemented. Lastly, it is important to share the experiences and knowledge of the system, what went well and what didn’t and why. Otherwise, future projects may not benefit from the PPR tool and therefore are no reason to use the tool.

Line 122:		Line 123:

	==== When to use the tool ====		==== When to use the tool ====
	The PPR tool is useful for large projects especially within IT as IT companies usually need formalized innovation strategy. The tool avoids uncertainties and duplications as using the tool lead to decreasing in prework. Furthermore, it makes sure that failures from previous projects don’t appear again in future projects.		The PPR tool is useful for large projects especially within IT as IT companies usually need formalized innovation strategy. The tool avoids uncertainties and duplications as using the tool lead to decreasing in prework. Furthermore, it makes sure that failures from previous projects don’t appear again in future projects.


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

Shakila: /* Potential problem analysis (PPA) */

2021-02-28T13:26:44Z

Potential problem analysis (PPA)

← Older revision		Revision as of 13:26, 28 February 2021
Line 99:		Line 99:

	[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]		[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]

			Figure 3 shows how the tool can be used. A table is set up with 8 columns respectively project stage, potential problems, likelihood, impact, PP risk number, possible causes, prevention measures and contingency plans.
			The project stage is described, the potential problems are identified. The likelihood/probability of failure is described by giving a number between 1-10, where 10 is given for the failure with the highest probability. Then it is described how much influence the failures have on the project or program. A PP-risk number is then calculated. Possible causes are identified to prevent and manage the risks and prevention measures are taken. Ultimately, a contingency plan is implemented.


	The tool is primary used when working on a large and complex project and as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.		The tool is primary used when working on a large and complex project and as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.

Shakila: /* Potential problem analysis (PPA) */

2021-02-28T13:08:37Z

Potential problem analysis (PPA)

← Older revision		Revision as of 13:08, 28 February 2021
Line 100:		Line 100:
	[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]		[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]

	The tool is primary used when working on a large and complex project as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.		The tool is primary used when working on a large and complex project and as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.
	<ref name="seven"> https://www.kepner-tregoe.com/lp/problem-solving-and-decision-making-workshop/ </ref>		<ref name="seven"> https://www.kepner-tregoe.com/lp/problem-solving-and-decision-making-workshop/ </ref>

Shakila: /* Potential problem analysis (PPA) */

2021-02-28T13:07:27Z

Potential problem analysis (PPA)

← Older revision		Revision as of 13:07, 28 February 2021
Line 100:		Line 100:
	[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]		[[File:PPA.png\|600x600px\|thumb\|'''Figure 3''': Example of the PPA (own figure)]]

	The tool is primary used when working on a large and complex project. Moreover, to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.		The tool is primary used when working on a large and complex project as the project is already large and complex, it can be difficult for project managers to identify and investigate risks and uncertainties in the project, program and portfolio. Using the risk management tool PPA, it is possible to identify risks that would not otherwise be seen. Moreover, the tool helps the project managers to meet deadlines without investing a lot of time and money on risk and changes, solving future problems and prevent uncertainties. The tool prioritizes which problems need to be addressed immediately, however is it hard to rate risks.
	<ref name="seven"> https://www.kepner-tregoe.com/lp/problem-solving-and-decision-making-workshop/ </ref>		<ref name="seven"> https://www.kepner-tregoe.com/lp/problem-solving-and-decision-making-workshop/ </ref>


	== Post-project review (PPR) ==		== Post-project review (PPR) ==