Subscribe to News

    Popular Stories

    7+1 Principles And Five Frameworks for Agile Portfolio Prioritization
    Weave Toolkit: SAFe PI Planning with Weave
    Giving Thanks for Portfolio Management
    Agile 2015 Keynote: Awesome Superproblems
    Case Study: How to Take the Pain out Portfolio Prioritization
    Written by Luke Hohmann
    on March 31, 2017

    Somewhere along the line the Agile community decided to use the word "Epic" to mean "Product Backlog Item too big for a Sprint". I've contributed to this use of the word in our training, often thinking it was helpful. 


    I now realize this can be pretty harmful, because I'm seeing too much excess baggage that does nothing more than slow down a team and not enough epics. 

    Epics Should Be Epic Wins

    To understand what epics should be in agile teams, let's consider how the Merriam-Webster dictionary defines epic:

    1. of, relating to, or having the characteristics of an epic • an epic poem
    2. a: extending beyond the usual or ordinary especially in size or scope
        b: HEROIC 

    Clearly the second definition is what the Agile community means: A Product Backlog Item that is beyond the usual or ordinary size or scope [for a Sprint]. That's what they are, but not what they should be.

    To understand what an epic should be, you'll have to turn to the game community. 

    I'm a game designer. So are you (watch my Agile 2015 keynote and you'll see why). When game designers and gamers think of the word "epic" we immediately associate it with the word "win": "Epic Win". We have to move from Merriam-Webster to the urban dictionary 
    for this definition:

    A win so great, so awesome that it is EPIC.

    We see Epic Wins in sports when the underdog overcomes great odds to win a championship. We see Epic Wins in business when a small but more agile and responsive competitor manages to take a contract from a slower, larger, and less-responsive opponent. We even experience Epic Wins in our personal lives, such as when we or a friend recovers from an illness or when neighbors join forces to agree on budget cuts to balance their budget.

    This leads to a natural reframing of what an epic should be:

    Epics in agile teams should create epic wins for customers. 

    It is that simple: If you're claiming that something is "epic", you'd better be able to show me how it produces an "epic win" for your customers. If you can't, you don't have an epic win, you have excess, bloated backlogs that are just slowing you down.

    Fly Light and Fly Fastemotional-baggage-2.png

    I'm a pretty frequent flyer and like most of my frequent-flying peers I make certain my bag can fit into the overhead compartment. Unfortunately, not everyone is as considerate and I have a considerable amount of empathy for flight attendants to who have to deal with passengers who try to break capacity guidelines.

    Product Owners who stuff too much into their backlogs and Sprints remind me of the luggage cheaters who bring suitcases into the main cabin when they know that those bags will likely be rejected. If they do manage to get their luggage stuffed into the compartment they take up space from other passengers who are playing by the rules. 

    What they should do instead is lighten up their Sprints and drop the excess baggage. This doesn't mean you can't have "big" backlog items. Indeed, we need epics, because we need big innovation. 


    What Should We Call "Big" Product Backlog Items

    I've been thinking about this quite a bit, because I realize that this post isn't likely to change the terminology of the Agile community (though I've been somewhat successful in helping organizations use "Planning Flame" instead of "Planning Onion").

    Here are my current favorite alternatives to Epic, when epics mean "big".

    MONSTROUS: is defined as both "having extraordinary often overwhelming size" and "having the qualities or appearance of a monster". If you've got large, ill-defined PBIs that don't provide clear value, you don't have epics, you have a bag full of monsters. 

    EON: An eon is a "an immeasurably or indefinitely long period of time". Eons fit many of the challenges facing Agile teams who are dealing with substantial technical debt or must deal with various kinds of infrastructure changes, because these situations may require substantial, sustained investment that may not result in truly epic wins for customers. As the team sheds unnecessary items, their bags naturally get lighter. 

    Epics and Normal PBIs from Conteneo

    To help illustrate the differences, let me share some recent Epics from Conteneo's work and perhaps contrast them with "normal" backlog items or user stories. 

    Epic: Localize Weave in Multiple Languages. We've recently released Idea Engine and Decision Engine localized into French, German and Spanish, with more languages and the rest of Weave scheduled for localization over the next few months. This has been a lot of work, but the epic win we're creating for our global customers and partners by enabling them to conduct forums in the native language of the participants who speak these languages is breathtakingly awesome. 

    Epic: Dynamic Decision Engine. Decision Engine (aka Buy a Feature online) now enables Producers to configure forums so that items can be edited in real-time during the forum. This has created a whole new set of applications and has supercharged portfolio prioritization. 

    These can be contrasted with many of the smaller user stories or PBIs that our dev team just cranks out and handles. The following recent improvements we've made to Weave definitely make the platform better, but probably don't really qualify as epic:

    Unifying our Design Language. Our team has worked hard to make sure that all of the Weave icons, colors, fonts and related design elements are completely unified, creating a much easier to use and far more enjoayble experience. 

    Redesigned emails. Our team has redesigned and simplified the emails Weave generates to keep Producers and Facilitators informed of their forums. 

    Redesigned scheduling and forum screens. Our subscribers provided us with a lot of feedback on how we could make subtle improvements in scheduling and managing forums. Individually, no one change was all that noticable. Collectively, the little stuff does add up and ultimately contributes to an improved user experience.

    Ultimately, every item in your Product Backlog should create value for the company. Most will create benefits for your customer. I sure hope that some are creating Epic Wins - and that none are overstuffed luggage full of clothes you'll never actually need during your trip. 

    I've Got Too Much Baggage and Too Few Epic Wins

    Well, that's not good. So let's fix it. 

    Let's start your epics. If you're unsure of how to create an Epic Win then you need to stop what you're doing and start collaborating with your customers. Use the Conteneo Weave platform to understand their challenges. Then engage them in understanding their priorities. You'll find your epics. 

    speedplan.jpegIf you've got some Monstrous or Eonic (sorry for the new word, but hey, it fits) PBIs then engage your team in helping understanding how to get them converted into something that makes sense. Speed Plane, a variation of Speedboat, will help. Click on the image to get started!


    Let us know what you think. 

    Add your comment below.

    You may also like:

    Agile Scrum PI Planning scaled agile framework SAFe product management

    Weave Toolkit: SAFe PI Planning with Weave

    A challenge faced by many SAFe organizations is creating an efficient PI planning process: one in which the in-person me...


    How to Run HUGE Retrospectives Across Dozens of Teams in Multiple Time Zones!

    Few years ago, Luke Hohmann, Conteneo's CEO, was helping with a large scale enterprise Agile Transformation project lead...

    Agile Innovation Strategy safety diversity and inclusion

    Anonymous Participation: Collaborating Safely on Sensitive Topics

    We have released fully anonymous participation for  organizations that need to increase safety when tackling sensitive t...