![]() Like the chapters in a book, user stories are nested within epics and ultimately make the epic what it is. On the other hand, your work may have been in vain if the team took on the whole epic at once, only to find out changes have made the epic obsolete in the end. When they need a change, you’re able to adapt the plan easily. Instead of taking on the whole epic at once with a deadline in a few months, you and your teammates deliver small increments of value to your customers, users, or stakeholders each sprint. It provides direction without a ton of investment in its plans and details. As conditions or customer requirements change over time, these smaller pieces can be modified, removed, or added to a team’s product backlog with each sprint. Your team may call these smaller pieces product backlog items, user stories, issues, or something else. Here’s what that means: The epic is broken down into smaller pieces of work. How an Epic Supports Continuous Value Delivery An epic is typically completed over the course of several sprints or longer. An epic is too large to be completed in a scrum team’s sprint (or agile team’s iteration) but is a smaller representation of work than the highest-level goals and initiatives. In a hierarchy of work, an epic comes from a higher-level theme, business goal, or initiative. It's a description of a large, high-level piece of work for your team. Think of epics as an optional tool - containers that break work down into elements the scrum team can tackle one sprint at a time.Īn epic is a work management tool. While epics can be an effective way to create structure and hierarchy in the product goals before you, using them is not a part of scrum formally. The sub-folders are product backlog items (PBIs), user stories, or another representation of smaller pieces of work based on the epic. Or, picture it this way: an epic is like a large folder that contains many sub-folders. An epic is a large, high-level piece of work that is too big to be completed in a single work iteration or sprint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |