Kevin is a Product Owner for a retail organization. The Product Backlog for his immense marketing tool project has 200 Product Backlog Items.
Into what should he group the smaller Stories together?
Kevin is a Product Owner for a retail organization. The Product Backlog for his immense marketing tool project has 200 Product Backlog Items.
Into what should he group the smaller Stories together?
When dealing with a large number of Product Backlog Items, such as 200, it is practical to group smaller stories into Epics. An Epic is a large body of work that can be broken down into smaller stories or tasks. This helps manage and prioritize the workload more effectively, as it organizes the backlog into larger, more manageable chunks. Grouping smaller stories into Epics allows the Product Owner to handle the backlog efficiently without getting overwhelmed by the sheer volume of individual items.
Themes
If there are more than 100 items on the Product Backlog, you should combine detailed low-priority items into Epics. To create a roadmap, it would require that you group even high-level requirements into themes and use these as a guideline to create a roadmap.
Answer is A correct . EPICS
I agree with Lulumellow and foxpo7 according to the Scrum. According to the "EXIN-Handbook for Scrum Masters and Product Owners": You can start a product backlog with as few as four and five course-grained user stories (Epics), and then decompose these in order of priority, with each iteration done. ... It is advisable to stick to the 100-item rule, and as soon as you see this number going up, see which items can be dropped from the backlog. Go through the exercise again to combine detailed low-priority items into Epics...