The goal of the co-production best practice, is to develop a plan to enable your resources to contribute to your Pega implementation while developing their Pega skills and capability.

What is co-production?

Co-production is a commitment of your resources (for example, System Architect or Business Architect) to develop their Pega skills and knowledge for your business. Your resources develop their skills through structured enablement plans. They also participate in designing and building the solution as part of the delivery team. To get the best value from this, you should establish this commitment during the initial project resourcing activities, where you identify suitable internal resources to become proficient in Pega products and Pega best practices.

Co-production resources learn how the application is being built and retain that knowledge for the organization of the client. Client resources also bring their deep business understanding directly to the project team, helping to influence the solution as it evolves. Co-producers become individually self-sufficient after the conclusion of the project. Once Pega-certified, co-producers can continue to develop their application and iterate to achieve additional business outcomes.

What is the value of co-production?

The model-driven architecture of Pega Platform™ enables meaningful, hands-on contributions by your business and IT resources. With co-production, you develop and retain in-house knowledge and skills to maintain and update the application, and the delivery team benefits from business expertise and delivers better solutions. Co-production generates the adoption of the new application in your organization. Internal resources who become Pega certified receive an exciting and challenging career path.

When does co-production take place?

Co-production planning starts early in the Pega Express™ delivery approach as part of the project readiness conversations. You secure the co-production commitments as part of the resourcing planning activities before the project starts. This commitment includes ensuring the team has completed or has a structured enablement plan to complete the mandatory training necessary for their identified Pega role in the project. 

Co-production activities reach their peak during the configuration activities, where your resources will be actively participating in the project to support the delivery of the application. This contribution increases throughout the project through following an agreed structured enablement plan that achieves through training and mentoring greater business architect or technical Pega skills.

By the time the solution progresses to go live, the co-production team can fully support the application and continue with minimal input from the external resources.