Have a row for 'orphaned' SBIs


Have SBIs that are not associated with any PBI be displayed on the dashboard in a special row.
see Mike Cohn post on this subject at http://blog.mountaingoatsoftware.com/?p=28


perb wrote May 29, 2008 at 7:01 PM

Ok, do you suggest having a row for actual orphaned SBIs (without a valid PBI-link in TFS) ? Or what Mike talks about which are those special PBIs (we create them for every sprint Story->Create Product Backlog in Scrum Dashboard) ?

wrote May 29, 2008 at 7:04 PM

alexvaccaro wrote May 30, 2008 at 8:27 AM

Hi perb,

I was interpreting "storyless = orphaned" but I see what you mean, I could create a 'Miscellaneous' and a 'Bugs' PBIs and then use those as my special rows. I must say I would prefer not having to create PBIs that don't have a clear business value. I think I could live with a PBI like 'Fix High Priority Bugs' for example, but I am very reluctant to have a 'Miscellaneous' PBI because it has no clear purpose.

Another benefit I would see in having a special 'orphaned' row is that it could help me identifying mismatched SBIs.

wrote Aug 25, 2008 at 6:05 PM

dzirkler wrote Aug 25, 2008 at 6:06 PM

I would like to see just a separate line for all SBIs that do not have an associated PBI for the sprint. The problem we have is that there are technical requirements ("Fix build script due to XXXX") that are not associated with a PBI. These are simply being left off of the dashboard and are not displayed anywhere, and are sometimes forgotten.

perb wrote Aug 26, 2008 at 6:38 PM

I'll try to add it for the next release if I can allocate the time.

alexvaccaro wrote Aug 27, 2008 at 12:35 PM

Another approach would be to implement Item #2444 'Display SBIs for current sprint even if PBI is set on another sprint'.

Currently if I am viewing the dashboard of sprint 2 and I have a PBI iteration path set to sprint 1 with a child SBI iteration path set to sprint 2, both the PBI & the SBI will not be displayed on the dashboard; if I change the view to sprint 1 I will see the PBI but not the SBI.
This is because the list of PBIs populated on the LHS is driven by them matching the sprint selected at the top of the dashboard. If instead the list of PBIs gets populated by the SBIs matching the currently selected sprint it would be possible to create a 'dummy' PBI as you suggested in your earlier comment and just create SBIs for general tasks against it.

perb wrote Aug 27, 2008 at 1:33 PM

Oh, that would be a smart approach.

dzirkler wrote Oct 22, 2008 at 3:11 PM

For me, the value is in SBIs who do not have a PBI associated with them.

wrote Apr 2, 2009 at 5:59 PM

wrote Jul 2, 2009 at 2:07 AM

wrote Dec 14, 2009 at 3:25 PM

wrote Feb 21, 2013 at 10:42 PM