Business System Analyst 3

Job Location

Warsaw. Travel may be required based on project needs.

Overview

The Delivery Business Analyst III defines, analyzes, and manages complex requirements for system delivery initiatives.

This senior individual contributor role produces delivery-ready documentation, supports cross-functional alignment, and ensures requirements remain clear, controlled, and traceable through implementation and handoff.

Primary Focus

• Define complex requirements across scope, integrations, reports, interfaces, configurations, and workflows.
• Own FRDs and supporting delivery artifacts for assigned requirement areas.
• Perform analysis, impact assessment, change control, and traceability.
• Ensure requirements are usable by delivery, testing, customer, and service teams.

Responsibilities

Advanced Requirements Elicitation and Analysis:

• Facilitate complex requirements discovery sessions where scope, stakeholder needs, or solution direction may be unclear.
• Elicit, analyze, validate, and document business, functional, and non-functional requirements across multiple workflows or system areas.
• Identify gaps, unresolved decisions, edge cases, exception flows, and downstream impacts before development begins.

Complex Requirements Documentation:

• Author and maintain FRDs and supplemental requirement packages with minimal rework.
• Document detailed business rules, configuration logic, workflows, interfaces, reports, data dependencies, acceptance criteria, and operational impacts.
• Ensure artifacts are complete, consistent, and easy to use.

Gap Analysis and Cross-System Impact Assessment:

• Compare customer needs, product capabilities, and project requirements to identify gaps.
• Assess impacts across functionality, integrations, reporting, configuration, operations, and handoff.
• Document customization needs, assumptions, risks, constraints, options, and decisions.
• Validate recommendations with Product, technical teams, QA, and project stakeholders.

Change Control and Traceability:

• Assess requirement changes for scope, schedule, cost, quality, testing, and operational impacts.
• Maintain traceability from approved requirements through design, development, testing, implementation, and handoff.
• Document baselines, revisions, approvals, and change rationale.

Testing, Validation, and Acceptance Criteria:

• Define clear acceptance criteria for complex requirements and business rules.
• Partner with QA to validate requirement coverage across test scenarios, test cases, defects, and UAT activities.
• Review defects to determine requirement gaps, clarification needs, or change control impacts.
• Support customer validation by explaining requirement intent, decisions, constraints, and solution behavior.

Delivery Documentation Quality and Handoff:

• Ensure final documentation reflects approved scope and delivered functionality.
• Support service transition with documentation of key requirements, configurations, open items, and known impacts.
• Contribute reusable examples, templates, and improvements to strengthen requirements consistency.

Qualifications

• Typically 5 to 8 years of business analysis, requirements management, systems delivery, or software implementation experience.
• Experience writing FRDs, SRS-style documentation, business rules, process flows, use cases, or equivalent delivery artifacts.
• Strong SDLC knowledge and experience supporting Agile, Waterfall, or hybrid delivery models.
• Advanced written communication skills with the ability to produce review-ready documentation.
• Experience with gap analysis, impact assessment, change control, and traceability.
• Ability to work independently with customers, Product, Engineering, QA, PMO, and Service stakeholders.

Preferred Qualifications

• Experience with requirements management and delivery tools such as Polarion, Jira or similar platforms.
• Experience on large-scale implementations, conversions, migrations, product rollouts, or regulated technology delivery programs.
• Strong background in business process modeling, interface/report requirements, configuration requirements, and formal baseline management.
• Familiarity with lottery, gaming, enterprise systems, or complex transaction-based platforms.

Core Competencies

Success Measures

• Requirement packages are clear, complete, traceable, and accepted by key stakeholders.
• Gaps, edge cases, and downstream impacts are identified early and documented.
• Engineering and QA teams can build and validate solutions with minimal clarification cycles.
• Requirement changes include clear impact analysis, rationale, approvals, and traceability.

Success Profile

• Leading Complexity
• Leading People
• Leading the Business
• Leading Self

#LI-JB1 #LI-Hybrid