Know ATS Score
CV/Résumé Score
  • Expertini Resume Scoring: Our Semantic Matching Algorithm evaluates your CV/Résumé before you apply for this job role: Business Analyst.
Kenya Jobs Expertini

Urgent! Business Analyst Position in Naivasha - NFT Consult

Business Analyst



Job description

Job Title: Business Analyst
Location: Nairobi, Kenya

Reports to: Country Manager

Role Overview

The Business Analyst (BA) will act as the critical link between business stakeholders, end-users, and technical teams.

The BA will be responsible for gathering, analysing, and documenting business requirements, converting them into functional and technical specifications, and supporting the delivery of software solutions that align with organizational goals and customer needs.

The BA will ensure that products are designed and delivered with clarity, efficiency, and business value in mind, serving as the voice of the business within the development lifecycle.

In summary, the BA’s role in the software development practice will not just be about documentation, but also about facilitation, collaboration, and ensuring business value alignment throughout the software development lifecycle.

Key Responsibilities

  • Work with stakeholders to elicit, document, and prioritize business and functional requirements.
  • Translate requirements into: User stories Use cases Process flows Acceptance criteria.

  • Conduct business process mapping and gap analysis to identify improvement opportunities.
  • Collaborate with product managers, architects, developers, and QA engineers to ensure requirements are understood and implemented correctly.
  • Maintain the Requirements Traceability Matrix (RTM) throughout the project lifecycle.
  • Support backlog grooming, sprint planning, and reviews in Agile environments through collaboration with the Scrum Master.
  • Assist in UAT planning, execution, and defect resolution with business stakeholders.
  • Validate solutions against requirements, ensuring business needs and quality standards are met.
  • Provide data-driven insights and reports to support decision-making.
  • Serve as a bridge between technical and non-technical teams, ensuring clarity in communication.
  • Development of requisite documentation and artefacts necessary for a successful product development.

    The exact documents are detailed below (Governance – Documentation)
  • Governance – Documentation

    As part of the governance process, the Business Analyst (BA) role will be responsible for producing a wide set of documents and artefacts that serve as the “bridge” between business needs and technical delivery.

    These artefacts will span requirements gathering, process modelling, solution design, testing alignment, and business validation.

    Together, they will ensure the software product aligns with both user needs and business strategy, while reducing the risk of miscommunication.

    They will also help align key stakeholders in the software development lifecycle, eg developers, testers, and product owners.

    Below are the documents and artefacts that the Business Analyst will be expected to develop in collaboration with other stakeholders relevant to the phase.

    1.

    Discovery & Requirements Elicitation Phase

  • Business Requirements Document (BRD): Captures high-level business goals, drivers, and scope.
  • Stakeholder Register / RACI Matrix: Identifies key stakeholders, roles, and responsibilities.
  • Interview Notes / Elicitation Log: Records findings from workshops, interviews, and surveys.
  • Current State Analysis (As-Is): Describes existing processes, systems, and pain points.
  • 2.

    Analysis & Documentation Phase

  • Functional Requirements Document (FRD): Breaks down business needs into functional capabilities.
  • Non-Functional Requirements (NFR) Specification: Performance, security, usability, scalability, compliance, etc.
  • Use Cases / User Stories / Acceptance Criteria: Detailed user interactions and expected outcomes.
  • Process Models / Business Process Model & Notation (BPMN): As-Is and To-Be workflows.
  • Data Models (Conceptual/Logical): High-level description of data entities and relationships.
  • Gap Analysis Document: Identifies gaps between current and desired state.
  • 3.

    Solution Design Support Phase

  • Requirements Traceability Matrix (RTM): Ensures all requirements are tracked from definition → design → testing.
  • System Context Diagrams: Shows how the system interacts with external actors and systems.
  • Wireframes / Prototypes / Mockups: Visual representation of features for validation with stakeholders.
  • Interface Specifications (APIs, integrations): Defines data exchange requirements.
  • 4.

    Development & Testing Support Phase

  • Change Request Documentation: Tracks modifications to scope and requirements.
  • Test Scenarios / Test Case Mapping: Ensures user stories and requirements are testable.
  • Defect Triage Reports: BA often supports prioritization of issues.
  • 5.

    Delivery & Transition Phase

  • User Manuals / Training Guides (co-created with Product Trainers): Helps end-users adopt the system.
  • Knowledge Transfer (KT) Document: Consolidates critical knowledge for support/operations teams.
  • Release Notes / Implementation Checklist: Captures what’s delivered, dependencies, and limitations.

  • 6.

    Governance & Continuous Improvement Phase

  • Lessons Learned Register: Captures successes and challenges for process improvement.
  • Post-Implementation Review (PIR): Evaluates solution effectiveness against business goals.
  • Benefits Realization Report: Confirms whether the project delivered measurable business value.
  • OKRs & KPIs

    Objectives (OKRs):

  • Ensure 100% clarity and alignment between business needs and technical implementation.
  • Reduce rework by improving requirement accuracy as captured in the Requirements Specification Document (RSD).
  • Support the timely delivery of high-quality software aligned with business objectives.
  • Facilitate continuous collaboration between stakeholders and developers.
  • Key Performance Indicators (KPIs):

  • % of requirements approved without major revisions.
  • % of UAT defects traced back to unclear/missing requirements.
  • Stakeholder satisfaction with the requirement gathering process.
  • Timeliness of requirement documentation vs.

    project deadlines.
  • Traceability coverage (business requirements linked to test cases and delivered features).
  •  

    Qualifications & Experience

  • Bachelor’s degree in Business, Information Systems, Computer Science, or related field.
  • 2–5 years of experience as a Business Analyst in software development, IT, or technology consulting.
  • Strong knowledge of SDLC and Agile methodologies (Scrum, Kanban).
  • Proficiency in requirement documentation tools (Confluence, Jira, Azure DevOps).
  • Experience with process modeling tools (Visio, Lucidchart, Bizagi).
  • Solid understanding of databases, APIs, and system integrations (ability to discuss with developers).
  • Strong problem-solving, critical thinking, and facilitation skills.
  • Excellent verbal and written communication skills.
  • Preferred Qualifications (Nice to Have)

  • Certifications: CBAP, CCBA, PMI-PBA, IIBA-AAC, or CSPO.
  • Experience with data analysis and visualization tools (Excel, Power BI, Tableau).
  • Exposure to cloud-based applications (AWS, Azure, GCP).
  • Experience in domain-specific industries (e.g., fintech, healthtech, govtech).

  • Competency Level Expectations

    Competency Area

     Beginner

    Intermediate

    Advanced

    Expert

    Time in Role

    Requirement Gathering 

     Assists workshops 

     Leads requirement workshops

     Structures enterprise-level requirements

     Defines org-wide BA standards

     0–2 years

    Documentation & Analysis

    Writes basic user stories

    Produces detailed

    BRDs/FSDs

    Optimizes process models

    Coaches teams on analysis best practices

    1–3 years

    Agile Delivery Support

    Participates in backlog refinement

    Manages backlog items with PM/PO

    Owns backlog for product stream

    Shapes Agile BA practices across org

    1–3 years

    Stakeholder Engagement 

    Attends meetings

    Facilitates discussions

    Manages conflicts

    & priorities

    Influences executive stakeholders

    1–3 years

    Technical Acumen

    Understands SDLC basics

    Works with devs/testers on feasibility

    Anticipates integration impacts

    Defines cross-platform requirement strategies

    2–4years

    Testing & Validation

    Supports UAT execution

    Designs UAT scripts & cases

    Owns UAT planning and sign-offs

    Defines quality validation frameworks

    1–3 years


    Required Skill Profession

    Business Operations Specialists



    Your Complete Job Search Toolkit

    ✨ Smart • Intelligent • Private • Secure

    Start Using Our Tools

    Join thousands of professionals who've advanced their careers with our platform

    Rate or Report This Job
    If you feel this job is inaccurate or spam kindly report to us using below form.
    Please Note: This is NOT a job application form.


      Unlock Your Business Analyst Potential: Insight & Career Growth Guide