-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
epic label ? #35
Comments
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 ? |
@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. |
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? 🤔 |
@iteles how do you refer to a "bigger issue" in projects if not as an |
@iteles - now that this label has been made can we close this issue? |
👍 |
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?
The text was updated successfully, but these errors were encountered: