Key Duties and Responsibilities:

Requirements Elicitation & Stakeholder Management

• Lead requirements discovery using interviews, workshops, observation, document review, and process walk-throughs.
• Identify and engage the right stakeholders; manage competing priorities and drive timely decisions.
• Translate stakeholder input into structured requirements with clear scope boundaries, assumptions, constraints, and dependencies.

Requirements Documentation (Formal Artefacts)

• Produce, maintain, and manage:
• BRD (Business Requirements Document) and/or FRD (Functional Requirements Document)
• User Stories and acceptance criteria (where agile is used)
• Process maps (AS-IS / TO-BE), SIPOC/value stream (as needed)
• Business rules catalogue, data requirements, and reporting requirements
• Requirements Traceability Matrix (RTM) linking requirements → design/configuration → testing/UAT outcomes
• UAT support artefacts (test scenarios, scripts, expected results) aligned to requirements

Gap Analysis & Solution Alignment

• Evaluate software functionality against business requirements, document:
• Fit/standard functionality
• Configuration opportunities
• Customisation needs
• Workarounds/manual processes
• Risks, trade-offs, and impacts
• Facilitate solution options discussions and recommend pragmatic approaches based on cost, risk, time, and business value.
• Support vendor demos and proof-of-concept activities with structured scoring and findings.

Change Impact & Readiness Inputs

• Identify process, role, data, and control impacts arising from solution changes.
• Provide inputs to change management and communications (e.g., impacted teams, process changes, training needs).
• Support governance with executive-ready summaries and decision papers.

Quality, Governance, and Delivery Support

• Ensure requirements are clear, testable, unambiguous, and version controlled.
• Manage requirement change requests and scope control through governance.
• Support delivery teams (internal and vendor) by clarifying requirements and validating proposed designs/configuration.

Experience & Qualifications

 Minimum Experience

• 3-5 years as a Business Analyst (or equivalent), with demonstrable ownership of requirements on major projects
• Proven experience working with COTS/SaaS platforms and vendor-led implementations
• Experience with enterprise documentation standards and governance routines

Qualifications (Preferred)

• Degree in Business, Information Systems, Computer Science, or related field (or equivalent experience)
• Certifications beneficial: IIBA (ECBA/CCBA/CBAP), PMI-PBA, ITIL, Lean Six Sigma, Scrum/Agile BA

Tools & Methods (Preferred)

• Documentation: MS Word/Excel/PowerPoint; Visio/Lucidchart/Miro for process mapping
• Backlog/requirements tools: Jira/Confluence, Azure DevOps, or similar
• Techniques: MoSCoW prioritisation, use cases, user stories, RTM, BPMN, workshop facilitation, prototyping