Are components still useful in GreenHopper's new-ish Scrum boards? Are epics the new way to go?

[Deleted user]

I've been going through the documentation on components, and it seems that GreenHopper is shying away from components to focus on epics. Am I right in saying that?

[J · Accepted solution]

Hi Chris,

It's true that both components and epics are ways to relate stories. A component was always meant to provide a way to provide structure below the level of a project. If you create a bug, its useful to know that it's related to the Confluence Editor, for example. Components tend to have long lifespans. Epics are meant to provide structure within the story development hierarchy, and as a way to help think about big stories that devolve into smaller stories. Epics can be completed, components typically don't. The epic reporting we are developing reflects this as well.

We use components to relate stories and bugs concerned with functional areas of the product, and epics to talk about feature work. Make sense?

[Timothy]

In the new boards, the focus is based on Scrum methodologies. So yea, Epics are the way to go but the Component field is still there for you to use.