Table of Contents

Complete solution design

While journeys and microjourneys are being defined, it is important to ensure that the solution design is taken into account at the same time as they are likely to have interdependencies. The technical team should prepare and share the proposed high-level design and intended class structure with the delivery team.


By reviewing and agreeing on the proposed IT architecture with you, the project technical team can better understand the interfaces and other technical dependencies.

The technical leads prepare the high-level configuration design and class structure documentation to provide guidance to the project delivery team.


By sharing these with the project team before development starts, the delivery teams are immediately aligned around the architecture and proposed Pega application design.

The integrations can be tracked and managed to ensure the documentation and interfaces are provided on time and any other technical dependencies are managed.

By determining the class structure to consider re-use and scalability, the solution can be delivered optimally from day one without the need to re-work.


The technical lead and your architecture team should work together to understand and influence the IT architecture. The project dependencies should be tracked through the RAID log established through governance.

Furthermore, the technical lead should create the high-level configuration design and share this with the delivery (including co-production team) along with the documented class structure.

Suggest Edit

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.