Embedded Files
This is a reference resource intended to be linked to in order to provide a visual summary. This is not intended to introduce the concept as a standalone article.
Interactive. Click or Swipe Left to proceed.
Each of these slides have been designed to encapsulate a specific aspect of the hierarchical product definition / specification, and can be viewed here:
Feel free to link to any of these posters from your documentation.
It's worth clarifying...
It's worth clarifying...
Epics should really come in to existence, at least most of the time, from a top down decomposition.
Many teams use epics to group together a bunch of related user stories rather than starting with the epic and decomposing it. The problem with this is that the epic tells us nothing more than the individual stories it contains. And, if the stories are created and refined just in time for a Sprint, the epic doesn't fulfil it's purpose of providing clarity about what we're aiming to achieve in the near future.
Page updated
Google Sites
Report abuse