1. What's up with the replay
review the situationThe term is derived from a term used in the game of Weiqi, which means that after a player has finished playing a game of Go, he or she has to re-set the board to see where he or she has played well and where he or she has played poorly. The good moves are inherited, and the bad moves are investigated in the process of rearranging the board to see how to make better moves.
Online issue reviewIn addition, by restoring the scene of the problem and the time line of the problem, we analyze the problems in design, development, testing, launching, operation and maintenance, fully expose the risks, find the root causes of the problems, and avoid the recurrence of the same kind of problems through effective improvement measures.
2. Purpose of the review
- Avoidance of recurrence of the same (similar) errors
- Provide a basis for the transfer of experience and the enhancement of competencies
- Turning Failure into Wealth and Success into Competence
3, when to review & who to review & how to prepare to review
When is the review?
- Typically within 3 days of an online outage (depending on the severity of the problem & the scope of the impact, this can be accomplished within 3-7 days, strike while the iron is hot considerations, usually within a week is recommended)
Which roles need to attend?
- PM, RD, QA, Project Manager (required)
- Counterpart Module Interfaces (may be PM/RD/QA, participation recommended)
- PM leader, RD leader, QA leader (optional participation depending on the severity & scope of impact of the issue)
- Specialized leaders (optional participation)
How do I prepare for a review?
The review sponsor needs to be completed:
- Project background sorting, what are the triggering scenarios, scope of impact and duration, problem troubleshooting point in time organization (what was done, who did it), what is the root cause of the problem (need to form a review document)
- Each role and stakeholder will be pulled into the group to arrange a time and place, and the review document will be sent to the group at least 1 day in advance for participants to review (a special reminder can be made if it is clear at the review meeting that a particular participant is required to make a statement).
4. What to do about the review process
4.1 Problems in retrospect
- Project Background
- time line
- direct root cause
- trigger condition
- Scope of impact
4.2 Analysis of causes
- Design & Realization
- offline test
- Online Deployment
- Problem discovery
- end of line(coll.) speak sarcastically
4.3 Improvement plans
-
Output improvement measures
- short-term
- mid-term
- long-term goal
-
Discussion on the feasibility of improvement measures
- Measures: implementable and evaluable
- Feasibility considerations:
| Not easy to implement | Easy to implement | |
| profitable |
Specialized improvements - medium- and long-term objectives |
Rapid processing - short-term objectives |
| small gain | It's a waste of time. |
Can be dealt with later - short-term objectives |
4.4 Follow-up on the ground
-
Follow-up mechanism
- Short-term services: real-time briefings (pinned, e-mailed)
- Long-term services: specialized weekly reports, etc.
-
Head & Time
- Head: Unique
- Time: deadlines and commitments
-
Effectiveness Tracking
- Technical improvements: setting milestones and reviewing achievements
- Process improvement: forming norms and actually running them