Timeline for How should I deal with common dependencies when estimating stories in Scrum?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 9, 2021 at 21:43 | comment | added | Thomas Owens♦ | @Daniel I cleaned up the answer a bit. All Product Backlog Items should have value. However, they may be directly valuable to different people. The Product Owner should be in a position to make decisions about technical work and how certain pieces of technical work can help the team improve the delivery of work that is directly valuable to stakeholders outside of the development team. As far as dependencies, if you are delivering thin slices of work, then you shouldn't get stuck in a position of a large amount of work that isn't directly valuable to users or customers. | |
| Oct 9, 2021 at 21:41 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 194 characters in body
|
| Oct 9, 2021 at 9:08 | comment | added | Daniel | If Product Backlog Items were not defined in terms of value, than how would Product Owner prioritize it? You would often have to explain dependecies and tech tasks to them and this becomes really similar to PMBoK, dependencies and critical paths, etc. A tech task in turn may have many other tech tasks as depencies that need to be done first, so you will end up not delivering any value for Product Owner for a long time. It does't look like Scrum or Agile... | |
| Dec 11, 2020 at 12:44 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |