DQ and RFC process
From UG
(Difference between revisions)
(→RFC Phases) |
(→RFC Phases) |
||
| Line 25: | Line 25: | ||
== RFC Phases == | == RFC Phases == | ||
| - | === | + | === BC BA === |
* '''ph''': RFC BA | * '''ph''': RFC BA | ||
| Line 35: | Line 35: | ||
* Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report | * Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report | ||
| - | === | + | === BC ISA === |
* ph: RFC-ISA | * ph: RFC-ISA | ||
| Line 57: | Line 57: | ||
* set L0 emh/emhR | * set L0 emh/emhR | ||
| - | === | + | === BC PR === |
* ph: RFC-PR (Product Team Review) | * ph: RFC-PR (Product Team Review) | ||
| Line 70: | Line 70: | ||
* post notes as required | * post notes as required | ||
| - | === | + | === BC FSA === |
4) ph=RFC-FSA (Full System Analysis) // AG | 4) ph=RFC-FSA (Full System Analysis) // AG | ||
| Line 78: | Line 78: | ||
* create SOW | * create SOW | ||
| - | === DQ === | + | === BC DQ === |
5) ph = DQ (Dev/QA/SIT/UAT/T2S/Rel phases of RFCs and Non Urgent Bugs) // Perry | 5) ph = DQ (Dev/QA/SIT/UAT/T2S/Rel phases of RFCs and Non Urgent Bugs) // Perry | ||
Revision as of 14:58, 4 June 2012
Contents |
Info
This wiki is about RFC and DQ methodology.
Problems with old process:
- no specs/SA in many cases
- developers had no clear plans
- we had no idea what will be completed when (except urgent tasks)
Glossary
- L0 (L zero) = initial/rough;
- L1 = full
- RFC = Request For Change
- DQ = Development Queue
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
RFC Phases
BC BA
- ph: RFC BA
- purpose: (Change Request/Biz Analysis or Bug Report)
- owner: Denise
Details:
- create mantis for requested Change or Non Urgent Bug
- Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report
BC ISA
- ph: RFC-ISA
- purpose: (Initial Sys Analysis)
- owner: Alex
Details:
- 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
BC PR
- ph: RFC-PR (Product Team Review)
- owner: ???
Descr:
- 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
BC FSA
4) ph=RFC-FSA (Full System Analysis) // AG
- conduct L1 SA
- consult KU, SA, developers, BA as required
- create SOW
BC DQ
5) ph = DQ (Dev/QA/SIT/UAT/T2S/Rel phases of RFCs and Non Urgent Bugs) // 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
