[Reprint] Project risk management seven kinds of weapons of departure hook

Confirmed that there is no legal risk, little handsome but also learned that the boss has the latest instructions, demand changes are unavoidable. Almost all Baidu projects have experienced demand changes or potential demand risks. In order to deal with the most typical risk of this category, we have prepared a parting hook.

Keywords

"You use the parting hook, just to get together." ”

Interpretation

Managing Risk is simply to minimize the probability of a risk occurring, or to minimize the risk of loss.

Demand risk is the most typical risk, for the most typical risk, the use of the 80:20 principle, focus on follow-up, either to maximize the return on risk or to minimize the risk of loss. This is the purpose of our use of the parting hook.

Scenarios where there may be a demand risk

1. More new team members, not familiar with the development process

2. Project involves more people, cross-team cross-system (HTTPS project)

3. The project is in the exploratory phase, and the intermediate demand changes frequently with the market reaction

4. The project relies on more, the two sides interface, data format, progress and so on need to synchronize communication in time

Effective response plan and attention points

1. The value of the demand (user story) is difficult to assess

2. Complex product architectures and complex dependencies

3. Lack of business knowledge and long business processes lead to high learning costs

4. When the organizational structure is adjusted, the project objectives need to be re-aligned

5. After the launch of new products, with the enhancement of operational propaganda, the situation of too much new demand

6. Post-project discovery of missing requirements

7. Changes in post-project requirements

8. Project safety-related needs not being taken seriously

9. Situations where there are many sources of demand and coordination priorities are difficult

10. In the cross-team cooperation, the demand communication is not timely (demand submission time is late) situation

11. Too much demand and insufficient manpower

12. Situations where there are many sources of demand and possible conflicts between requirements

13. Inadequate operational knowledge and difficulty in presenting effective demand

14. Situations in which non-functional requirements are not taken seriously

15. The development team carries out multiple projects at the same time, encountering high-quality demand insertion situation

16. Different roles have different requirements for product user experience

17. Multi-terminal demand synchronization situation

Next go to a real project

1. Features are as follows:

• Product Development Stage : direction exploration

• Project Organizational Structure : cross-system

• end of product included : PC, SDK

• Project cycle : Long (years)
  

• Project category : Business, Platform category

• Development Model : Iteration

2. Background Description:

• Phase two, phase three focus on product functional requirements development and product stability improvement, the goal of the four phase is to achieve the quality requirements of commercial trial operation.

3. Risk Identification:

• identification phase: During the development of the commercial trial operation plan, several important needs of the customer's attention are not sorted out.

• Trigger conditions: These features are required for the use of products by paid customers who are officially commercial.

• probability of occurrence (high, Medium, low): high
  

• impact assessment (high, Medium, low): high

4. Response measures (avoidance, mitigation, transfer):

• Avoid

• Learn from competing products, learn from and reuse architectures in-house, set up special teams to develop quickly, and coordinate Rd engineering for architectural Review (compatibility and flexibility). At present, the guarantee architecture is designed to meet the important functions during the commercial trial run and can be launched flexibly and quickly.
  
  

Summary and refinement: When the demand carding, the analysis of business users is not in place, in order to avoid similar problems, need to strengthen user analysis and storymapping to solve.

The stone of his mountain, can attack Jade. Xiao Shuai hurriedly discussed the requirement change and PM.

Blog turn from: "Project risk management seven kinds of weapons of departure hook 丨 Baidu Agile Coach"

[Reprint] Project risk management seven kinds of weapons of departure hook