Recommended build order and a single outcome

Rather than importing all Pega Blueprint™ content at the same time, import and complete one Case Type at a time. This sequence reflects Minimum Lovable Product (MLP) thinking. For each Case Type, the team imports it, validates it, integrates it, and confirms that it is fully functional before moving on to the next. This focused, iterative approach prevents unresolved issues from accumulating across multiple Case Types and keeps the team oriented toward a functional, demonstrable result at every step.

After the initial import, merge the import branch to create a stable baseline before you begin any feature development in separate branches. Starting feature work directly in the import branch is a critical anti-pattern in Blueprint Delivered, because it conflates design validation with feature delivery and makes issues difficult to isolate.

The build order consistently prioritizes end-to-end functionality over depth of configuration. A working, navigable application, even one with simplified logic or generated sample data, is more valuable at this Stage than a partially complete application that has highly refined but untestable components.

In Stage 2: Security and data integration, implement data retrieval integrations before data persistence and advanced integrations:

• Data retrieval first. Retrieving data populates the application with realistic information early, which makes validation more meaningful.
• Persistence and write-back next. These integrations follow after the data model is confirmed to be stable.

In Blueprint Delivered, the outcome is the unit of delivery, not the sprint, the module, or the Case Type list. You make every build decision in service of delivering a working, validated outcome.

Check your knowledge with the following interaction: