Skip to main content
9 events
when toggle format what by license comment
Oct 30, 2013 at 9:14 vote accept whyAto8
Oct 30, 2013 at 9:14
Oct 30, 2013 at 9:13 comment added whyAto8 @AshokRamachandran - Thanks, this is helpful. I understand it now.
Oct 30, 2013 at 0:37 comment added jmort253 @AshokRamachandran - I feel like stories can always be broken down into smaller components. The paypal example in the link highlights that well.
Oct 29, 2013 at 22:36 comment added Todd A. Jacobs @jmort253 Good question! Yes. Epics are often useful for estimating entire backlogs or roughing out release schedules, but must be broken down sufficiently for accurate per-iteration planning. As Ashok mentioned, this is often done during Backlog Grooming or Sprint Planning. It also falls under the Negotiable mnemonic from the INVEST acronym.
Oct 29, 2013 at 20:22 comment added Ashok Ramachandran @whyAto8 In my experience larger stories are not as well understood by the team and are high risk. All you know is it is larger than a 20 and smaller than a 100. That is too wide a range for making a team commitment to completing in the sprint. If this story is not completed, your velocity may drop drastically impacting team morale and leadership perception. Try some of the suggestions here to split larger user stories.
Oct 29, 2013 at 20:11 comment added Ashok Ramachandran @jmort253 Yes, it is.
Oct 29, 2013 at 17:39 comment added whyAto8 What if the team has identified the story has a effort of 40 and it has to go in next sprint? And this can not be broken as well into smaller one's? Would having 40 be okay and are there any disadvantages of having 40?
Oct 29, 2013 at 17:36 comment added jmort253 Is this because the stories at the top of the backlog have been broken down into smaller stories?
Oct 29, 2013 at 17:30 history answered Ashok Ramachandran CC BY-SA 3.0