Task Board

Task Board is a software tool used in a Pega Platform project to track feature development and manage work after a Blueprint is imported. Task Board helps teams refine work, track progress, and connect Blueprint intent to implementation.

You can associate work objects with features or subfeatures to maintain traceability between the application work and the capability being developed. Features represent capabilities that the application supports. Subfeatures represent smaller units of work within a feature. When you create a Case Type in the application, Pega Platform creates a corresponding feature with the same name. For example, you can associate a task for updating a drop-down field with the feature that represents the related Case Type.

In Blueprint Delivered, features and generated work objects help the team preserve the intent of the imported Blueprint. The team uses these work objects as the starting point for refinement instead of manually recreating the backlog from scratch.

Work objects become the backlog of development work. In Task Board, teams use Tasks, also called user stories, to describe and refine business requirements.

After Blueprint import, the team uses generated work objects to identify what needs to be reviewed, clarified, configured, or validated. Teams refine the generated work objects by adding enough detail to support development, including clear descriptions, acceptance criteria, and any required business rules. Blueprint notes and descriptions can help inform user story content during refinement.

Status

Each work object includes a status of To do, Doing, or Done. You change the status of a work object by moving the card to the appropriate column or by updating the status on the work object itself.

In Blueprint Delivered, status tracking helps the team understand whether imported or generated work objects still need refinement, are actively being refined, or are ready for build. Refinement preserves Blueprint intent rather than recreate the design.

Refinement is the process of improving a generated or draft work items until they are ready for build or validation. The purpose of refining a work item is to ensure that your team has a complete understanding of the intent and scope. In Blueprint Delivered, refinement begins with the generated work objects from the import, not with a blank page. 

During refinement, the team completes these tasks:

• Reviews the generated work object.
• Confirms that the work object reflects the Blueprint intent.
• Adds missing business details.
• Identifies non-functional requirements, such as accessibility requirements.
• Clarifies acceptance criteria.
• Identifies dependencies or open questions.
• Determines whether the change belongs in Blueprint or in Pega Infinity Studio.
• Updates the work object so it can support development, validation, or testing.

Refinement is an iterative process that matures the work item content to meet the definition of ready. Refinement focuses on outcomes and avoid unnecessary documentation. Do not add unnecessary documentation when the team can clarify or configure a simple item directly.

Refining work in Task Board

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

As you refine the work item, you might realize it is too big or complex. In that case, break it out into more than one work item. Alternatively, refinement might expose a gap in the requirements and necessitate adding additional work items to your backlog.

The refinement process ends when the following conditions are met:

• The team agrees that they understand the work to be completed.
• The team adds all supporting information to the work object.
• A team lead approves the acceptance criteria.

Check your knowledge with the following interaction:

In a typical Blueprint Delivered scenario, a team imports a Blueprint into Pega Platform and reviews the generated application artifacts. The team then uses Task Board to refine the generated work objects that support the build.

For example, after importing a Customer refund Case Type, the team reviews the generated Case Type, data objects, Personas, and related work objects. If the team identifies missing details or configuration updates, the team records or refines those items as Tasks in Task Board. Each Task includes enough information to support build or validation without requiring the team to redesign the Blueprint.

This approach supports lean, agile development because the team starts with Blueprint-generated work, refines what is needed, and avoids unnecessary documentation when an item can be clarified or configured directly.

Task Board supports development tracking in Agile Studio, a separate Pega Platform tool that expands the Task Board functionality with more robust features for release management, progress tracking, team capacity, and analytics. Task Board can also integrate with external tools, such as Jira or CA Agile Central, when required by the project. The integration abilities of Task Board enable clients to use their existing infrastructure.

Use Task Board to refine generated work objects and maintain traceability during post-import work management. If the team uses another backlog tool, such as Agile Studio or Jira, Task Board can support refinement before work is tracked in the preferred project-management tool.

Check your knowledge with the following interaction: