ISEB BA

1

Organisation Type, Organisation State, SMART, CSF, KPI, SWAT, Pestle, Porter 5 forces, Legal and Regulatory, ToR, CORBA, Current Situation, Stakeholder Vision, BAM, Consensus BAM, Gap Analysis, Business Case, Requirements, Process Model, Class Diagram, Organisation Structure, Financial Management, Management Accounting, Budgeting, Investment Appraisal, Costing, Financial Reports, Financial Ratios

BUSINESS AGILITY AgileNorthwww.agilenorth.orgAgileNorth 2016

Thursday 30th June 2016Preston

2

agile or Agile: The small a in Team, the big A in ISEB BA

First amendment: Adding value over on time on budget

BA Plan.

Agile is as agile does

Managing your energyUse CasesMain flowAlternative FlowsException Flows

Lean -> AgileKeizenContinuous improvement

Self organising teams

TDDAutomated testCardsPair programmingChapter 19 If it is worth doing do it all the time – canvasesNow FIT andSpecification by Example

TeamCommunicationHow are we going to work together on this project?

VDD RDD

3

RequirementsEpics/UserStories SystemUseCase Requirements CatalogueId UCRef&Name ReqIDAsan[Actor] PrimaryActorIwant[Function) Goal RequirementDescriptionSothat[Rationale] Rationale RationaleAcceptanceCriteria PostConditions AcceptanceCriteria

System Use Cases are structured with:a) Flows (Main, Alternative and Exception) within System Use

Cases b) Steps in a flow to add detail of interaction and sequencingc) Includes and extends between System Use Cases

Epics/User Stories are structured hierarchically:a) Each System Use Case flow is equivalent to a sub User Storyb) Each included or extend System Use Case can is equivalent to

an Epic/User Storyc) Steps in a flow can be documented as:

i. Acceptance criteria specifying the need for step orderingii. A User Story specifying the need and rationale for step

ordering

1.The Lack of actor in Requirements Catalogues leads to requirements being presented primarily from the business perspective or from an unknown perspective

2.System Use Cases are written from the viewpoint of the user of the system. In branch an telephony this is an LBG colleague and NOT the customer. Business and Customer perspective are considered in secondary and tertiary actors.

3.Epics/User Stories allow Customer, Colleague and Business perspective to be given equal footing

4.System Use Cases include sequenced action steps: this can imply a solution. Epics/User Stories would only specify the order if needed.

5.The System Use Case Trigger: is equivalent to the Goal in most cases.6.Related Artefacts: These are detail to requirements that exist in all three approaches7.Epics/User Stories place more rigour/importance around the detail of acceptance

criteria using the ‘Given, When, Then’ format.

The Goal by Eli Goldratt & Jeff Cox

(1984)

The Phoenix Project by Kim, Behr & Spafford

(2013)

Managing the Design Factoryby Don G. Reinerston

(2013)

Foundations of Agile Thinking

Practicalities of Scrum

The Scrum GuideEssential Scrum Scrum & XP

from the Trenches

Agile BA

5

SPECIFICATION BY EXAMPLE

Automated Tests

Automated Tests

USE CASE 2.0ESSENCE

For internal use only 6

Risk

Scale