Rambøll2020

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 24: Line 24:
 
This tool is one of the methods that is used the most in system reliability, maintainability and security analysis. It is used to determine which undesired events could happen. This method starts by having a conclusion from where specific causes are determined by constructing the fault tree. When using this method, the purpose is to identify potential causes of a failure before it happens. When the analysis is performed it can be determined what happens based on the different factors through the tree. <ref>ASG. ''What Is a Fault Tree Analysis?''. ASQ. Retrieved from http://asq.org/quality-progress/2002/03/problem-solving/what-is-a-fault-tree-analysis.html.The benefits of this method is that it creates a visual understanding of the events and it is easy for other people to get a quick understanding of the results. The fault tree is like a foundation for further analyses. It is easy to go through the tree to check for failures in other or future projects, to make sure that the risk for bad events are minimized. The model also has to be updated if it is going to be used later on, which can be time consuming if there is no one currently working with the method.  
 
This tool is one of the methods that is used the most in system reliability, maintainability and security analysis. It is used to determine which undesired events could happen. This method starts by having a conclusion from where specific causes are determined by constructing the fault tree. When using this method, the purpose is to identify potential causes of a failure before it happens. When the analysis is performed it can be determined what happens based on the different factors through the tree. <ref>ASG. ''What Is a Fault Tree Analysis?''. ASQ. Retrieved from http://asq.org/quality-progress/2002/03/problem-solving/what-is-a-fault-tree-analysis.html.The benefits of this method is that it creates a visual understanding of the events and it is easy for other people to get a quick understanding of the results. The fault tree is like a foundation for further analyses. It is easy to go through the tree to check for failures in other or future projects, to make sure that the risk for bad events are minimized. The model also has to be updated if it is going to be used later on, which can be time consuming if there is no one currently working with the method.  
 
This method is often used in engineering industries where there may be huge consequences of failures.  
 
This method is often used in engineering industries where there may be huge consequences of failures.  
Step 1:Define the undesired event: the primary fault or failure being analyzed
+
Step 1: Define the undesired event: the primary fault or failure being analyzed
 
Step 2: Deduce the event's immediate causes
 
Step 2: Deduce the event's immediate causes
 
Step 3: Keep stepping back through events until the most basic causes are identified
 
Step 3: Keep stepping back through events until the most basic causes are identified
Line 37: Line 37:
 
By asking the questions “Have we got to where we want to be in the project?” and “When are we going to finish this project?”, it helps to define a more specific plan as to where the project is going to end.
 
By asking the questions “Have we got to where we want to be in the project?” and “When are we going to finish this project?”, it helps to define a more specific plan as to where the project is going to end.
 
When the value of work done is equal to the planned the basic principle of EVM is achieved. The following indicators can be used to describe how good/bad the project are performed:   
 
When the value of work done is equal to the planned the basic principle of EVM is achieved. The following indicators can be used to describe how good/bad the project are performed:   
Schedule variance (SV); difference between actually work done vs the amount of planned work to be done. This will show if the project follows the timeplan.  
+
- Schedule variance (SV); difference between actually work done vs the amount of planned work to be done. This will show if the project follows the timeplan.  
{{columns-list|colwidth=10em|
+
- Cost variance (CV); difference between the cost for the project vs the budget that was made. This shows if the project is on budget.  
*Cost variance (CV); difference between the cost for the project vs the budget that was made. This shows if the project is on budget.  
+
- Schedule performance index (SPI); ratio between the approved budget for the performed work to the approved budget for the planned work in the first place. A measure of the project’s time efficiency.  
*Schedule performance index (SPI); ratio between the approved budget for the performed work to the approved budget for the planned work in the first place. A measure of the project’s time efficiency.  
+
- Cost performance index (CPI); ratio between approved budgets for the performed work to the actually spent budget for the stipulated work. <ref>APMG International. ''What is Earned Value Management and Why is it Important?''. APMG International. Retrieved from https://apmg-international.com/article/what-earned-value-management-and-why-it-important.
*Cost performance index (CPI); ratio between approved budgets for the performed work to the actually spent budget for the stipulated work. <ref>APMG International. ''What is Earned Value Management and Why is it Important?''. APMG International. Retrieved from https://apmg-international.com/article/what-earned-value-management-and-why-it-important.
+
}}
+
  
  

