DQ and RFC process
From UG
(Difference between revisions)
(→DQ: definition, process, etc) |
|||
Line 1: | Line 1: | ||
[[Category:DQ]] | [[Category:DQ]] | ||
- | + | == Urgent Bugs == | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
*U-bugs are managed by Sup Man, must be posted into mantis, estimated and fixed ASAP. Decide if they require Emerg Release. | *U-bugs are managed by Sup Man, must be posted into mantis, estimated and fixed ASAP. Decide if they require Emerg Release. | ||
*Non Urgent Bugs are managed through RFC | *Non Urgent Bugs are managed through RFC | ||
- | === RFC: | + | == Glossary == |
+ | |||
+ | * L0 (L zero) = initial/rough; | ||
+ | * L1 = full | ||
+ | * RFC = Request For Change | ||
+ | * DQ = Development Queue | ||
+ | |||
+ | == RFC == | ||
+ | |||
+ | 1) ph=RFC (Change Request/Biz Analysis or Bug Report) // Denise | ||
+ | |||
+ | * create mantis for requested Change or Non Urgent Bug | ||
+ | * Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report | ||
+ | |||
+ | 2) ph=RFC-ISA (Initial Sys Analysis) // Alex | ||
+ | |||
+ | * review periodically RFC records (say 5 a week) | ||
+ | * meet to discuss: Alex, AG, Sasha, Denise, etc (all together or in sub groups) (group might depend on the task) | ||
+ | * split / combine as required | ||
+ | * tweak summary/desc as required | ||
+ | * Mantis Description field should have 3 sections: | ||
+ | ** Problem/Request | ||
+ | ** Solution | ||
+ | ** SOW link | ||
+ | * identify what is large enough to be classified as a project and tag as such | ||
+ | * discuss solution | ||
+ | * conduct and post into Mantis L0 SA | ||
+ | * set Dv (to "any" if possible or to specific dev) | ||
+ | * set L0 emh/emhR | ||
+ | |||
+ | 3) ph=RFC-PR (Product Team Review) // ? | ||
- | * RFC ( | + | * review periodically tasks that completed RFC-SA (say 5 a week) |
- | + | * meet to discuss requirements/solution/emh (Marc, Denise, Alex, Perry?) | |
- | * | + | * reject/approve (by Marc) |
- | + | * set T | |
- | + | * post notes as required | |
- | * | + | |
- | + | ||
- | + | ||
- | * | + | |
- | * | + | |
- | + | ||
- | + | ||
- | + | ||
- | = | + | 4) ph=RFC-FSA (Full System Analysis) // AG |
- | + | * conduct L1 SA | |
+ | * consult KU, SA, developers, BA as required | ||
+ | * create SOW | ||
- | + | == DQ == | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | = | + | 5) ph = DQ (Dev Queue Management) // Perry |
- | + | * conduct weekly DQ meetings to: a) review previous week's progress b) create plans for next week | |
+ | * review previous week's progress (post mortem): | ||
+ | ** sort by due=wYY | ||
+ | ** go task by task and see status/ph it is in (most must pass QA and be in SIT/UAT) | ||
+ | ** send weekly review (post mortem) to all managers (Marc, KU, Ale, Den) | ||
- | + | * create plans for next week: | |
+ | ** identify how many mh available from each dev next week | ||
+ | ** sort tasks in DQ by T and create plan for each dev: | ||
+ | *** assign mantis to dev | ||
+ | *** set due mantis field to wXX where XX is week number | ||
+ | ** send weekly plan to all managers (Marc, KU, Ale, Den) | ||
- | + | * coordinate SIT/UAT and Releases of DQ |
Revision as of 21:27, 3 June 2012
Contents |
Urgent Bugs
- U-bugs are managed by Sup Man, must be posted into mantis, estimated and fixed ASAP. Decide if they require Emerg Release.
- Non Urgent Bugs are managed through RFC
Glossary
- L0 (L zero) = initial/rough;
- L1 = full
- RFC = Request For Change
- DQ = Development Queue
RFC
1) ph=RFC (Change Request/Biz Analysis or Bug Report) // Denise
- create mantis for requested Change or Non Urgent Bug
- Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report
2) ph=RFC-ISA (Initial Sys Analysis) // Alex
- review periodically RFC records (say 5 a week)
- meet to discuss: Alex, AG, Sasha, Denise, etc (all together or in sub groups) (group might depend on the task)
- split / combine as required
- tweak summary/desc as required
- Mantis Description field should have 3 sections:
- Problem/Request
- Solution
- SOW link
- identify what is large enough to be classified as a project and tag as such
- discuss solution
- conduct and post into Mantis L0 SA
- set Dv (to "any" if possible or to specific dev)
- set L0 emh/emhR
3) ph=RFC-PR (Product Team Review) // ?
- review periodically tasks that completed RFC-SA (say 5 a week)
- meet to discuss requirements/solution/emh (Marc, Denise, Alex, Perry?)
- reject/approve (by Marc)
- set T
- post notes as required
4) ph=RFC-FSA (Full System Analysis) // AG
- conduct L1 SA
- consult KU, SA, developers, BA as required
- create SOW
DQ
5) ph = DQ (Dev Queue Management) // Perry
- conduct weekly DQ meetings to: a) review previous week's progress b) create plans for next week
- review previous week's progress (post mortem):
- sort by due=wYY
- go task by task and see status/ph it is in (most must pass QA and be in SIT/UAT)
- send weekly review (post mortem) to all managers (Marc, KU, Ale, Den)
- create plans for next week:
- identify how many mh available from each dev next week
- sort tasks in DQ by T and create plan for each dev:
- assign mantis to dev
- set due mantis field to wXX where XX is week number
- send weekly plan to all managers (Marc, KU, Ale, Den)
- coordinate SIT/UAT and Releases of DQ