3 ms·
Sometimes it can. Sometimes teams plan based on "How long does it take to implement these use cases?" Other times (more frequently in agile) it's "How many us
by mathattack 10y ago
Sometimes it can. Sometimes teams plan based on "How long does it take to implement these use cases?" Other times (more frequently in agile) it's "How many use cases can we get by date X?"
It's harder to commit to the first scenario than the 2nd, since the 2nd (in practice) implies that the date transcends scope so you can take items out.
- pdimitar 10y agoIn my 15 years of commercial practice, I feel that your 2nd scenario very rarely translates well to reality: most of the times you need to put some foundations in the code that would allow features A, B, C, D and E. Even if your Scrum Master is liberal and tells you "OK man, we don't have much time, put features A and B only", this doesn't change the fact that often times the initial overhead of all 5 features takes the most time. Outside of that, I definitely am in agreement with you.
- mathattack 10y agoI think we're on the same page. The world isn't black and white. It's a matter of accepting which constraint (scope, quality, timeline) is the dominant one.