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

Deleted user March 5, 2013

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?

2 answers

1 accepted

4 votes
Answer accepted
J
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 5, 2013

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?

2 votes
Timothy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 5, 2013

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events