To take advantage of Pega’s experiential delivery model, business staff have meaningful involvement in the development of their Pega application. This involvement is achieved through co-production. Your business staff receive formal training before the project starts for the role they are expected to participate in the project. During the project, the newly enabled team resources work side-by-side with experienced Pega mentors in building the application. In this process of “learn by doing”, the new resources will learn best practices and gain proficiency so they grow their role on the development team. Within a short window, your resources become able to support and expand the applications on their own.
What and Why
To get started, select a minimum of 3 people and provide the appropriate role based training. The critical roles to start are the:
- Business Architect (BA) – Drives working sessions to gather and analyze requirements; pick someone that works in the business but shows an acumen for technology. They know what process automation is, flow charts, process diagrams – these types of resources can easily learn Pega and make a great BA.
- Product Owner (PO) – Sets priorities and the backlog of what to build; best choice is a decisive person, which greatly influences your project velocity.
- System Architect (SA) – Designs and builds components of the applications; look for someone with some programming skills but more importantly, someone who loves to build – likes to move quickly and not be tied to building lines of code.
Typically this training is completed online via the Pega Academy. Alternatively, instructor-led training can be attended at one of public Pega’s training centers, or as dedicated onsite courses. Mentored self-study options are also available. Certifications are available via a network of certified testing centers.
Contact the methodology team at firstname.lastname@example.org for a more comprehensive enablement planner if needed.