In a Pega Agile project, the Business Architect (BA) is a key liaison between business stakeholders and the technical team. Their responsibilities include collaborating with stakeholders to define the vision and roadmap, which involves planning for current and future application needs (C). This plan is translated into a product backlog, which the BA is responsible for building and refining with user stories, thus managing the project team's backlog (A). To ensure the developed solution meets the business requirements, the BA also develops scenarios and acceptance criteria to test the application's functionality (B), confirming the user stories are implemented correctly.

D. Assign IT team members user stories to work on.

This is incorrect. In Agile methodologies like Scrum, the development team is self-organizing and pulls work from the prioritized backlog during sprint planning; work is not assigned by an individual.

E. Execute the assigned work on schedule.

This is incorrect. The responsibility for building and implementing the application features (executing the work) lies with the development team, such as System Architects, not the Business Architect.

---

1. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"The Pega Business Architect role" module

"Key responsibilities of a Business Architect" lesson.

This lesson explicitly states that a Pega Business Architect is responsible for "building a backlog of user stories" which aligns with (A) Manage the project team's backlog. It also states the BA must "work with stakeholders to define business objectives" and "define business requirements

" which supports (C) Plan current and future application needs.

2. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"Validating a Pega application" module

"Testing an application" lesson.

This section details the BA's role in quality assurance

stating

"As a Business Architect

you are responsible for application testing and validation. You confirm that the application meets the business requirements by creating test cases and scenarios." This directly supports (B) Develop scenarios to test application functionality.

3. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"Designing a Pega application" module

"Defining the scope of the MLP" lesson.

This lesson describes how the BA works with stakeholders to define business outcomes and the scope of the Minimum Lovable Product (MLP). This activity is a core part of (C) Plan current and future application needs.