From Mike Cohn’s fantastic blog at Mountain Goat Software.
User stories often are deliberately vague at first. If work won’t begin on a story for a couple of iterations, agile teams have learned there is little value in adding detail to the story so far in advance.
But the time comes in the life of any user story when adding detail is appropriate. And there are two ways a team can add detail to a user story: split it or add acceptance criteria. Let’s look more closely at both methods. Read More