epic label ?

[nelsonic]

When a "Story" is actually a larger collection of features that can/should be sub-divided, the overarching story is referred to as an "Epic". see:
https://www.scrumalliance.org/community/spotlight/mike-cohn/march-2014/agile-user-stories-epics-and-themes
The question is: how do we label this kind of issue in a GitHub Backlog...?

we needed a way to designate an "Epic" today: https://github.com/o2tank/setup/issues/17#issuecomment-253814070

@iteles thoughts?

[nelsonic]

@iteles / @jrans / @des-des has the use of the Epic label for the "ART" project been successful? (does it help to organise the project into related features/themes which are then split out into smaller stories)

[iteles]

This hasn't actually been successful but that's mostly because our Product Owner was a little too busy so a lot of these epics were initial placeholders that were never filled in or updated so they have become disused.

We use this much more sporadically on OA and whereas I have found them useful personally, but I don't think the developers use them. They will come into play a lot more in the next stage where there are 5 or 6 big topics to tackle.

I think this one needs more time before making it into 'core'.

Thoughts @naazy @Conorc1000 @roryc89 ?

[des-des]

@nelsonic I agree with @iteles on art. I think Having a set of top level issues could be useful for a big project though.

[jrans]

@nelsonic If done right it can be but its hard to draw a line at whats epic plus no real use to developer as concentrating on smaller issues and more for managing things in longer term. No real use filtering by it too while milestones more helpful.

[nelsonic]

Ok. so what I should have asked was: how do we inform a PO that the story they have just written is actually several stories and it should therefore be split out accordingly? 🤔

[nelsonic]

@iteles how do you refer to a "bigger issue" in projects if not as an epic ...?
(all projects that aren't hackathons or 2-week MVPs are "big" by definition and thus require an over-arching issue - AKA epic - which is then broken down into user-stories)

[iteles]

Like I said, I use epic as a label across the various projects and I've seen two sets of developers use them in the last week (correctly). It's time:

I use a deep deep blue for epics because I feel like it gives them some weight and substance without making them depressing (black).

[iteles]

https://github.com/dwyl/labels/blame/18039e87ef897d40f85454735f320828ac11331c/README.md#L73

[Cleop]

@iteles - now that this label has been made can we close this issue?

[iteles]

👍