Microsoft Solution Architecture (Module 3) (2)

zhaozj2021-02-17  53

I. Step 2: Analyze the risk and prior priority

the goal:

l For risk list, you can make teams to allocate resources for the highest priority risk

Risk Analysis: The process of converting estimates or data on specific project risks into a team can be used to make priority decisions.

Risk Sort: Sort by the entire threat and solving priority of the organization according to risks

II. List of primary risk after a priority order

priority

condition

result

possibility

influences

Disclose

1

Developers use new development technology

Since developers need time to learn to extend the development time

30%

2

6

2

The development team was divided into two, one in London, a loose machine

Team member's communication is difficult

20%

2

4

III. Step 3: Planning to manage risk and schedules schedules

the goal:

l In order to create a detailed plan for top-level risk

l Synthesate these plans with standard project management processes to ensure they are complete

plan:

l The process of transitioning the prioritized risk list into action plan

Arrange a time:

l The process of going the risk management plan and the project time schedule

IV. Ways of risk behavior plans

Investigation: Get more information before taking action.

Accepted: If the risk is happening, can we bear the result?

Avoid: Can we avoid risks by changing the functional range of the project?

Change: Can we transfer risk to other projects, teams, organizations or individuals?

Reduce: Can the team reduce the possibility of risks or reduce risks?

Emergency Plan: Can it reduce the risk by reactions in the plan?

V. Reduce risk

Take action in advance

Prevent risk

Reduce the impact of risk or results to an acceptable level

Vi. Risk emergency

What should I do when the risk actually occurs?

Should decide in advance

Excitation of an emergency plan by exciting or deciding from a defined trigger

VII. Set the trigger

Trigger emergency plan using trigger

l Time trigger: If the milestone is postponed

l limit trigger: If the error reaches 75

l Event trigger: If the person is redistributed

Trigger based on risk type or impact type

The manager who will be affected will agree on the trigger and its value.

VIII. Risk Action Plan Documentation

condition

result

Reduce

Emergency

trigger

owner

Developers use new development tools

Since developers need to learn to lead to development time

Provide technical training for developers

Return to the previous version

Developers do not have related technical exams approved by the project plan

Mike

The development team is divided into two groups that have been separated.

Difficulty in the team

Weekly meetings through a conference between two places

Establish communication ports for publishing project information on the Internet

Lack of communication, causing the process delay

Big

IX. Step 4: Track and report risk status

the goal:

l Control the risk of risks in the risk activity plan

l Provides notice when the emergency plan trigger is reached

l Communication risk status and report the mitigation program

track:

l Risk undulation and trigger events control to ensure planned risk events

report:

l Provide a regular, detailed risk status report for project teams, providing top risk status reporting for project groups and other project supporters.

X. Step 5: Control Risk

the goal:

l Successfully perform the risk emergency plan

l Upgrade risk and risk analysis, priority, planning and timeline

risk control:

l Executive Risk Emergency Plan and Related Status Report Process

XW. Step 6: Learning from the risk

the goal:

l Provide quality assurance to the ongoing risk management activities

l Provide tutorials for improving future project risk management capabilities

l Improve risk management process

Learn:

l Document chemistry to the tutorial and get the risk management knowledge base in related projects to be reused in the future

1) Summary of modules

The risk management of the Microsoft Solutions framework is:

Comprehensive: Represents all elements in the project (people, processes, technology)

Continuous: Application in the entire life cycle of the project

Pre-prevention or reduction of risk

Flexible: Applying a wide range of risk analysis methods

Based on future: used for individuals and enterprise learning

转载请注明原文地址:https://www.9cbs.com/read-28673.html

New Post(0)