Business Analyst

The Business Analyst (BA) owns the end-to-end analytical lifecycle of a project. They bridge the gap between business stakeholders and technical IT teams by discovering business needs, defining strategic value, translating requirements into technical specifications, and validating that the final solution delivers the intended business value.

End-to-End Scope of Responsibilities

Phase 1: Discovery & Business Case (Pre-Project)

• Problem Definition: Partner with business sponsors to investigate operational challenges and define the root problem before jumping to a solution.
• Feasibility & ROI: Assist in evaluating software vendors, conducting cost-benefit analyses, and building business cases to justify project investments.

Phase 2: Requirements, Process Architecture, & Design

• Elicitation: Lead interactive workshops, interviews, and shadow sessions with stakeholders to extract hidden functional and non-functional requirements.
• Process Mapping: Document current state ("As-Is") and design optimized future state ("To-Be") workflows using standard notation (e.g., BPMN, Swimlane diagrams).
• Technical Documentation: Translate business needs into detailed technical artifacts, including User Stories, Acceptance Criteria (BRDs/FRDs), Use Cases, and Data Flow Diagrams.

Phase 3: Build Management & Agile Execution

• Backlog Grooming: Work alongside the Product Owner to prioritize, refine, and estimate the product backlog (using frameworks like MoSCoW or RICE).
• Technical Triaging: Act as the primary point of contact for developers and architects during sprints to clarify requirements and resolve roadblocks.
• Scope Control: Monitor requests for new features to prevent scope creep and ensure the team stays focused on the core project MVP (Minimum Viable Product).

Phase 4: Testing, Go-Live, & Value Realization (Post-Project)

• UAT Management: Define User Acceptance Testing (UAT) scenarios, write test scripts, and coordinate with business users to execute testing and sign off on quality.
• Change Management Bridge: Partner with Change Analysts to ensure training materials match the updated system logic.
• Value Realization: Conduct post-implementation reviews 3 to 6 months post-launch to track system adoption, analyze usage data, and verify if the project achieved its original business goals.

• Experience: 3-5+ years as a Business Analyst, Systems Analyst, or Consultant spanning the entire project lifecycle.
• Project Type: Proven experience in end-to-end software implementations, custom application development, or digital transformations.
• Tools: Proficiency in Jira, Confluence, Miro/Visio, and basic data query tools (e.g., SQL or Excel) for data validation.
• Competencies: Strong negotiation and stakeholder management skills, sharp analytical thinking, and the ability to explain complex technical logic to non-technical users.