SDLC and related for 2012

From UG

(Difference between revisions)
Jump to: navigation, search
(Dev Team)
(Product Team)
Line 9: Line 9:
* Project Sponsor (Simon)
* Project Sponsor (Simon)
* Product Manager/Lead Module Owner (Marc)
* Product Manager/Lead Module Owner (Marc)
 +
:: - reports to Project Sponsor
* Module Owners (Simon, Marc, Karen, CK, ...)
* Module Owners (Simon, Marc, Karen, CK, ...)
-
* CT2 Board (Simon, Marc, Karen, Alex, Perry)
+
:: - report to Project Sponsor
 +
* CT2 Board (Simon - Chairman, Marc, Karen, Alex, Perry)
=== Dev Team ===
=== Dev Team ===

Revision as of 18:56, 8 February 2012


Contents

Info

Teams and roles

Product Team

  • Project Sponsor (Simon)
  • Product Manager/Lead Module Owner (Marc)
- reports to Project Sponsor
  • Module Owners (Simon, Marc, Karen, CK, ...)
- report to Project Sponsor
  • CT2 Board (Simon - Chairman, Marc, Karen, Alex, Perry)

Dev Team

  • Director of Development (Alex)
  • Project Manager (Perry)
- managing timeline and resources
- managing all backlogs (projects, BA, Dev)
- project planning
- status updates
- escalations, conflict resolutions
- liaison between Dev and Product teams
- liaison between Dev and Support teams
  • Solutions Architect (Alex)
  • Development Manager (Kostya)
  • Business/Systems Analysts (Tira, Alex, Perry)
  • Developers (Kostya, Sasha, AK, Misha)
  • QA (Roma)

Support Team

  • Support Manager (Denise)
  • Systems Administrator (Vlad)
  • Support Engineers (Tracie, AG)

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)
Personal tools