Please wait...

Business Analysis

The Business Analyst is accountable for gathering the detailed definition of business requirements to enable programme's delivery.

Please wait...

Basket
More information

Activities:

Participate in relevant agile ceremonies when required (SI planning, PI planning, scrum meetings, sprint retrospective); Maintain data integrity in Confluence & Jira for features & stories created by the BA Service; Input into traceability decisions of features gained through solution and system demos; Support UAT test case preparation & test case sign off Defect triage support SIT / UAT / ORT

Included deliverables

Deliverable [per PI] Media Quality Criteria
check Deliver draft stories for prioritised features as an input into PI planning Jira/Email

A draft user story meets at least 51% of the criteria for a well-defined user story

check Deliver user stories and acceptance criteria Jira/Email

A well-defined user story includes:

  • Story meets all the INVEST quality criteria
  • Story can be implemented by a single Release Train
  • User Story name (Summary field in Jira) is described using the format:  As a <user> I want to <do something> so I can <benefit somehow>
  • Enabler Story name (Summary field in Jira) is NOT described in the 'As a <user>…' user voice’
  • Story includes Acceptance Criteria
  • Story is supported by non-functional requirements / non-functional Acceptance Criteria
  • Story is linked to an upstream Feature using the Parent Link field in Jira
  • Each Story Acceptance Criteria is an independently testable with a pass or fail result
  • Each Story Acceptance Criteria is written in clear, concise, and unambiguous language

Additional deliverables

Add on Deliverables Media Quality Criteria
Deliver SAFe Features and Acceptance Criteria Jira/Email

A well-defined feature includes:

  • Feature name (Summary field in Jira) is NOT described in the 'As a <user>…' user voice
  • Feature includes Acceptance Criteria
  • Feature is supported by non-functional requirements / non-functional Acceptance Criteria
  • Feature Description is in the format: FOR – WHO – THE – IS – THAT – UNLIKE – OUR SOLUTION
  • Each Feature Acceptance Criteria is an independently testable with a pass or fail result
  • Each Feature Acceptance Criteria is written in clear, concise, and unambiguous language
Deliver user journeys for user stories with customer touch points Jira/Email

May include journey steps, enablers, considerations and scenarios

Bespoke Deliverables Media Quality Criteria
TypeAmount
Return to Individual Agile services Add to basket