From b711c7a453e02594e279b774867d2181883d133d Mon Sep 17 00:00:00 2001 From: Jonathan Lam Date: Wed, 5 Dec 2018 20:27:55 -0800 Subject: [PATCH] Adding more information to agile epics (#24016) --- guide/english/agile/epics/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/english/agile/epics/index.md b/guide/english/agile/epics/index.md index 68858fe70a..9b708d7f87 100644 --- a/guide/english/agile/epics/index.md +++ b/guide/english/agile/epics/index.md @@ -2,7 +2,7 @@ title: Epics --- ## Epics -An epic is a large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories. Epics usually cover a particular persona and give an overall idea of what is important to the user. An epic can be further broken down into various user stories that show individual tasks that a persona/user would like to perform. +An epic is a large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories. Epics can help teams break their work down, while continuing to work towards a bigger goal. Epics usually cover a particular persona and give an overall idea of what is important to the user. An epic can be further broken down into various user stories that show individual tasks that a persona/user would like to perform. This can help the team organize their work and to create a hierarchy. This way, large projects can actually get completed and the team can continue to ship value to the customers on a regular basis. There is no standard form to represent epics. Some teams use the familiar user story formats (As A, I want, So That or In Order To, As A, I want) while other teams represent the epics with a short phrase.