Dev News 2011
From UG
(→Detailed example of monthly project plan to be created and maintained by BAs) |
(→Detailed example of BA monthly project plan) |
||
| Line 50: | Line 50: | ||
=== Detailed example of BA monthly project plan === | === Detailed example of BA monthly project plan === | ||
| - | * MUST | + | * MUST be created at the beginning of sprint and sent to me for review |
* Please use format below. | * Please use format below. | ||
Revision as of 16:28, 12 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.
Focus on Requirements not Design, direct BA to Dev interaction, Prototype if required
Highlights of new process:
- Focus on Requirements not Design
- direct BA to Dev interaction
- Prototype if required
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
