Setting up a Program Board is the most important step in ensuring a successful PI Planning event. This guide provides a comprehensive overview of the three primary methods for creating your first program board. These methods ensure your data is structured for both planning and execution.

The Kendis Only board is a "sandbox" style environment where all data is created and stored internally within Kendis. This is perfect for teams in transition or those who do not use a traditional ALM.

From your ART view, click the + Create Board button and select Kendis Only.

Choose the SAFe® Program Board model. This template automatically sets up the rows (teams) and columns (iterations) required for standard PI Planning.

Board Name: Give your board a descriptive name (e.g., "Q1 Global Payments Plan").

Board Prefix: This prefix will be added to the beginning of every card ID created on the board.

Color & Description: Use the color picker to categorise your board and add an optional description for context.

Terminologies: Define what you call your work items. If your organization uses "Requirements" instead of "Stories," change it here. You can also set Card Colors based on these types to make the board easier to read at a glance.

Team & Iteration Setup: Search for and add existing teams that are part of the ART.

Manually enter iteration titles (e.g., "Sprint 1") and their specific Start/End Dates.

Preview: Review the generated grid. Each cell represents the intersection of a Team and an Iteration.

Click Save to launch.

This method links Kendis to your Jira instance, allowing for a two-way sync where updates in one tool reflect in the other.

Follow these steps to create your new Program Board with Jira. Click + Create Board and select Jira.

Choose a saved Jira configuration or select + Add New.

If adding new, select Jira Cloud (or Server/Data Center) and enter your Username and API Token.

Click Test Connection. If this fails, Kendis cannot pull your Jira issues.

Define Terminologies: Align the Kendis naming convention with your Jira Project's naming (e.g., Epic vs. Feature).

Map Teams and Sprints: Select which Jira Teams and which specific Sprints should be pulled onto the board.

Once validated, click Save. Kendis will begin the initial import of your Jira backlog.

The ADO integration is highly structured, relying on your existing Area and Iteration paths defined in Microsoft Azure.

To ensure your ALM synchronization is flawless and your data flows correctly, please follow these steps crucially:

Select Azure DevOps from the creation menu and choose your verified ALM Account.

Provide a clear name and unique prefix, then click Next to define your organization's specific terminologies.

Click Add Projects from ADO; search for and select your specific project (e.g., "Great Minds").

Team & Work Item Mapping: Add your teams and define the Work Item Type (e.g., "User Story") so Kendis accurately identifies the backlog items in ADO.

Iteration Mapping:

Select your specific sprints from the ADO iteration tree.

Review the Iteration Mapping Preview.

Ensure the dates align perfectly with your actual PI calendar to avoid scheduling conflicts or orphaned items later.

Feature Retrieval Logic:

Choose Include Features from the iteration path. This is the recommended "Smart" way to pull features automatically.

You can also use a custom ADO Query for more complex filtering needs.

Dependencies & Fields: Map how ADO "links" should appear in Kendis (e.g., Successor/Predecessor) and select any Custom Fields, such as Acceptance Criteria, that you want visible on the digital cards.

Carefully review the generated board preview and click Create Board to launch your workspace.

Regardless of the board type you choose, the goal is transparency. A well-configured board acts as a single source of truth for the entire ART.

For Kendis Only: Focus on clear labels and manual data accuracy.

For Jira/ADO: Focus on correct JQL/Area Path mapping to ensure the right data is synced.

By following these steps, you ensure that when your teams log in for PI Planning, they are greeted with a board that is ready for collaboration, dependency mapping, and committed objectives.