PEGA Technical BSA

Roles and Responsibilities :

• Has practical exposure to the Pega PCS framework

• Conduct stakeholder interviews, workshops, and DCO sessions

• Conduct stakeholder interviews, workshops, and DCO sessions

• Understand business processes, pain points, and objectives

• Gather and document:
o Business Requirements (BRD)
o Functional Requirements (FRD)
o Use cases & process flows

• Perform gap analysis (current vs future state)

• Convert requirements into:
o User Stories & Acceptance Criteria
o Case types, flows, stages, SLAs

Define:
o Business rules
o Data mappings
o UI/UX logic (screen mockups)

• Ensure solution aligns with Pega framework capabilities

• Participate in Agile ceremonies:
o Backlog grooming
o Sprint planning
o Daily stand-ups
o Sprint demos

• Create and manage Product Backlog Items (PBIs)

• Prioritize and refine user stories with Product Owner

• Work closely with:
o Lead System Architect (LSA)
o Senior System Architect (SSA)
o Developers

• Clarify requirements and constraints

• Validate the feasibility of business requirements in Pega

Support:
o SIT (System Integration Testing)
o UAT (User Acceptance Testing)

•

Responsibilities include:

o Defining acceptance criteria
o Reviewing test cases
o Validating solution against requirements
o Ensuring BA sign-off before test execution [Cognizant...ementation | Word]

• Act as a single point between business stakeholders and IT team

Conduct:
o Playback sessions
o Demos
o Requirement clarification calls

• Manage expectations and drive approvals

Documentation & Deliverables:

Key deliverables:

• BRD / FRD

• User stories + acceptance criteria

• Process maps/workflows

• Data models/mappings

• UI mockups/wireframes

• Traceability matrix