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

Submitted by admin on Wed, 12/03/2008 - 09:02
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. http://www.youtube.com/watch?v=b_WeHcZcx1w  
Category

Comments

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!

When going from scratch to gather requirements, what is the first level of documentation? Is that an EPIC? Is there a project charter? Is the correct progression EPIC--> User story --> Theme? Thanks.

Add new comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.