Chronicles of a Scrum master #8 : Epics and Release management

What are epics in an agile context ? Epics group or categorize stories into release features. It plays an important role in the organization and release of features for the product.

For example, an Epic of “Login based on country” can use to group stories as following :

  1. Develop splash page with login User ID textbox and Login button.
  2. Login to verify User ID and match against correct password.
  3. Display after login landing page based on user country.

Above is just a simple example. There are more complicated ones.

Source :

Epics also serve as a guide for code branches and releases. A code branch can be based on an Epic (feature) and a release can contain multiple Epics. Taking into example above, there could be another epic “Display landing page” with break down of stories :

  1. Create and display banner
  2. Display list of products
  3. Display vouchers
  4. Display menu bar

The code branches are advised to follow by epic level so that it can be independent from each other and deployed without dependency on prior completed stories. This will allow the release of next stories if prior completed ones are not ready to be deployed.

It is an important point to take note of because a product that has already gone live and being used by users may have fixes and enhancements on existing functions. The proper naming of the epic and tagging of stories allows a clear understanding of separation between BAU bug fixes or defects and New features (enhancements).

An example of this would be the following :

  1. BAU bugfixes or defects :
    1. Bugfix / defect – Login unable to work when clicked on button.
  2. New features :
    1. Enhancement – Login to support multi-language

Source :

Disclaimer: What I am sharing is purely from my point of view and does not reflect anyone else’s. What I present in my posts doesn’t necessarily mean tat it is applicable to your work, organization and culture. Would love to hear from you if you have any different opinions or feedback. 

Agile Scrum master

Chronicles of a Scrum master #20 : The end of a journey and the start of another

Being a scrum master for the past few years, I am extremely grateful to be given the opportunity to guide, educate and motivate several product teams. This has allowed me to be a better servant leader. In my previous journey, as a first time line manager with direct reports, there were long hours and many […]

Read More
Agile Scrum master

Chronicles of a Scrum master #19 : User stories guide to better development and further refinement

In the world of agile, requirements come in the form of user stories and it is important to understand that the details contained in the stories are needed to absolute clarity for anyone who is going to be working to get this stories done. Consequently, here are several practices which can be adapted to organizations […]

Read More
Agile Scrum master

Chronicles of a Scrum master #18 : Measuring agile

Agile development is fundamentally about the delivery of value to customer via a iterative and incremental process. This value can be a perceived or tangible value, depending on what the end goal is. Hence, in order to measure the success of an Agile project or product, it is imperative to establish the objectives and end […]

Read More