DQ and RFC process

From UG

Revision as of 14:45, 7 June 2012 (edit) Alex (Talk | contribs) (→Top level Jag Soft Dev Workflows) ← Older edit		Current revision as of 20:30, 27 June 2012 (edit) (undo) Alex (Talk | contribs) (→DQ)
(22 intermediate revisions not shown)
Line 18:		Line 18:
	* DQ = Development Queue		* DQ = Development Queue
-	== Top level Jag Soft Dev Workflows ==	+	== Top level Jag Soft Dev Workflow classes ==
	We have the following top level workflows		We have the following top level workflows
Line 24:		Line 24:
	* Projects (Prj). Examples: GM Split, POEM, DR/KPI, I-Portal		* Projects (Prj). Examples: GM Split, POEM, DR/KPI, I-Portal
	* Urgent Bugs (UB)		* Urgent Bugs (UB)
		+	* Urgent Change (UC)
	* Development Queue (DQ) - any work that is subject to CT2 Release and is not covered by '''Prj''' or '''UB'''		* Development Queue (DQ) - any work that is subject to CT2 Release and is not covered by '''Prj''' or '''UB'''
	* Support (Sup). Examples: create new user, re-start server, etc.		* Support (Sup). Examples: create new user, re-start server, etc.
Line 30:		Line 31:
	"wf" mantis field is used to associate task with specific workflow class.		"wf" mantis field is used to associate task with specific workflow class.
-	== IS ==	+	* Prj
		+	* UB
		+	* UC
		+	* DQ1 - Invention/Analysis phases of DQ (BA/SA/etc)
		+	* DQ2 - Implementation phases of DQ (Dev/QA/SIT/etc)
		+	* Sup
		+	* Misc
-	Prj, UB, DQ have different initial phases but common end - IS (Implementation Sequence):	+	== IP ==
		+
		+	Prj, UB, DQ have different initial phases but common end: IP (Implementation Phase).
		+
		+	It consists of the following sub-phases:
	* Dev		* Dev
Line 38:		Line 49:
	* SIT		* SIT
	* UAT		* UAT
-	* T2S	+	* Stg (Staging)
-	* Rel	+	* Rel (Release)
-		+
-	== UB Phases ==	+
		+	== UB ==
		+	Phases:
	* BR - bug report		* BR - bug report
