Dev News 2011

From UG

Revision as of 16:54, 11 April 2011 (edit) Alex (Talk | contribs) (→BA Management and updates) ← Older edit		Revision as of 18:15, 11 April 2011 (edit) (undo) Alex (Talk | contribs) (→Updated BA process) Newer edit →
Line 22:		Line 22:
	[[File:No SA process.jpg]]		[[File:No SA process.jpg]]
		+
		+	==== 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 ====		==== BA Management and updates ====

---

Revision as of 18:15, 11 April 2011

Contents 1 Intro 2 Jan 3 3 Jan 31 4 Apr 11 4.1 Updated BA process 4.1.1 Focus on Requirements not Design, direct BA to Dev interaction, Prototype if required 4.1.2 BA Management and updates

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.

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