Sometimes stories have some dependencies on other stories. It's easy to put cross-references in to card descriptions, so have people done this generally just by having a standard section in story cards that says 'blocked by' and leave it at that?
What's a good way to set up 'blocking' stories?
Comments
2 comments
Chris
There is an example using a property of type card called "depend on' in the Scrum template. This is used to link cards together via properties and is used in the "Dependency Chart" at the bottom of the overview page. This chart helps to give insight into which cards are blocking other cards.
Thanks
- Suzie
Chris,
One thing that I've done is to create a Story card Property called "Blocked by", of type Card. Then for each applicable Transition, I set the "Blocked by" property to "Not Set" in the begining state. Thus, if this property is set, the dev. engineer can quickly determine what is blocking them. If it's not set, the state change is allowed.
This type of "Not set" precondition should work for most types of card properties.
I've attached a pic of the transition.
Regards,
Tim
Please sign in to leave a comment.