Business Analyst

1. Role Summary The Business Analyst acts as the primary bridge between business stakeholders and the development team. The role is responsible for eliciting, documenting, and managing requirements across the full project lifecycle, validating delivered functionality against stakeholder intent, and ensuring complete traceability from business need through to tested, accepted software.

2. Key Responsibilities 2.1 Requirement Elicitation & Management

• Conduct requirement workshops and interviews with domain experts, end users, managers, and leadership to capture current-state workflows and define future-state needs.
• Document requirements as User Stories, Use Cases, and a Software Requirements Specification (SRS) aligned with IEEE 830 standards.
• Maintain a Requirements Traceability Matrix (RTM) linking each business requirement to design, development, and test artefacts.
• Manage requirement changes through a formal Change Request process, assessing timeline and cost impact with the Project Manager.

2.2 Process & Domain Analysis

• Map and document end-to-end business process flows, identifying pain points, automation opportunities, and data dependencies.
• Analyse data fields, status workflows, and business rules for each application module.
• Document integration touchpoints with external systems and define data exchange contracts.
• Identify and capture compliance, audit, and accreditation-related documentation needs.

2.3 UI/UX & Prototype Collaboration

• Collaborate with UI/UX designers to validate wireframes and prototypes against stakeholder expectations.
• Define role-based views and access levels for different user personas (leadership, managers, field engineers).
• Review notification triggers, access control levels, and multi-device (desktop, tablet, mobile) usability requirements.

2.4 Agile Sprint Planning & Delivery Support

• Participate in all Agile ceremonies: sprint planning, backlog grooming, sprint review, and retrospective.
• Write and refine User Stories with clear, testable acceptance criteria before each sprint begins.
• Support developers during the build phase by resolving requirement ambiguities and providing domain context.
• Conduct sprint demo walk-throughs with business leads and obtain formal sign-off.

2.5 Quality Assurance & UAT

• Define test scenarios and acceptance criteria for System Integration Testing (SIT) and User Acceptance Testing (UAT).
• Coordinate and support the UAT team; log defects and track resolution within agreed SLAs.
• Verify that generated outputs, reports, and document exports match approved templates and business rules.

2.6 Documentation & Governance

• Produce and maintain all BA artefacts: SRS, Use Case diagrams, Role Matrix, NFR document, RTM, Meeting Minutes, and Sprint Acceptance Records.
• Ensure timely document sign-off in accordance with project governance guidelines.
• Support RACI adherence, escalation communications, and stakeholder reporting as defined in the project charter.

3. Required Qualifications & Skills 3.1 Education

• Bachelor's degree in Engineering, Computer Science, Information Technology, or a related field.
• MBA or equivalent post-graduate qualification is an advantage.

3.2 Experience

• 3–6 years of Business Analysis experience on enterprise web application projects.
• Exposure to laboratory management, quality management, or compliance-driven environments is preferred.
• Prior experience working with government or regulated-industry clients is an advantage.

3.3 Technical Skills

• Proficiency in writing SRS documents, Use Cases, User Stories, and Acceptance Criteria.
• Ability to read and review data models, REST API contracts, and process flow diagrams.
• Familiarity with ERP integration concepts (read-only data fetch scenarios).
• Working knowledge of SDLC, Agile/Scrum methodology, and sprint-based delivery.
• Tools: MS Word, MS Excel, JIRA or equivalent issue tracker, Confluence or SharePoint, Visio or draw.io for process mapping.

3.4 Soft Skills

• Strong stakeholder management with ability to facilitate workshops for mixed technical and non-technical audiences.
• Excellent written and verbal communication skills.
• Analytical thinking and meticulous attention to detail in documentation and data field definitions.
• Proactive in identifying scope creep, risks, and dependency gaps; surfaces issues early.
• Ability to work independently and manage multiple workstreams in parallel.

4. Key Deliverables #

Deliverable Cadence 1 Requirement Workshop Minutes & Initial BA Charter Project kick-off 2 Software Requirements Specification (SRS) Early phase 3 Use Case Diagrams & Role / Access Matrix Early phase 4 Requirements Traceability Matrix (RTM) Living document 5 Approved User Stories with Acceptance Criteria Before each sprint 6 UI/UX Wireframe Sign-off Documentation Design phase 7 Sprint Demo Sign-off Records End of each sprint 8 UAT Test Scenarios & Defect Log Testing phase 9 BA Closure Report & Knowledge Transfer Pack Project closure

5. Success Metrics

• Zero unresolved requirement ambiguities at the start of each sprint.
• 100% RTM coverage — all requirements traced to test cases before UAT commences.
• Sprint sign-off obtained within the agreed timeframe after each sprint demo.
• UAT defects resolved and verified within SLA.
• No post-go-live critical defects attributable to missed or misunderstood requirements. T