• Product Management – Defines and prepares features for the upcoming PI Planning. Often handled by multiple people across different products.
• Product Owners – Refines the feature backlog, creates user stories, and works with teams to ensure development aligns with business goals.

These roles have very different workflows:

• Product Management gathers feedback, negotiates priorities, and secures approvals.
• Product Owners refine features into stories, work with UX, architects, and development teams, and prepare everything for execution.

Instead of using multiple statuses in Jira or ADO, Kendis allows teams to visually manage these workflows across Kanban boards.

• Unstructured refinement where teams struggle to align on feature readiness.
• Product Owners and Managers creating their own fragmented workflows.
• Features being too vague or overly technical, leading to delays in PI Planning.

Before diving into your Pre-PI Planning session, ensure the following:

• 1. Define Objectives – Clearly outline team goals for the upcoming PI.
• 2. Review Backlog – Prioritize and refine backlog items to ensure they’re well-defined and estimated.
• 3. Stakeholder Input – Gather feedback from key stakeholders to align on priorities.
• 4. Capacity Planning – Assess team capacity while considering time-off constraints.
• 5. Dependencies – Identify and document cross-team dependencies.
• 6. Communication Plan – Set expectations on how information will be shared during the session.

This is what Kendis solves. it provides a structured, visual approach to pre-pi planning that ensures features are truly ready for PI Planning.

• Org View Access – How to check if you have access.
• Contact Support – If you need assistance, reach out to our team.
• Accessing Kanban from Collection – Ensuring the toggle is enabled to see the board.
• Kanban List Overview – Reviewing Kanban options before setting up.

• Pulling in Features from custom Jira/ADO filters.
• Mapping Columns to Jira/ADO statuses (or using them independently for more flexibility).
• Kanban Columns Can Map to:
• Jira/ADO Statuses
• Non-ALM Statuses
• Other Kanban Boards
• Program Boards
• Drag & Drop Functionality – Move items across columns.
• WIP Limits & Overload Indicators – Prevent workflow bottlenecks.
• Grouping & Filtering by Custom Fields – Organize work based on your needs.
• Creating Kendis-Only Cards – Convert them into Jira/ADO items when needed.

• Move refined Features directly to a PI Board once they’re ready.
• Map Kanban columns to PI Boards, ensuring work transitions smoothly.
• Map Kanban to another Kanban Board, allowing work to progress through multiple workflows across teams.

This approach solves visualization, prioritization, and workflow alignment, so teams can focus on delivering value instead of managing process complexities.

• Selective Kanban Mapping – Choose which Kanban boards receive specific items, instead of mapping only by column.
• Enhanced Dependency Tracking – View and track dependencies directly on Kanban boards.
• Planned vs. Unplanned Items – Identify unplanned items after PI Planning.
• Improved Import Functionality – Quickly populate Kanban boards from external sources.
• Detailed Activity Log – Track changes, updates, and user actions.
• Sub Column Linking – Push and pull for shared workflows.
• Custom Grouping Categories – Group cards using categories like Expedite, Fixed Date, and Standard.