1. Module 3: Project Risk Management
1) Module profile
Manage the risk of the entire project
Take steps for effective risk management
2) Risk management in the process
I. Discussion: What does risks mean for you?
When you mention the risk, what do you think of?
Can you give an example of your work that you work and lead to a reverse results?
Can you mention some reasons to take risks? Quote a risk in a project and judge it by saying it.
Ii. Some definitions
risk:
l Loss or injury possibilities
l A expected problem or possibilities of reverse results, loss or damage in the future
Risk Management:
l Confirm the risks and manage events for these threat items.
III. Risk management in the Microsoft Solutions framework
Project Risk: The possibility of reverse results assumed in the project in order to pursue a chance
Risk Management Guidelines for Microsoft Solutions Framework
l The risk is distinguished from known issues.
l Define a risk management process for pre-identification, analysis, and risk of risk
l Increase the possibility of success by minimizing failure potential
IV. Applying for the basic principles of the Microsoft Solutions Framework
Keep keen, expect changes
l Hug changes and turn it into opportunities
l Continue assessment and pre-managing risks
Cultivate open communication environments
l Encourage uncroving culture
l Public discussion of risk in order to make a decision
Clear task, share responsibility
l Let the program manager responsible for risk management activities
l Let all team members participate in sharing responsibilities during risk management.
l Let team members share risks for allocation risks and activities
Learn from experience
l Use learning to get sustained improvements and greater success.
V. Key Concept of Risk Management Guidelines in Microsoft Solutions Framework
Assume that the risk is with the fear of any project or process.
Despect the determination of the risk as normal activity
First specify risks, then manage them
Continuous assessment risk
Use pre-risk management
Don't justify the number of risks to judge the value of the project
Vi. Awareness advantage from pre-risk management
Looking forward to the problem rather than responding to the problem
l Plans for preparing problems before the problem
l is as possible to prevent measures
Indicates a root cause rather than just symptoms
To solve the problem of structured, repeatable processes
VII. Features of Risk Management Guidelines in Microsoft Solutions Framework
Comprehensive: Represents all items elements (people, processes, technology)
Trained: Merge system, renewable process
Flexible: Applying a wide range of risk analysis methods
3) Take steps to conduct effective risk management
I. Risk management process for Microsoft Solutions Framework
Identification -> Analyze and Row Superior -> Plan and Arrange Schedule -> Track and Report -> Control -> Learning
Ii. Step 1: Identify the risk
the goal:
l Identify project risk
l Use the clear and clear way to make full understanding, reach a consistent list.
Risk recognition: Form a project risk plane by providing data from the team to the risk management process
l Risk classification: a structuring method of risk identification, it can provide ready-made liquid insurance orders for project areas for reference
l Risk Description: Use natural language representation to describe conditions that may result in losses and if the risk is determined.
Iii. Sources of derived risk from risk types
People: customers, users, sponsorship, individual, organization, skills, strategy
Process: tasks and objectives, decision making, project features, budget, fees, time schedules, demand, design, create, test
Technology: Safety, development, and test environment, tools, development, support, operational environments, availability: law, regulations, competition, economic conditions, technology, business
IV. Expression risk
Root Cause -> Conditions -> Results -> Total Loss or Opportunity Cost
V. Generate initial risk list
category
root cause
condition
result
Sequelae
technology
Technical change
Developers use new development technology
Since developers need to learn to extend the development time
We postpone the market share of entering the market and competed
people
organization
The development team is divided into two blocks in London and Luoshan.
Difficulties in communication between team members
Since additional rewriting leads to postponement
