Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
User stories are used with Agile software development methodologies as the basis for defining the functions a business system must provide, and to facilitate requirements management. It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper notecard
3
votes
Do multiple levels of epics make sense?
There exists an additional, often-used, term that can help you here: themes. Themes are collections of stories with a common theme (thus the name).
So you could organise your epics thus:
Epic "As a …
2
votes
Is my "Personal Contact Information" theme broken down properly?
I'm going to disagree with the other two answers here and say: no, your approach is not valid. Consider the simple use case of a contact that doesn't have a home phone, just a mobile one. They are goi …