How can I create an Epic based on requirements following best practices?



  • I am trying to learn Kanban and Scrum and for that, I have a sample mobile app for the gym in mind with the following ideas:

    • User should be able to create a workout plan.

    • User should be able to create a diet plan to follow

    • The app should cater to different types of users with assisting them with workout videos and how to use equipment.

    • User should be able to book search and find a trainer for training

    • User should be allowed to book an specialised equipment and locker to avoid waiting.

    • User should be able to join special programs like yoga and Zumba classes.

    Now here I am confused with what should be my Epic and how to associate my user story with an Epic.

    What are some samples of what should be my Epic and user stories following the above requirements/features? Why have they created Epic in that way?

    Note: I am not asking how to create an Epic in any tool. I am asking how to come up with valid Epics which makes sense according to the requirements/features.



  • There are two schools of thought about what an Epic is.

    Some define an Epic as a large user story, often one that cannot be delivered in a single iteration. However, it can be placed and ordered in a Product Backlog and then be refined by the team when it comes up. The refinement activity will decompose the Epic into a number of User Stories, each of which typically meets the INVEST criteria.

    Others define an Epic as a container for related user stories (and sometimes other work). In this case, the Epic may be the deliverable that ultimately adds value for one or more stakeholders and is what is tracked to completion.

    Using your example of a gym mobile app, you can find some examples.

    If you treat the Epic as a large user story, you may simply define one of the Epics as "User should be able to join special programs". This may be decomposed into user stories regarding registration, login, searching for classes, and enrolling in a class.

    If you treat the Epic as a container for related stories, there are any number of ways to group them. For example, there could be an "Equipment Usage" Epic that contains user stories about displaying workout video and booking equipment. These user stories could be delivered independently and add value to one or more stakeholders, but someone may be interested in organizing and tracking the body of work associated with helping people use equipment.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2