Maintaining the backlog

Blueprint Delivered changes how the backlog is created and refined. The team starts with Blueprint-generated work objects, not a blank backlog. This approach helps reduce duplicate discovery work and keeps the team focused on delivering value from the imported Blueprint.

To apply lean, agile practices, complete the following steps:

• Start with the generated work objects.
• Preserve Blueprint intent.
• Refine only what needs more detail.
• Fast-track simple items when appropriate.
• Add acceptance criteria that are clear and testable.
• Keep the backlog current as the application evolves.
• Use Task Board or an external tool to track the work according to the process the team follows.

In Blueprint Delivered, backlog creation begins with the imported Blueprint. The generated work objects in Task Board provide an initial structure for the project backlog. These work objects are based on the Blueprint design and help the team start from an existing application foundation instead of creating all backlog items manually. Use the imported Blueprint as the source of context. Refine the backlog to preserve the original design intent instead of recreating the requirements from scratch.

The first version of the backlog does not need to include every detail. The backlog evolves as the team reviews the imported artifacts, validates the application against the Blueprint, and refines the generated work objects. As the backlog matures, the team adds the details needed to support build and validation, such as business context, open questions, and dependencies.

Backlog refinement is the process of reviewing and updating backlog items so that the team can act on them. In Blueprint Delivered, refinement focuses on turning generated work objects into clear, build-ready or validation-ready user stories.

During backlog refinement, the team completes the following tasks:

• Reviews generated work objects in Task Board.
• Confirms that each item reflects the intended Blueprint design.
• Adds missing business details.
• Clarifies acceptance criteria.
• Identifies dependencies or open questions.
• Determines whether changes belong in Blueprint or in Pega Infinity Studio.
• Updates the backlog based on new information from validation or stakeholder review.

Keep refinement lightweight and outcome-focused. Not every requirement needs extensive documentation. If a simple item can be clarified, configured, or validated directly, the team avoids unnecessary documentation.

The backlog changes over time as the team learns more about the application, validates generated artifacts, and identifies new work. Prioritization helps the team decide which work to refine, configure, or validate first.

When prioritizing backlog items, consider the following factors:

• Business value
• Impact on the application outcome
• Dependencies between work objects
• Readiness of the user story
• Complexity of the configuration
• Requirement to validate the imported Blueprint
• Dependency of other work on the item

The team regularly reviews the backlog to keep it aligned with the application goals and the Blueprint design. New work objects might be added, existing work objects might be refined, and some items might no longer be needed.

Use Task Board to manage and refine generated work objects after Blueprint import. Task Board helps the team track work, update status, and maintain traceability between the imported Blueprint and the application work.

If the project uses an external planning tool, such as Agile Studio or Jira, Task Board can still support refinement before work is tracked in the preferred project-management tool.

Check your knowledge with the following interaction: