Developing Epics for Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single business process that must be fully completed as a whole for the business value to be realized. These user stories are described as epics because they will require refining over multiple cycles before they can be considered done.

Defining epics and scheduling them into a release plan is an effective way to manage the product backlog. Part of identifying what epics can be made for the project requires an understanding of the granularity of backlog items. Scrum masters can help the product owner and the development team in defining and planning of Epics by letting them understand what epics are and how they can be broken down into user stories.

Collecting Content for the Product Backlog

The product backlog consists of requirements that come from conversing with the stakeholders. Some ways that can be used to collect such content could be the following:

1. Workshops – Meetings and sessions where the team empathizes with a group of customers and users by having them present problem areas and solutions to each other. This can be done by writing them down on post-its, grouping them together, and later on processing next steps.
2. Interviews – Up close conversations with individuals that have more personal statements, which can lead to useful and unique insights for the product.
3. Questionnaires – Surveys that are accessible to various users and customers and can be answered at their own convenience. Results can be more quantitative in nature since trends and patterns can be found based on the answers.

Collecting Content for the Product Backlog

Analyzing results from workshops, interviews, and questionnaires will help the team come up with personas who represent user groups for the product. Designing the product around personas helps ensure that the developed product is valuable by addressing the problems and preferences raised by users.

59 Seconds Agile - Developing Epics

59 Seconds Agile – Developing Epics

Breaking Down the Product Backlog

One could think of the product backlog as a large repository of work that can be divided into smaller and smaller parts. There’s the overarching statement of what the product is, broken down into what its objectives are, and then further split into what functionalities it has.

The granularity of a feature will vary from one organization to the other. Some organizations use themes or value streams to group features together. Some organizations come up with epics that cover different focus areas, and then map user stories that complete these epics. The Scrum team and the stakeholders need to work together on deciding how to categorize user stories into epics and epics into themes.

User Stories

User stories note the agreements between the stakeholders and the Scrum team and detail what actions need to take place within the product. A popular template used for writing user stories are:

As a (type of user), I want to (action here) so that (reason or intended output here).

This statement encapsulates what the Scrum team needs to cover when developing the product: who the user is, what they want to do, and why they want to do it, as well as the value it will give to them.

INVEST Criteria

The INVEST criteria guides Scrum teams into coming up with good user stories, and it stands for the following:

Independent – Story is not redundant and provides enough detail as it is.
Negotiable – Story can be discussed and is eventually negotiated.
Valuable – Story is important to the customer.
Estimable – Story has an approximate range along which it can be estimated.
Small – Story fits within an iteration.
Testable – Story is clear enough to be tested.

Following the INVEST criteria helps the team practice exchanging feedback, estimating effort, and implementing features with sufficient understanding.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Scrum Master?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Scrum Masters

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Scrum Masters

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Scrum Masters

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Scrum Masters

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Scrum Masters

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Scrum Masters

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Scrum Masters

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Scrum Masters

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Scrum Masters

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Scrum Masters

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Scrum Masters

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Scrum Masters

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Scrum Masters

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Scrum Masters

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Scrum Masters

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Scrum Masters

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Scrum Masters

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Scrum Masters

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Scrum Masters

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Scrum Masters

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More

Developers

Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Share
Translate »