SDLC and related for 2012

From UG

Revision as of 19:28, 6 February 2012 (edit) Alex (Talk | contribs) (→Mantis cleanup) ← Older edit		Revision as of 21:13, 6 February 2012 (edit) (undo) Alex (Talk | contribs) (→Misc) Newer edit →
Line 38:		Line 38:
	=== Status updates ===		=== Status updates ===
		+
		+	== Ver 2.0 ==
		+
		+	* add est fields for BAs and weekly schedule (alex)
		+	* Formal approval of SOWs
		+	* Change control for tasks in Dev
		+	* UAT by end users
		+	* Formal communication plan for executives (dashboard)
		+	* post mortem for Sprint with Dev team // post proj review
		+	* weekly status updates (all dev team together)

---

Revision as of 21:13, 6 February 2012

Contents 1 Info 2 Development Process 2.1 RFC 2.2 BA 3 Support Process 4 Project Management 4.1 Mantis cleanup 5 Misc 5.1 Communication hours 5.2 Mantis feedback 5.3 Status updates 6 Ver 2.0

Info

Development Process

RFC

ph = RFC

This phase is for ....

BA

??? I suggest to re-use .e, ..., 1,2,... for BAs. Add flag if required "type of hours"

BA phases: |RFC|Blog|BA|SA|ArcSR|MOSR|Est|

Dev phases:|Dlog|Dev|QA|UAT|WU|T2S|TG|CDR|Arc

Support Process

Project Management

Mantis cleanup

Review tasks from previous sprints that remain in open state and push BAs to resolve.

Sup tasks cleanup is managed by Sup Manager.

Misc

Communication hours

Mantis feedback

Status updates

Ver 2.0

• add est fields for BAs and weekly schedule (alex)
• Formal approval of SOWs
• Change control for tasks in Dev
• UAT by end users
• Formal communication plan for executives (dashboard)
• post mortem for Sprint with Dev team // post proj review
• weekly status updates (all dev team together)