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 | |
Results tagged with specification
Search options answers only
not deleted
user 36330
1
vote
Technical Spec: Is more detail help or hindrance?
A lot depends on a team's ways of working but relying on evidence-based results rather than detailed specification often makes better use of a team's collective problem-solving ability. …
- 6,345
2
votes
Is the client or vendor responsible for writing the BRD?
The team as a whole (developers and client) should take responsibility for creating any documentation. It's a collaborative effort and to maximise productivity the team should try to avoid having unne …
- 6,345
1
vote
How do we prevent debates over whether changes to user stories are new work or bugs?
Document as much detail as you need to get the work done, which should normally include sufficient documentation for future support but not necessarily to complete further stories or defect fixes.
I b …
- 6,345