Defect Flow Improvement

--Sprint 2 Review
Members:  Sherry, Ice, Cherie, Charles, Jonny
Mentor:      Simon
Volunteer: Sunny

Previously on DFI

    1. Why we propose this topic?
    2. Analyze the root cause of current situation
    3. Define list of actions

Current Situation

  • Hard to define bug owner
  • Ping-Pong Defect
  • No Unified Live Defect reporting format & process
  • No shared understanding of Defect Priority between production & CR team
  • ....

Root Cause

  • No defined role to response the Live Defect
  • No D.O.D of bug fixing
  • Lack of standard rule to handle multi-team bugs
  • Lack of practice of defect analysis
  • ...

Outputs

  • Define unfied and clear template to report live defect
  • Defect flow diagram, Roles and Responsibility
  • Defcon system upgrade
  • Define and clarify the understanding of Defcon system
  • Calculate Defcon automatically in JIRA
  • Regular syc-up meeting between SMG and CRM

Outputs

  • Define unfied and clear template to report live defect


Roles & Clear Responsibility


2 Events

  • Send the new Live Defect report to Labs
    • Every Month
    • By Eric.Azumi

  • Catch-up meeting with CR

Regular meeting with CR TEam

Purpose:
    1. Better knowledge of the Release info and Product functionality
    2. Reduce the open days of live defects
When:
Friday 2pm ~ 3pm @ Code Freeze Week
Host:
Scrum Masters host in turns

Regular meeting with CR team

Agenda:
    1. PO Demo: invite PO in turns to do product demo/introduction
    2. Share release visible/potential impact with SM&CRM
    3. Live Defects Status follow-up/Escalation


Notice: After catch-up meeting, Scrum Master drives the concerned live defect progress.

Defcon system upgrade

  • Update the feature list in defcon system
  • Marked the owner of different feature, easy for CR to assign Live Defect to teams

Calculate defcon in jira

    • Basic of Calculation Format
      • Feature
      • Degree of functionality
      • Number of people affected

Defcon = (Feature + Degree + Affected ppl)/3

Calculate Defcon in JIRA

    • Merge Defcon with Priority in JIRA
      • 4.5 ~ 5    Blocker
      • 4 ~ 4.5    Critical
      • 3 ~ 4        Major
      • 2 ~ 3        Minor
      • 1 ~ 2        Trivial
    • Set Due Date based on Priority
 


Demo




Stay tuned for our next sprint...

To-Do

  • Live Defect flow Roles & Responsibility enhancement
  • Live Defect matrix design and data collection
  • EF Labs monthly Live Defect report
  • Defcon system deployment
  • Live defect flow Roles & Responsibility deployment
Made with Slides.com