Reputation
211
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 4
Newest
 Nice Answer
Impact
~868 people reached

  • 0 posts edited
  • 0 helpful flags
  • 27 votes cast
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
We've had some of this at the beginning, but we've found that it helps if we move the Grooming and UI work as close as possible to the Sprint where it should be implemented. The main item for me is that the preparatory work (like mockups or wire frames) has to be done before development starts to estimate the story, since we've seen all kinds of surprises if we don't do that. We've had stories that looked really simple when estimated, but then we received a mockup that was really complex. Having the UI work done as a prerequisite helped us resolve this issue.
Apr
4
comment Do your stories include tasks across disciplines? How do you do capacity planning?
I completely agree. It's an option, but it might not be a good one, due to the dependencies between these stories and the arguments you mentioned. Like I said in my post, the second approach is what we're using, where we treat the UI work as required input for the story to be "ready".