Timeline for Should sprint backlog have MoSCoW prioritization applied?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2015 at 22:40 | comment | added | David | I see your point, @doug. here is a question I posed for people to address that specific issue of completing a project after the "must haves" are complete. | |
| Jul 9, 2015 at 12:13 | comment | added | Doug B | @David - My perspective is that if you wait to ask "are we done?" until you are pushing up against your budget or schedule you aren't taking advantage of every opportunity to finish early or under budget. Personally, if there is an option to finish under budget/ahead of schedule, but with consequences to non-necessary scope items, I feel obligated to lay that option out. | |
| S Jul 9, 2015 at 12:04 | history | suggested | David | CC BY-SA 3.0 |
Refined a good answer with clear reference to product and sprint backlogs, and product backlog refinement meetings.
|
| Jul 9, 2015 at 7:52 | comment | added | David | I like your answer, and suggest the reference to product backlog refinement meetings as a clarification. I am not convinced that one needs to be asking the business (product?) owner if he considers the project complete at each sprint after the "must haves" are done. Maybe such would be the case only if the team was getting close to some budget/time constraints. I did not, however, suggest editing that, as it didn't seem my place to do so. | |
| Jul 9, 2015 at 7:49 | review | Suggested edits | |||
| S Jul 9, 2015 at 12:04 | |||||
| Jul 8, 2015 at 12:35 | history | answered | Doug B | CC BY-SA 3.0 |