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 estimation
Search options not deleted
user 16148
For questions about the estimation of the project's parameters, such as time or cost.
-1
votes
Should user stories be estimated by efforts or by value it added?
The purpose of story points are to give the team the capability to forecast and provide projections in regards to their ability to deliver software in a given time frame. Many things are factored int …
- 560
2
votes
Should we create multiple stories for same thing to be replicated at code level?
What you've created is technical debt, and it needs to be refactored.
Do not create duplicate stories, and try not to duplicate code as you just end up paying for things multiple times. A user stor …
- 560
0
votes
What could be potential harm of giving points to chores or technical debts?
I do not see an issue accounting for all tasks/user stories, bugs, technical spikes, refactors, etc., as over time it allows the team to better understand capacity, and you can do a bit more analysis …
- 560
1
vote
Do you include testing in the original estimate?
Quick answer: YES
Always factor ALL the effort your team will need to commit towards a story or piece of work, regardless of the estimation technique used. …
- 560