Dev News 2011

From UG

Current revision as of 11:34, 25 February 2012

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

[edit] Jan 3

See 2011 January 3 update

[edit] Jan 31

See 2010 Jan 31: Impact of IT transformation

[edit] Apr 11

[edit] Updated BA process

See Figure below.

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

Example of BA weekly report:

TBD

[edit] Apr 12

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

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

[edit] April 13

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

[edit] Update Dev diagram

[edit] Apr 19

[edit] Org Chart with Support group

[edit] May 25

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

[edit] May 26

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

• daily (help desk):
  • 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

• 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!

[edit] Some changes to Mantis folders

[edit] May 27

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

[edit] Sep 06

[edit] Weekly report template

Adopted from Richard Kelly.

CT2 development and IT weekly report.

Highs
Lows
Issues & Matters Arising
Activity next period
Additional Info

[edit] Nov 29

[edit] Standard for wiki spec and related biz process

As promised this is a new format for specs.

First, please look at the example here: http://ct.jaguarfreight.com/wiki/Client_Report_Scheduler.

"Info" section now have required "scope" section.

"History" section is what we had before.

I defined two new types of sections:

• series of SOW (Statement Of Work) sections. Each of them defines what changes, new features, etc requested in each particular mantis. This is what developer needs to do to consider this mantis to be completed.
  • Do not delete SOW sections. Add new at the bottom with incremented id

• User Guide, that is a brief description of state of a component as it is in production. This gets updated at the WU phase.

About SOW:

• Do not post any SOW into mantis as we do before in many cases (even if it is a one line spec)
• Link to "SOW X" section in wiki should be posted into mantis notes saying "<Dev name>, this is your SOW: <wiki link>"

Please note that:

• it is assumed that each mantis is for defined wiki components that should also have parent (under CT2 Map). If not - please let me know I will create one.

• multiple CT2 components (and related wikis) can share one parent

Let me know if you have questions, etc. Let's go over it tomorrow on our meeting.

And please start using this! As well as when you have time please bring existing wikis to this standard.

[edit] Q and A

[edit] How will one know if wiki is up to date?

See section below:

=== User Guide Status ===
Up to date = No.

BAs should do the following:

• After spec is updated under WU set Up to date = Yes.
• Immediately after release go over all released tasks and for every one of them set Up to date = No.This will stay like that until you do WU.

[edit] Can User Guide section link to text defined in SOW?

We should avoid that when possible. But if it make sense then do it. (Example: 20 tab TMS report)

[edit] Wiki code

==Info==
===Parent Mantis===
===Scope of this wiki===
==Glossary==
==Core Business Need==
==Business Requirements==
==SOW 0==
==SOW 1==
==History==
==User Guide==
===User Guide Status and SOW covered===
== User Guide ==
=== Section 1 ===
=== Section 2 ===
===User Guide Status and SOW covered===
* Up to date? N
* SOW Covered: SOW X, ...