Dev News 2011
From UG
(Difference between revisions)
(→Apr 11) |
(→BA Management and updates) |
||
| Line 29: | Line 29: | ||
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. | 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 monthly plan:''' |
[[File:Example of BA monthly plan.JPG]] | [[File:Example of BA monthly plan.JPG]] | ||
| + | |||
| + | |||
| + | '''Example of BA weekly report:''' | ||
| + | |||
| + | TBD | ||
Revision as of 16:54, 11 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
