Business Analyst

Key Responsibilities: 1. Requirement Gathering & Analysis: - Conduct detailed discussions with clients, users, department heads, and project stakeholders to understand business requirements. - Analyse existing manual, spreadsheet-based, ERP-based, or software-driven business processes. - Identify business problems, process gaps, automation opportunities, and improvement areas. - Convert business requirements into clear, structured, and technically understandable software requirements. - Identify functional, non-functional, integration, reporting, security, and workflow requirements. - Ensure all requirements are properly validated before development begins. 2. Scope Definition & Requirement Management: - Define project scope, modules, features, workflows, user roles, masters, forms, dashboards, reports, and integrations. - Clearly identify in-scope, out-of-scope, assumptions, dependencies, and constraints. - Maintain requirement traceability throughout the project lifecycle. - Identify additional client requirements and determine whether they fall under the approved scope or require a Change Request. - Help prevent uncontrolled scope expansion and unnecessary project rework. 3. Functional Documentation: - The candidate should have experience preparing: Business Requirement Document (BRD), Software Requirement Specification (SRS), Functional Requirement Specification / Functional Specification Document (FRS/FSD), User Stories, Use Cases, Acceptance Criteria, Requirement Traceability Matrix (RTM), Process Flow Diagrams, Workflow Diagrams, Role and Permission Matrix, Screen and Field Specifications, Master Data Requirements, Integration Requirements, Report and Dashboard Specifications, UAT Documents, Change Request Documents, Requirement Clarification Logs, and Meeting Minutes / MOM. - Documentation must be detailed enough for developers and testers to execute requirements without unnecessary assumptions. 4. Process Mapping & Solution Design: - Study the client's existing business process and recommend an improved software-driven workflow. - Define approval hierarchies, escalation mechanisms, exception handling, notifications, alerts, and role-based access. - Work with solution architects and technical teams to ensure proposed functionality is technically feasible. - Participate in functional solution design and application architecture discussions. - Identify opportunities for process automation, digitisation, integration, and data optimisation. 5. Wireframe & Prototype Coordination: - Prepare or coordinate preparation of wireframes, prototypes, screen flows, forms, dashboards, and navigation structures. - Define fields, validations, dropdowns, masters, buttons, actions, statuses, and business rules for individual screens. - Conduct prototype walkthroughs with clients and obtain formal confirmation before development. - Ensure UI/UX designs are aligned with approved functional requirements. 6. Development Team Coordination: - Explain approved requirements clearly to developers, designers, database teams, and testers. - Conduct requirement walkthrough and clarification sessions. - Resolve functional queries during development. - Ensure developers understand business logic, validations, workflows, dependencies, and acceptance criteria. - Work closely with Project Managers to track requirement-related dependencies and risks. 7. Functional Testing & Quality Validation: - Review developed modules from a functional and business perspective. - Ensure the application has been developed according to approved requirements. - Validate workflows, calculations, forms, reports, dashboards, business rules, permissions, and integrations. - Identify gaps between approved requirements and implemented functionality. - Coordinate with QA teams for test scenarios, test cases, defect clarification, and closure. 8. User Acceptance Testing - UAT: - Prepare UAT scenarios and acceptance criteria. - Coordinate UAT sessions with clients and stakeholders. - Maintain UAT observations, pending points, clarifications, and closure status. - Ensure approved UAT observations are properly communicated to the development team. - Track observations until closure and obtain stakeholder sign-off wherever applicable. 9. Change Request Management: - Evaluate new requirements received during or after development. - Compare additional requirements with the approved scope. - Prepare Change Request documentation with impact on functionality, effort, timeline, and dependencies. - Coordinate with management/project managers for commercial and timeline implications wherever required. - Ensure CR development starts only after necessary internal/client approvals. 10. Client & Stakeholder Management: - Act as a functional SPOC for assigned projects whenever required. - Conduct client meetings, requirement workshops, product demonstrations, and review sessions. - Prepare MOM and maintain action items with owners and deadlines. - Follow up with stakeholders for pending requirements, approvals, master data, integrations, UAT, and sign-offs. - Maintain professional communication with enterprise and institutional clients. 11. Data, API & Integration Analysis: - Understand master and transactional data requirements. - Define data mapping between systems. - Analyse API and third-party integration requirements. - Coordinate requirements related to ERP, HRMS, biometric devices, payment gateways, OCR/AI services, external databases, and other enterprise platforms. - Define import/export and data migration requirements. - Identify mandatory validation, audit trail, and data security requirements. 12. Reports, Dashboards & MIS: - Understand reporting requirements from operational and management stakeholders. - Define MIS reports, dashboards, KPIs, filters, drill-downs, exports, and analytical requirements. - Ensure reports are useful for business decision-making rather than only displaying transactional information. 13. Project Risk & Gap Identification: - The Business Analyst should proactively identify: Incomplete or contradictory requirements, missing business rules, unclear approval workflows, data dependencies, third-party dependencies, integration risks, scope deviation, delayed client inputs, functional gaps, UAT risks, and possible rework. - Such risks should be escalated to the Project Manager and management at an early stage. Required Skills: - Strong Business Analysis and Requirement Engineering skills - Excellent analytical and problem-solving ability - Strong understanding of Software Development Life Cycle (SDLC) - Knowledge of Agile / Scrum and Waterfall methodologies - Strong functional documentation skills - Experience in BRD, SRS, FRS/FSD, User Stories and Use Cases - Process mapping and workflow design - Wireframing and prototyping knowledge - Functional testing and UAT coordination - Client handling and stakeholder management - Change Request and scope management - Strong verbal and written communication skills - Ability to understand complex enterprise business processes - Good knowledge of database concepts, APIs, integrations, and software architecture from a functional perspective - Ability to coordinate with technical and non-technical teams Preferred Tools / Technology Exposure: - Knowledge or working experience with any of the following will be advantageous: Jira, Azure DevOps, Microsoft Visio, Figma, Balsamiq, Draw.io / Lucidchart, Microsoft Excel, PowerPoint, SQL fundamentals, REST APIs, Postman, ERP / HRMS / CRM applications, and Web and Mobile Application Development environments. - Exposure to technologies such as .NET Core, Angular, React, Next.js, SQL Server, APIs, Cloud Platforms, AI/OCR integrations, IoT, GPS, and Industry 4.0 solutions will be an added advantage. Domain Experience - Preferred: - Experience in one or more of the following will be preferr