Dev News 2011
From UG
(→Guidelines for BA (highlights of new process)) |
|||
| Line 23: | Line 23: | ||
[[File:No SA process.jpg]] | [[File:No SA process.jpg]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
==== BA Management and updates ==== | ==== BA Management and updates ==== | ||
| Line 93: | Line 77: | ||
---------------- | ---------------- | ||
Support took less than 20 hours allocated so freed up time was used against Rates DB project. | 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 === | ||
Revision as of 15:07, 13 April 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
Jan 31
See 2010 Jan 31: Impact of IT transformation
Apr 11
Updated BA process
See Figure below.
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
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
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
- for now just email
- 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
