OKRs, Epics & Stories – practical example

OKRs Epics Stories

Written by admin

March 4, 2019

Following up on the article about OKRs, Epics & Stories, I have an exercise that I always use when explaining to the teams I coach why I think this is a good idea.

Exercise with OKRs

Cucumber Solution

For the whole Cucumber Solution we have 3 Objectives, like:

  • We have the fastest Cucumber process of doing transactions
  • Our solution has the most efficient calculation of Cucumber data
  • We provide the Cucumber report in the most seamless way

These are the big solution Objectives for the next OKRs Cycle.

Now, these Objectives have 3-5 Key Results each, clear Outcomes that help us track some progress towards the Objective.

From the framework OKRs – Epics – Stores, the OKRs part is defined. What happens next is that the team(s) now define how many Epics they need to reach any of the 3 Objectives. Remember that an Epic is a bigger functionality that cannot be delivered in 1 iteration. So it ends, it’s not a label, a category of activities.

For the fastest Cucumber process of doing transactions 5 Epics might be enough to reach some key results, for most efficient calculation of Cucumber data maybe 8 Epics will be needed and for Cucumber report in the most seamless way 4 Epics will be enough.

So, 3 Objectives and 17 Epics for the next period of time of our Cucumber Solution. You can split the 17 Epics into Stories from the beginning, or prepare only next 2-3 sprints and then split them Just in Time and Just Enough, nevertheless you commit on reaching the Objectives, not doing the Stories, Outcome not Output.


You will get better at this over time so you might reach the conclusion after 5 sprints that one Epic is not needed anymore because you discovered another way, better way, of doing some functionality. Or you may add another Epic that you did not think of in the beginning. Responding to change over following a plan, remember?

Your commitment doesn’t change, the Objectives, the Outcome, the What. The output of your sprints, the How, can and should get better with time, you will be more efficient, you will work smarter rather than harder, you will become more mature and, by using Objectives that drive your activities, you also have focus over this team development process.

You might also like…

getKanban – Experiential Kanban board game

getKanban – Experiential Kanban board game

Either you want to switch for your current way of working to Kanban, or you want to map some Kanban principles on your current way of working, this game is a great way to find out what fits you the best. 

Organizing a process improvement workshop inspired by the Lencioni model

Organizing a process improvement workshop inspired by the Lencioni model

A team asked for a product discovery workshop. After addressing few upfront questions, I realized very fast that their poor and unpredictable velocity is not caused by uncertainty on the product level; it was the foundation that was actually missing – the absence of trust on the team level (Lencioni’s 5 Dysfunctions of a team).

The road to Lean HR

The road to Lean HR

One example of Value Stream is “Recruiting for new employees”. The trigger is clear, there is a need for a “Java Developer”. The end of the Value Stream is “java developer available”.

1 Comment

  1. Franz Pouchet

    Eugen, thanks a lot for this article. That really cleared things up. Now I see the link between epics; linking my Jira software to my OKR saas makes a whole lot more sense.


Submit a Comment

Your email address will not be published. Required fields are marked *