In VS2010 Scrum 1.0 project template, can I create a PBI that has child PBIs? If not, what is a good alternative for large user stories aka product backlog items?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In VS2010 Scrum 1.0 project template, can I create a PBI that has child PBIs? If not, what is a good alternative for large user stories aka product backlog items?
The short and simple answer is yes. You can create a child PBI. Quite simply, under the Links tab, you add a new (or link to an existing) PBI work item.
The greater question is: Why do it?
Strictly speaking, from a Scrum point of view, you shouldn’t have hierarchy in your user stories. The stories, as Mike Cohn (I believe) put it, you should INVEST in good stories. The ‘I’ stands for independent, which a story can’t be if it is the child of another.
The only “Scrum-appropriate” reason to introduce a hierarchy is when you’re breaking down a large story into small workable stories, or (rarely) molding to overly-small stories into one story of reasonable size.
Assaf.