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 agile ceremonies: SI planning, PI planning (support as needed and relevant),  daily stand-up, retrospectives, show and tells

• Maintain data integrity in Confluence & Jira for Capabilities and Features created by the BA Service

• Facilitate prioritisation of Capabilities and Features and capture results in Jira

• Input into traceability decisions of features gained through solution and system demos

• Support UAT test case preparation, & provide test case sign off as required

• Defect triage support during SIT / UAT / ORT

Included deliverables

Deliverable [per PI] Media Quality Criteria
check Deliver SAFe Capabilities and Acceptance Criteria to support the Epic Lean Justification Business Outcomes and Lead Indicators Jira

A well-defined SAFe Capability includes:

  • Capability name (Summary field in Jira) is NOT described in the 'As a <user>…' user voice but should be a concise statement that describes the intent
  • Capability Description is in the format:  “FOR  -  WHO - THE - IS - THAT  - UNLIKE - OUR SOLUTION”  i.e. provides the context of what we want to achieve and why
  • Capability Benefit Hypothesis in the format “IF … THEN …”
  • A Capability has Acceptance Criteria
  • Capability should be broken down into relevant Features
check Analysis Approach Confluence

Create a plan for analysis activities in the Analysis Approach page in Confluence for any new Epic, Release or Increment, following the Analysis Approach template.

check Deliver SAFe Features and Acceptance Criteria Jira

A well-defined SAFe Feature includes:

  • Feature name (Summary field in Jira) is NOT described in the 'As a <user>…' user voice but should be a concise statement that describes intent.
  • Feature Description is in the format: FOR - WHO - THIS FEATURE – ACHIEVING
  • Feature Benefit Hypothesis in the format “IF… THEN…”
  • Feature must have a User Journey or Storyboard attached.
  • Feature is supported by non-functional requirements / non-functional Acceptance Criteria
  • Feature includes Acceptance Criteria
  • Each Feature Acceptance Criteria is independently testable with a pass or fail result
  • Each Feature Acceptance Criteria is written in clear, concise, and unambiguous language
  • Meets the agreed Definition of Ready available in the Analysis and Design Confluence page
check Solution Context / Overview Confluence

Create analysis, design thinking & customer experience inputs in to the solution context page in Confluence, including CX examples, recognition of discussions had and informed decisions

Additional deliverables

Add on Deliverables Media Quality Criteria
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
Bespoke Deliverables Media Quality Criteria
TypeAmount
Return to Individual Agile services Add to basket