Dev News 2011

From UG

(Difference between revisions)
Jump to: navigation, search
(Support and IT for Summer 2011. Review of biz proc, policies, org chart, etc)
(Support and IT for Summer 2011. Review of biz proc, policies, org chart, etc)
Line 188: Line 188:
*** part a) tasks to be logged into txt doc or xls (required)
*** part a) tasks to be logged into txt doc or xls (required)
*** part b) notes about this week's support (optional)
*** part b) notes about this week's support (optional)
 +
 +
* IT education for Tracie and Denise: by mid summer must start!
== May 27 ==
== May 27 ==
=== Software Development for Summer 2011. Review of biz proc, policies, org chart, etc ===
=== Software Development for Summer 2011. Review of biz proc, policies, org chart, etc ===

Revision as of 21:06, 26 May 2011


Contents

Intro

At the moment this is a collection of 2011 messages from Dev Director to the team related to dev biz process, announcements, etc

Last year messages: Dev News

Jan 3

See 2011 January 3 update

Jan 31

See 2010 Jan 31: Impact of IT transformation

Apr 11

Updated BA process

See Figure below.

File:No SA process.jpg


BA Management and updates

I would like BAs to be as independent is possible (work with little supervision).

This means that after they receive BA Sprint Plan from CT2 Board (list of projects and tasks) they create more detailed plans for themselves and work independently only providing weekly status updates in the form of short written report and meeting (if required), once at the end of each week.

Example of BA monthly plan:

File:Example of BA monthly plan.JPG


Example of BA weekly report:

TBD

Apr 12

Detailed example of BA monthly project plan

  • MUST be created at the beginning of sprint and sent to me for review
  • Please use format below.


NOTE1: You can use additional tabs (one per project for example) if more convenient.

NOTE2: Original xls can be downloaded from here: http://ct.jaguarfreight.com/mantis/file_download.php?file_id=2180&type=bug

File:Pp ex.JPG

BA weekly report

  • goal is to provide status for critical and possibly other tasks (on schedule or if not why) and visibility to how time is spenT
  • send as email to me and also attach as a Word doc to mantis for current Sprint
  • example
WEEKLY REPORT (TRACIE) MON 11 -15
.
Per Task
--------
.
2901	[Acc April] (Acc Misc) Train with all operators in accounting to …	
  Completed
.
2902	[Support wikis v2] Create/update wikis for Currencies and…
  In progress. Probably will take less time.
.		
2894	[Rates DB] Implement phase1 for MOT Air 	
  On schedule. One more sub-task added to plan: "Meeting with Simon"
.
Additional Notes
----------------
Support took less than 20 hours allocated so freed up time was used against Rates DB project.

April 13

Guidelines for BA (highlights of new process)

BA phase:

  • Focus on Requirements not Design

DevEst:

  • Contact developer to discuss if task is large/high impact

Dev phase:

If task is large/high impact:

  • Prototype is required
  • Proj plan is required
  • regular BA to Dev interaction is required

Update Dev diagram

File:No SA process Apr 13.jpg

Apr 19

Org Chart with Support group

File:Orgchart2011april13.jpg

May 25

Review of roles and activities

Support ..... <role>

Support for CT2 components, each BA handles its own comp

BA/PM ..... <role>

BA phase: - requirements gathering - etc

Dev phase: - manage development - UAT - WU ...

Support Coord ..... <role>

Sales Engineering ..... <role>

Dev (TT) Management ..... <role>

-- Managing development team (Technical Team - developers/QA):

- allocation - code review - mentoring - release coordination - etc

Who: Kostya

Global Proj Management ..... <role>

- Overall PM for all teams: Product, Dev, Support - Sprint PM

General communication ..... <activity>

-This is communication (meetings, etc) not related to any specific project/task.

May 26

Support and IT for Summer 2011. Review of biz proc, policies, org chart, etc

Pure IT sub-tasks breakdown:

  • daily help desk routing:
    • all issues must come as an email:
      • itsupport@ for pure IT issues
        • option 1, if we are too busy) automatically forward to TSI email CC Sup Coordinator
        • option 2, if we are not too busy) manually forward to TSI email CC Sup Coordinator
      • ihelp@ for CT2 issues
        • manually forward to appropriate BA (based on CT2 module ownership:
          • Tira: Ops, Client
          • Denise: OpsTruck, TMS
          • Tracie: Acc, Rates
    • educate Jag users about response times, ask to escalate to itsupport@
    • agree with TSI about response times for regular users and VIPs
  • IT projects
    • large: now there are several assigned to Alex
    • small:
      • handled by: Tracie,
      • escalate/mentor: Tira
      • help out: Denise
  • purchasing (this BP to be reviewed by Simon)
    • two levels of approval: a) IT Approval and b) Simon
    • if not immediate(must buy today to solve critical problem) need and more then 100USD and Alex is not on vacation then (a)is Alex, else Tira
  • reports/updates:
    • Weekly Joint Meeting
    • Weekly IT Report:
      • part a) tasks to be logged into txt doc or xls (required)
      • part b) notes about this week's support (optional)
  • IT education for Tracie and Denise: by mid summer must start!

May 27

Software Development for Summer 2011. Review of biz proc, policies, org chart, etc

Personal tools