Effective Risk Identification and Long-Term Monitoring Mechanisms in Project Management
This article expands on risk management by detailing practical methods for risk identification—such as silent brainstorming and risk breakdown structures—and presenting a combined "1‑2" approach, while also outlining sustainable risk monitoring mechanisms like daily briefs and a case‑library for agile teams.
The article continues the author’s original work "未雨绸缪话风险" and focuses on two of the five key risk‑management keywords: "identification" and "monitoring". It first reviews basic risk concepts and then introduces six common risk‑identification techniques, emphasizing the silent brainstorming method and the Risk Breakdown Structure (RBS).
Silent brainstorming (a silent version of traditional brainstorming) encourages each participant to write risk ideas on sticky notes within a timed round, then share and discuss them, reducing the influence of dominant personalities. The Risk Breakdown Structure provides a hierarchical view of potential risk sources, ensuring comprehensive coverage without duplication.
To overcome the limitations of single techniques, the article proposes a combined "1‑2" method that merges silent brainstorming with RBS, enabling teams to capture a broader set of risks efficiently.
Practical steps for applying the "1‑2" method during an iteration planning meeting are detailed: (1) silent brainstorming, (2) individual presentation of sticky notes, (3) clustering similar risks, and (4) discussing mitigation actions. Typical timing is 3 min, 5 min, 2 min, and 8 min respectively, allowing the whole process to finish in about 20 minutes.
A case study of an agile team using the "1‑2" method illustrates how risks are categorized into risk packages (e.g., resources, time, quality) and further broken down into risk items and points, with examples from a Japan‑Okinawa travel project.
The article then shifts to long‑term risk monitoring, recommending two mechanisms: a daily risk briefing that collects and distributes current risks to key stakeholders, and a risk‑case library that documents past risks, solutions, and lessons learned, stored in a collaborative tool such as Confluence.
Templates for daily briefings and example tables of risk registers are provided (images shown in the original article). The author also references his book "互联网项目管理实践精粹" for additional guidance.
Overall, the piece offers actionable guidance, templates, and visual examples to help project and R&D managers systematically identify and continuously monitor risks throughout a project’s lifecycle.
JD Retail Technology
Official platform of JD Retail Technology, delivering insightful R&D news and a deep look into the lives and work of technologists.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.