Over the course of several sprints, the scrum team will deliver pieces of work that support the overall epic of a website that makes it possible for customers to browse and buy pajamas, to use a digital payment like Apple Pay or Google Wallet, and to ensure reactive features on multiple devices. Later sprintable PBIs might involve activating specific plugins that provide different aspects of the functionality, including testing to ensure it works. These stories might be used to frame the first sprintable PBI: evaluate existing platforms to see which best provides the desired functionality. The interface epic might be viewed through a series of stories about the ways that potential users might interact with the website. This project might be broken down into three epics: designing the website, developing the interface, and creating the content. Let's consider in more detail the example of using epics to conceptualize the project of an eCommerce website. Supplying the elements necessary to fulfill the user stories creates the work in the product backlog. They may speak generally or specifically about the functionality they desire from the product, and often the stories are codified in the acceptance criteria.Įach product backlog item or user story expresses an element that must be completed to achieve the full epic. A PBI or user story might be something like, "Shoppers should be able to browse pajama pants by color, material, theme, price, and size." The epic above it may be "pajama eCommerce website.”Ĭustomers, product owners, and stakeholders are often the source of stories. To create that level of granularity, a team may break the epic into individual user stories (or PBIs).Ĭonsider the example of an eCommerce website. Why Are User Stories or Epic Sub-Items Necessary?īecause an epic is a broad, high-level, flexible tool, it doesn't necessarily depict how individual users will interact with your product or service. Scrum teams who use epics may express the smaller work pieces as product backlog items. User stories are arguably the most traditional way to break the large epic into smaller pieces, although not the only way. 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 |