Back

Epics and Personas – Part 1

Developing Epics

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.

How to Use Epics

The use of epics is very helpful to the Product Owner because it means that they can describe and note down the high-level functionality of the user story, but they do not have to dive into the detail yet. The Product Owner will initially use the epic as a container to broadly capture the requirement and will add this as an item in the Product Backlog. It acts as a placeholder until it is turned into a group of fully formed user stories at a later stage.

Epics will always be placed lower down in priority in the Product Backlog by the Product Owner. The reason for this is that, as soon as they become high priority items, the first step will be to break the epic down into user stories that are of a size that can be delivered within a sprint. Because of this, the Product Backlog is sometimes referred to as having the shape of an iceberg, with the larger epics at the bottom and the most granular and well-refined stories at the top. Both epics and user stories can be divided up into smaller pieces of work, and this hierarchy can be stretched to whatever level is necessary and makes sense. In other words, larger epics can be split into smaller epics, and these are then split into stories, which can be further refined into smaller stories, and so on.

59 Seconds Training Video

Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)

Introductory Offer: Free Course

Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)

What is this course?

This ‘Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Tester roles and responsibilities

You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’

This course is aimed at those with or without prior knowledge and experience of the Agile values and principles

During this course you will learn the tools needed to succeed as an Agile Scrum Tester

What will you learn?

You will gain an in-depth understanding of the Agile Scrum Tester roles and responsibilities, and you will be able to

  • Fully understand the role of the Agile Scrum Tester
  • Understand the roles involved in an Agile project
  • Create an effective Product Backlog
  • Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
  • Identify the roles involves in the Scrum Team
  • Fully understand the role of the Agile Scrum Developer
  • Understand the roles involved in an Agile project
  • Create an effective Product Backlog
  • Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
  • Identify the roles involves in the Scrum Team

What topics are covered within this course

You will cover the following topics during this course:

  1. An Introduction to Agile Project Management (Tester)
  2. The 12 Agile Principles (Tester)
  3. Introduction to Scrum (Tester)
  4. Scrum Projects (Tester)
  5. Scrum Project Roles (Tester)
  6. Quality in Agile (Tester)
  7. Acceptance Criteria and the Prioritised Product Backlog (Tester)
  8. Quality Management in Scrum (Tester)
  9. Epics and Personas (Tester)
  10. Planning in Scrum (Tester)
  11. Scrum Boards (Tester)
  12. User Stories (Tester)
  13. The Daily Scrum (Tester)
  14. The Product Backlog (Tester)
  15. Review and Retrospective (Tester)
  16. Validating a Sprint (Tester)

Our Book Recommendations

We found these books great for finding out more information on Agile Scrum:

Translate »