We are using JIRA Team Managed Project. We are following a structure in JIRA to managed our OKRs based on these recommendations: Sprint: Quarter. Epic: Objectives. Stories: Key Results. Tasks/Subtasks: what we need to do to achieve the KR. In the board configuration we can group by Epic or Subtasks but not by Epic-Story-Tasks-Subtasks.
You may want to create additional swimlanes that map to other values of your Jira 'Priority' field, or use a different field to categorize your swimlanes. Assignees. One assignee per swimlane, with unassigned issues appearing either above or below the swimlanes (your choice). Epics. One epic per swimlane. Issues that don't belong to an epic are Step 2: Use epics as objectives and issues as key results. Before listing your OKRs, there are a few details you need to customize. For non-Jira admins, you can use Epics as Objectives and Tasks as Key Results. But if you’re a Jira admin, you can simply rename Epics to Objectives under Issues > Issue Types. Jun 24, 2021. Initiatives, epics, and stories belong to the agile realm. From here the surprises begin. It turns out that the popular Initiative – Epic – Story hierarchy is not engraved in stone. Scrum, Kanban, SAFe, and LeSS approach initiatives, epics, and stories differently. It is the “living backlog”, rather than epics and stories Step 2: Fill your sprint with stories from the backlog. Once you've created your sprint, you'll need to fill it with issues. Before you do this, make sure you sit down with your team and discuss what work you'd like to commit to doing. Ensure you add enough work for everyone in the team. 0Q1RvHN.