-	* [[#IS]]	+	* [[#IP]]
		+
		+	== UC ==
		+	Phases:
		+
		+	* BA
		+	* SA
		+	* Est
		+	* [[#IP]]
	== Proj ==		== Proj ==
		+	Phases:
	* BA		* BA
	* SA		* SA
	* Est		* Est
-	* [[#IS]]	+	* [[#IP]]
	== DQ ==		== DQ ==
		+
		+	Phases:
	DQ1:		DQ1:
Line 61:		Line 83:
	* PTR		* PTR
	* FSA		* FSA
		+	* Est
	DQ2		DQ2
-	* [[#IS]]	+	* [[#IP]]
	== Details of DQ workflow ==		== Details of DQ workflow ==
-	For convenience it is broken into 2 sub phases: DQ1 and DQ2.	+	For convenience it is broken into 2 sub-workflows: DQ1 and DQ2.
-	===  DQ1 RFC ===	+	DQ1:
		+	* covers BA, SA and related
		+	* '''wf mantis field''' = DQ1
-	* purpose: create mantis	+	DQ2:
-	* owner: Alex	+	* covers Implementation (Dev/QA/SIT/etc)
		+	* '''wf mantis field''' = DQ2
		+
		+	=== DQ1 details ===
		+
		+	====  RFC ====
		+
		+	* '''purpose''': create mantis
		+	* '''owner''': Denise
		+	* '''ph mantis field''': RFC
	Details:		Details:
	* create mantis record with initial available info for Change Request or Non Urgent Bug		* create mantis record with initial available info for Change Request or Non Urgent Bug
-	=== DQ1 IBA ===	+	==== IBA ====
-	* '''purpose:''' (Biz Analysis or Bug Report)	+	* '''purpose:''' (Initial Biziness Analysis or Bug Report)
	* '''owner''': Denise		* '''owner''': Denise
		+	* '''ph mantis field''': IBA
	Details:		Details:
-	* Conduct and post into mantis L0 BA (requirements) or Detailed Bug Report	+	* Conduct and post into mantis preliminary Business Analysis/Requirements (for changes) or Detailed Bug Report (for bugs)
		+	* design/solution ideas could be added as well if needed/available
-	=== DQ1 ISA ===	+	==== ISA ====
	* '''purpose:''' (Initial Sys Analysis)		* '''purpose:''' (Initial Sys Analysis)
-	* owner: Alex	+	* '''owner''': Alex
		+	* '''ph mantis field''': ISA
	Details:		Details:
Line 106:		Line 143:
	* set L0 emh/emhR		* set L0 emh/emhR
-	=== DQ1 PTR ===	+	==== PTR ====
-	*   (Product Team Review)	+	* '''purpose''':  (Product Team Review)
-	* owner: ???	+	* '''owner''': Denise or Alex?
		+	* '''ph mantis field''': PTR
-	Descr:	+	Details:
	* review periodically tasks that completed RFC-SA (say 5 a week)		* review periodically tasks that completed RFC-SA (say 5 a week)
Line 119:		Line 157:
	* post notes as required		* post notes as required
-	=== DQ1 FSA ===	+	=== FSA ===
-	4)  (Full System Analysis) // AG	+	* '''purpose''': Full System Analysis
		+	* '''owner''': AG
		+	* '''ph mantis field:''' FSA
		+
		+	Details:
	* conduct L1 SA		* conduct L1 SA
Line 127:		Line 169:
	* create SOW		* create SOW
-	===  DQ2 Dev, QA, SIT, UAT, T2S, Rel ===	+	=== Est ===
		+
		+
		+	* '''purpose''': Exact estimation
		+	* '''owner''': Developer/ Dev Manager
		+	* '''ph mantis field:''' Est
		+
		+	Details:
		+
		+	* conduct L1 estimation (replace L0 with L1)
		+
		+	===  DQ2  details ===
		+
		+	* '''purpose''': Implementation
		+	* '''owner''': Perry
		+	* '''ph mantis field''': Dev/QA/SIT/UAT/T2S/Rel
		+
		+	Details:
-	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
-	* conduct weekly DQ meetings to: a) review previous week's progress b) create plans for next week
	* review previous week's progress (post mortem):		* review previous week's progress (post mortem):
	** sort by due=wYY		** sort by due=wYY
	** go task by task and see status/ph it is in (most must pass QA and be in SIT/UAT)		** 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)	+	** send weekly review (post mortem) to all managers (Marc, KU, Ale, Den). Highlight in RED overdue tasks/developers that have overdue tasks.
	* create plans for next week:		* create plans for next week:
-	** identify how many mh available from each dev next week	+	** identify how many m/h available from each dev next week (Normally, each dev would contribute 8 hours a week to DQ2. 4 hours if super busy with the Proj )
	** sort tasks in DQ by T and create plan for each dev:		** sort tasks in DQ by T and create plan for each dev:
	*** assign mantis to dev		*** assign mantis to dev
Line 144:		Line 204:
	** send weekly plan to all managers (Marc, KU, Ale, Den)		** send weekly plan to all managers (Marc, KU, Ale, Den)
-	* coordinate SIT/UAT and Releases of DQ	+	* coordinate SIT/UAT and Release phases of DQ2

---

Current revision as of 20:30, 27 June 2012

Contents 1 Info 2 Glossary 3 Top level Jag Soft Dev Workflow classes 4 IP 5 UB 6 UC 7 Proj 8 DQ 9 Details of DQ workflow 9.1 DQ1 details 9.1.1 RFC 9.1.2 IBA 9.1.3 ISA 9.1.4 PTR 9.2 FSA 9.3 Est 9.4 DQ2 details

[edit] 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)

[edit] Glossary

• L0 (L zero) = initial/rough;
• L1 = full
• RFC = Request For Change
• DQ = Development Queue

[edit] Top level Jag Soft Dev Workflow classes

We have the following top level workflows

• Projects (Prj). Examples: GM Split, POEM, DR/KPI, I-Portal
• Urgent Bugs (UB)
• Urgent Change (UC)
• Development Queue (DQ) - any work that is subject to CT2 Release and is not covered by Prj or UB
• Support (Sup). Examples: create new user, re-start server, etc.
• Misc (Misc)

"wf" mantis field is used to associate task with specific workflow class.

• Prj
• UB
• UC
• DQ1 - Invention/Analysis phases of DQ (BA/SA/etc)
• DQ2 - Implementation phases of DQ (Dev/QA/SIT/etc)
• Sup
• Misc

[edit] IP

Prj, UB, DQ have different initial phases but common end: IP (Implementation Phase).

It consists of the following sub-phases:

• Dev
• QA
• SIT
• UAT
• Stg (Staging)
• Rel (Release)

[edit] UB

Phases:

• BR - bug report
• #IP

[edit] UC

Phases:

• BA
• SA
• Est
• #IP

[edit] Proj

Phases:

• BA
• SA
• Est
• #IP

[edit] DQ

Phases:

DQ1:

• RFC
• IBA
• ISA
• PTR
• FSA
• Est

DQ2

• #IP

[edit] Details of DQ workflow

For convenience it is broken into 2 sub-workflows: DQ1 and DQ2.

DQ1:

• covers BA, SA and related
• wf mantis field = DQ1

DQ2:

• covers Implementation (Dev/QA/SIT/etc)
• wf mantis field = DQ2

[edit] DQ1 details

[edit] RFC

• purpose: create mantis
• owner: Denise
• ph mantis field: RFC

Details:

• create mantis record with initial available info for Change Request or Non Urgent Bug

[edit] IBA

• purpose: (Initial Biziness Analysis or Bug Report)
• owner: Denise
• ph mantis field: IBA

Details:

• Conduct and post into mantis preliminary Business Analysis/Requirements (for changes) or Detailed Bug Report (for bugs)
• design/solution ideas could be added as well if needed/available

[edit] ISA

• purpose: (Initial Sys Analysis)
• owner: Alex
• ph mantis field: ISA

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

[edit] PTR

• purpose: (Product Team Review)
• owner: Denise or Alex?
• ph mantis field: PTR

Details:

• 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

[edit] FSA

• purpose: Full System Analysis
• owner: AG
• ph mantis field: FSA

Details:

• conduct L1 SA
• consult KU, SA, developers, BA as required
• create SOW

[edit] Est

• purpose: Exact estimation
• owner: Developer/ Dev Manager
• ph mantis field: Est

Details:

• conduct L1 estimation (replace L0 with L1)

[edit] DQ2 details

• purpose: Implementation
• owner: Perry
• ph mantis field: Dev/QA/SIT/UAT/T2S/Rel

Details:

• 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). Highlight in RED overdue tasks/developers that have overdue tasks.

• create plans for next week:
  • identify how many m/h available from each dev next week (Normally, each dev would contribute 8 hours a week to DQ2. 4 hours if super busy with the Proj )
  • 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 Release phases of DQ2