The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.


Scrum Epics

Posted by admin under Scrum Basics

In Scrum, the teams that complete the work spend time refining the top items in the Product Backlog. To minimize work in progress, user stories shouldn’t consume more than one quarter of a Sprint. In most cases they can be made much smaller than that while still providing visible value to the customer.

What happens when a story includes too many unknowns to tell just how big it is? Or what if the story’s requirements are known, but its effort is too huge to complete in a single sprint? We call these stories “epics.” If an item require more than a quarter of a Sprint to complete, it’s probably an epic.

Estimating epics can be harmful because it creates a false sense of certainty. Instead, they should be split, as illustrated in this video.


Watch a team split epics during a Backlog Grooming Meeting.


Be Sociable, Share!
Comments Feed

Reader's Comments

  1. Scrum Estimating Experiences « Sputnik Coding |

    […] team also has a backlog that is proving difficult to estimate as the features are more Epics than Stories. This is being addresses by the PO. However, questions are being raised as to how to […]

  2. VersaPay Development Flow | VersaPay |

    […] quarterly plans. The “big” features we want to implement in a quarter are stored in Epics. The Product Manager takes care of […]

  3. The Coming Culture Storm « CLAR[IT]Y |

    […] software. You sit down with the end-users and gather stories about how they do work and craft epics out of them. The agreements for how work will be done made in those meetings will be reified within […]

  4. Scrum in Marketing – The Backlog | Mobility Journey |

    […] use the uber-backlog to stick everything we know we need to do at some point in the future. We use Epics for big or fuzzy thing like “Develop a New Website”, “Launch product XYZ” […]

  5. Sebastian Bonelli |

    This video explains how to conduct a productive backlog grooming sessions could help product manager to dive-in, further breakdown feature in needed detail and prioritize. Thanks!

Leave a Reply