Revision as of 23:24, 22 February 2020

Collection of tools

Risk Management In Project Portfolios

Including Risk Management in Construction Projects

Mapping Stakeholders/Stakeholder Management Cite error: Closing </ref> missing for <ref> tag ]]

Secondly we want to evaluate a stakeholder match by Stakeholder Compatibility. This is done by categorizing the relationships into the “Four Stakeholder Configurations”. It is also this step where the “Stakeholder Matrix” comes in play, which is an interest/power matrix. Lastly Stakeholder Management involves creating stakeholder engagement. In this step we utilize “Stakeholder Engagement approaches” and “Stakeholder integration methods”.


Fault Tree Analysis This tool is one of the methods that is used the most in system reliability, maintainability and security analysis. It is used to determine which undesired events could happen. This method starts by having a conclusion from where specific causes are determined by constructing the fault tree. When using this method, the purpose is to identify potential causes of a failure before it happens. When the analysis is performed it can be determined what happens based on the different factors through the tree. Cite error: Closing </ref> missing for <ref> tag ]]

The figure above is known as the business canvas model, in that it has 9 building blocks, the are as follow, KP is Keypartners , KA is Key activities, KR is key resources, VP is value proposition, CR is customer relationship, CH is channels, CS is customer segment, CS is cost structure and RS is revenue streams.

The use of this tool, is to divide the business model into smaller parts/blocks which provide a better overview of the whole picture, and make the process for any change tangible.


SWOT SWOT-analysis is a tool that helps the organization to identify strengths, weakness, opportunities and threats. The internal organization concerns the strengths and weakness of the organization and externally the environmental opportunities and threats are analyzed and defined.

The manager can based on the SWOT-analysis select the corporate, business, and functional strategies to put the organization in a better position and achieve the desired goals.

The first step for the manager is to identify the strengths and weaknesses from the current situation of the organization. Afterwards it is desired to take benefit from the strengths and correct the weakness that may affect the organization in the future.

The second step is defining the external factors and taking advantage of any opportunity that might occur and work on the threats.

The tool ensures the managers that they make the most of what the organization got and reduces the risk of failures by understanding and defining what the organization is lacking, which will result in a better position in that market.

Figure 1: Salience Model Representing the Importance of Different Stakeholders[1]

Tabel The table above shows what a SWOT Analysis matrix could look like.


Four Classical Functions of Management The use of this tool is to establish a overlook for the mangere, of where the problem of his/hers management is, and to help provide the understanding and information needed to any changes to help solve that problem. When working with this tool, there are four functions, first function is Planning, which is that the manager is choosing the right organizational goals to provide and achieve those goals, second function is Organizing, which is that the manager has the right setup for his works, and is best suited to their abilities. Third one is Leading, which the managers ability to motivate and coordinate their staff to achieve organizational goals. And the last one is Controlling, here there is looked at which system or ways the manager measure og monitor the work progress.


STAR-model The Star Model consists of five areas that should be connected and aligned to successfully shape the decisions and behaviors of your organization: Strategy, Structure, Processes, Rewards, and People.

Figure 1: Salience Model Representing the Importance of Different Stakeholders[1]

1. Strategy The strategy comes first in the model as it sets the direction of the organization. An organization's strategy of an organization is defined by the vision, mision and values as well as the goals.

2. Structure

3. Business, processes & lateral links 4. Rewards systems 5. Human resource management





References

  1. 1.0 1.1 Ronald K. Mitchell, Bradley R. Agle, Donna J. Wood. The Academy of Management Review, Vol. 22, No. 4, 1997, p872
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox