Developing Epics for Developers

Epics and personas are an important part of Agile software development. They allow the Scrum team to get into the heads of the user, and know the intended use of the product. The product owner typically creates the epics and personas. However, the developer role still has an interest in the creation of epics and personas, as they benefit from having well-written epics and personas in a project.

What is an Epic?

In the context of Agile software development, an Epic is basically a large user story. A user story is a task that an average user would want to accomplish in a software product. If a product contains a database of people, a user story might be to access and edit the information of one person. An epic for this product may be to send a mailer to any person in the database with an address listed. The epic clearly involves more steps, and more code development, than the user story.

Scrum teams make a distinction between user stories and epics because of the difference in development time. A typical user story can be finished within a single sprint. An epic, however, might take multiple sprints to finish. Because of this, the Scrum team will usually break up epics into multiple user stories. Even if the whole epic isn’t finished in a single sprint, each sprint gives more functionality to the stakeholders. Eventually, stakeholders will receive all the functionality required to complete the epic.

Despite their size, epics are typically treated the same as other user stories. They are prioritized into the backlog in the same way. The Scrum team works on them as they would any other functionality. The biggest difference is simply that epics are too large to fit into one sprint. This changes the way that the Scrum team must break them apart.

Epics and personas are an important part of Agile software development. They allow the Scrum team to get into the heads of the user and know the intended use of the product. The product owner typically creates the epics and personas. However, the developer role still has an interest in the creation of epics and personas, as they benefit from having well-written epics and personas in a project.

What is an Epic?

In the context of Agile software development, an Epic is basically a large user story. A user story is a task that an average user would want to accomplish in a software product. If a product contains a database of people, a user story might be to access and edit the information of one person. An epic for this product may be to send a mailer to any person in the database with an address listed. The epic clearly involves more steps, and more code development, than the user story.

Scrum teams make a distinction between user stories and epics because of the difference in development time. A typical user story can be finished within a single sprint. An epic, however, might take multiple sprints to finish. Because of this, the Scrum team will usually break up epics into multiple user stories. Even if the whole epic isn’t finished in a single sprint, each sprint gives more functionality to the stakeholders. Eventually, stakeholders will receive all the functionality required to complete the epic.

Despite their size, epics are typically treated the same as other user stories. They are prioritized into the backlog in the same way. The Scrum team works on them as they would any other functionality. The biggest difference is simply that epics are too large to fit into one sprint. This changes the way that the Scrum team must break them apart.

<– Continue Reading –>

Our Book Recommendations

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

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

Introductory Offer: Free Course

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

What is this course?

This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer 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 Developer

What will you learn?

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

  • 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 (Developer)
  2. The 12 Agile Principles (Developer)
  3. Introduction to Scrum (Developer)
  4. Scrum Project Roles (Developer)
  5. The Agile Project Life-cycle (Developer)
  6. Acceptance Criteria and the Prioritised Product Backlog (Developer)
  7. Initiating an Agile Project (Developer)
  8. Forming the Scrum Team (Developer)
  9. Epics and Personas (Developer)
  10. User Stories and Tasks (Developer)
  11. Implementation of Scrum (Developer)
  12. The Daily Scrum (Developer)
  13. The Product Backlog (Developer)
  14. Scrum Charts (Developer)
  15. Review and Retrospective (Developer)
  16. Validating a Sprint (Developer)
  17. Retrospective Sprint (Developer)
  18. Releasing the Product (Developer)
  19. The Communication Plan (Developer)
  20. Formal Business Sign-off (Developer)