Identifying roles on a Pega Project

For every Pega project, collaboration across a diverse set of roles is essential to delivering strategic outcomes efficiently and effectively. The following overview highlights some of the key roles involved in Pega project delivery:

• Product Owner (PO): The Product Owner is a representative from the client’s Business team who manages the scope of the project and prioritizes requirements throughout the software development lifecycle. The PO ensures that the application aligns with strategic business outcomes and is delivered within the expected timeframe. The PO prioritizes requirements in sprints so that each release of the application delivers its own material business value.
• Project Manager: The Project Manager is responsible for leading the Pega delivery team, maintaining project governance, and serving as the primary liaison with the client’s leadership team. The Project Manager ensures that the project remains on schedule, within budget, and in scope.
• Scrum Master: The Scrum Master promotes and supports the Scrum framework, an Agile-based software delivery methodology. Responsibilities include organizing the Scrum team, facilitating ceremonies such as Sprint Planning, Sizing, Backlog Refinement, and Retrospectives, and ensuring the team’s overall success by removing impediments during the development process.
• System Architects (SAs):  System architects configure the Pega applications. This role includes System Architects (SAs), Senior System Architects (SSAs), and Lead System Architects (LSAs). LSAs are responsible for importing Blueprint files into Pega Platform and configuring both functional and technical requirements based on user stories.
• Quality Analysts (QAs): Quality Analysts verify that the application functions as intended and meets documented business requirements. They create test scripts and scenario tests based on user stories and participate in Scrum rituals to ensure testing efforts are appropriately sized and scheduled.
• Subject Matter Experts (SMEs): SMEs are client representatives with deep operational knowledge of the business process. They provide specific functional and operational requirements and often participate in walkthroughs to demonstrate how end users interact with current systems and processes.
• Business Architect: A Business Architect plays a key role in translating business needs into functional application requirements by analyzing current processes and identifying opportunities for improvement. They help define workflows, Data Models, and user experiences that align with strategic goals, ensuring the application delivers value to both end users and stakeholders.
• UX Designers: UX Designers ensure that the application’s design meets user needs, complies with accessibility standards, and delivers a consistent experience across all deliveries. They focus on optimizing the user interface to align with strategic business goals and usability best practices.
• Solutions Consultant: The Solutions Consultant engages with the client during the early phases of the sales process. They often co-design the Blueprint with business stakeholders and transition it to the delivery team once the project moves forward.

Each team member, including those in the roles outlined above, brings unique expertise and responsibilities that collectively drive the success of the initiative.

Pega Platform™ provides four role-based authoring spaces, referred to as Studios. Each studio provides specific tools and features for application development. When using the appropriate studio, Pega project team members are enabled to complete tasks by using tools that align with their role and expertise.

Pega Platform studios:

• App Studio: Pega's no-code authoring space is designed for use by most of the roles on a Pega project including system architects, business architects, UX designers, and solutions consultants. Project Managers use App Studio to deliver application documentation. Scrum Masters can use App Studio to manage user stories for development team. To learn more about App Studio, see App Studio overview.
• Dev Studio: A low-code authoring space with advanced configuration options for technical team members including system architects and quality analysts. To learn more about Dev Studio, see Dev Studio overview.
• Prediction Studio: An analytics space used by data scientists and decision-makers aligned more with the business than application development. To learn more about Prediction Studio, see Prediction Studio overview.
• Admin Studio: A software administration space managed by the business-related IT staff for system administration. To learn more about Admin Studio, see Admin Studio overview.