As my scrum team prepares backlog makeup, we usually begin with epic level work, and those Refine PBI in themes and stories. As part of general beauty activities, as a means of structuring these work items, PBI has been created as a hair link for larger items as a result of refining and clarifying the other PBI. We apply this process only by specifying the stories of Scorpio for sprints, while leaving the original subject PBI in the current relocation.
We are gradually increasing in the facilities provided in 2012 after the upgrade in the beginning of this year, and in the product backlog view in web access (rather than manual manually values) The ability to draw objects is very attractive.
We want to use it, but there is a problem: PBS with our parents' relationship, as most of our plans are expressed, expressed The last form can not Gsi. Instead, each epic product appears in a backlog as a tree, in which its children have a priority limit of [1..1000000], and it emerges from an atomic form.
Keeping this in mind, how should this work? Am I missing something about the features of the product backlog scene? Do we intend to destroy our epics and subjects because they become sophisticated in small PBI so that the stories can be determined independently?
We are struggling with the same type of issue. We decided to remove epics and used only stories. Then we tag each PBI with an epic name so that we can easily search and group objects, when there is actually no better option yet available.
No comments:
Post a Comment