In this video, we will cover, * How to create SAFe® Proram Board for your PI Planning. * Configure Teams and Sprints * Get Features from Atlassian JIRA

1. Agile Scaling Platform
www.kendis.io
Guide to Create Board

2. Kendis
What we will cover?
2
• Create Board
• Configure Teams and Sprints
• Get Features from JIRA
• Example Program Board

3. Kendis
Create Board
3

4. Kendis
1. Select Board Type
4
• Kendis offers supports for the multiple scaling models. Choose the board type you want
to create.
• Board types are
• SAFe® - Program Board for the PI
• Spotify Scaling Model
• Scrum of Scrums Board
• Custom Model

5. Kendis
2. Board Name
5
• Type the board name .
• Choose the Board Configuration
• With JIRA
• Supports 2-way sync between Kendis and JIRA, able to get the features, stories and other items from JIRA
into Kendis for Planning and Tracking.
• Without JIRA
• Suitable for the brainstorming of the ideas or other custom needs.
Note: In this presentation we will only cover the “With JIRA” connected Board

6. Kendis
3. Select JIRA Connection String
6
• Select existing JIRA connection or click on the “Add New” to create new
• Add New Connection
• Type Connection Name (It’s just a label to identify the settings)
• URL : <Your JIRA URL>
• Kendis supports both the Cloud and Self-Hosted JIRA
• Username : <JIRA username that you use to login>
• Best practice is to use the ”service user”, otherwise, you can also start with normal user account and change
it later to service user.
• Password: <JIRA password of the user>
Note: More detailed information about the JIRA connection available at

7. Kendis
4. Define Item Labels
7
Kendis boards supports 2 levels at each board. You can label the parent and child items as
you like
• Parent Item
• It’s pre-filled as “Feature”.
• It’s only a label and can be changed later
• No relation to actual JIRA Item type
• e.g., call your JIRA epics at Kendis as “Features”
• Child Item
• It’s pre-filled as “Story”.
• Edit as you like, e.g., “Team Story”

8. Kendis
5. Select Teams
8
Like a physical board, you can name your teams anything you like. You don’t have to name
them like JIRA projects, as linking between Teams and JIRA projects is done later.
• Create Team
• Name : Full name of the team, like “Team Whale”
• Prefix: Max 5 chars team prefix>
• Color: Select different color for each team
• Select Existing Teams
• In case you have existing teams, just select from the list.
Note: You can add/edit teams at the board later as well!

9. Kendis
6. Add Sprints
9
Define the sprints or iterations for your board. By default 5 sprints are created.
• Edit Sprint
• Name : Title of the Sprint, it’s just a label that will appear at the top of the board for each column
• Prefix: Max 5 chars sprint prefix, e.g., SP5.1
• Dates: Sprint start and end dates, these are optional, however it’s good to set them as they will appear on the
board.
• Note: these dates are not dependent/connected to JIRA sprints
Note: You can add/edit sprint names and date at the board later as well.

10. Kendis 10
7. Preview Board

11. Kendis
Configure Teams and Sprints
11

12. Kendis
8. Configure Teams
12
User with “Admin” rights would be able to edit the board and configure settings.
• Go to Settings from top right corner and select “Edit Board Settings”
• Select on the Teams tab
• Teams can be local Kendis or they can be linked to JIRA projects and sprints.
• Click on the Settings icon in front of the team name
• Click on “Sync to JIRA” and you will be able to define the JIRA settings

13. Kendis
8.a. Sync to JIRA Settings
13
1. Sync to JIRA
• Enable to configure team to connect to JIRA
2. Team Board at JIRA
• Project: Select team project name
• Board: All the boards under the project are shown, select the
relevant one. It must be “Scrum Board” with the Sprints
• Type: The default selection of the item type
3. Select Existing Sprint
4. Create New Sprint: Kendis will create sprint at the
board automatically.
5. No Container: The cell at the board is not mapped to
any sprint.

14. Kendis
8.b. Configure All Teams
14
Now complete the JIRA configuration settings for all other teams one by one
• Teams with correct configuration to JIRA will be shown with the green circle
• Teams that are not configured to connect to JIRA will show grey icon
• It’s useful to use not to sync JIRA options in case you are having external dependencies, risks or milestones that
don’t exist in JIRA

15. Kendis
Get Features from JIRA
15

16. Kendis
9. How it works?
16
To get your features into Kendis from JIRA you should consider following
• Go to JIRA and create a filter with all of your features that you want to get at Kendis
• Ensure the filters privacy setting is “Any logged in User” or your relevant group
• Ensure the filter is marked as “Favorite” at JIRA
• Click on “Sync to JIRA” and you will be able to define the JIRA settings
• Important Note
• Filter should only contain the parent items like “Features”, e.g., if your features are Epics in JIRA then only include the Epics
in the filter.
• Connected stories to your features will be fetched automatically
• You can use multiple filters at Kendis to get features.

17. Kendis
9.b Get Features from JIRA
17
• Go to Settings from top right corner and select “Edit
Board Settings”
• Select the “Backlog Filters” tab
• Search and select the filter
• Filters content count will be shown, clicking on the count will
open it in JIRA.
• Select the linking between the features (parent item) and the
(child items) like stories.
• If your features are Epics, then choose “Epic Link”, if you are using
”Issue Link” then choose the relevant “Issue Link” type, e.g., “is
Implemented By”

18. Kendis
Example Kendis Board
18

19. Kendis
Next Steps
19
To get your features into Kendis from JIRA you should consider following
• Now your features and their linked stories are at Kendis. You can start using the board for your actual
usage.
• Use the Kendis board to plan and track your Program Increment for your Agile Release Train or any
other purpose.
• Check the https://help.kendis.io for other help guides

20. Kendis
Thank You
20
For more info contact us at
team@kendis.io
www.kendis.io