Loading ...
Sorry, an error occurred while loading the content.

Re: [scrumdevelopment] Re: release planning

Expand Messages
  • Kevin Callahan
    I guess it depends what you re hoping to gain by spending time sizing epics? I ll also say that release planning has been one of the most difficult
    Message 1 of 16 , Mar 6, 2013
      I guess it depends what you're hoping to gain by spending time sizing epics? I'll also say that release planning has been one of the most difficult organizational problems to solve. One option, and this is at risk of hijacking the thread, is to ask a different question: what is the minimum we can do right now to push value out the door?

      The teams I work with have seen a lot of value in just-in-time estimation; as long as the next sprint's work is prioritized, groomed, and estimated, there's not a tremendous amount of effort put into additional stories. Lean has deeply influenced my thinking on this, particularly the emphasis on eliminating time delays between story state changes; I realize this is not universal, and varies greatly depending where an app is in its lifecycle, among a whole slew of other important variables.

      In short, from your message it *seems* like maybe there's a bit too much planning, and perhaps not enough stakeholder involvement, to be able to clearly prioritize exactly what is next, and then break only that part down. Stakeholders *should* be excited and eager that their needs are being met, though if there's not alignment at the stakeholder level, well, that's another issue ;)

      Hope that helps…


      On Mar 6, 2013, at 2:26 PM, Richard Griffiths wrote:




      Interesting epic sizing meeting with the team today. We did relative sizing and then assigned them t-shirt values. Then we assigned them points based on planning poker multiplied by 10. Now I know there’s a chance of gaming the values, but some of the epics point sizes matched quite well with previous equivalent epics. The problem arose with larger epic sizes, which was unsurprising due to complexity and some of them being mixed buckets of work. A good first pass, giving us plenty of time to review the epics, split and start grooming the stories. The fact that stakeholders will probably have a heart attack is another matter.


      I’d be interested to see if people think it is worth sizing epics at the t-shirt level and then trying to map story points to them? I’ll be doing the same tomorrow with a more established team so will be interested to see the difference.





      Speed is n0 subsitute fnor accurancy

      Kevin Callahan
      Scrum Master & Agile Coach
      LiveWorld Inc.

      Mobile+1 (207) 691-2997

      Follow UsFacebook Twitter LinkedIn

    Your message has been successfully submitted and would be delivered to recipients shortly.