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

Re: When does the tasks in sprint backlog estimated in man hours?

Expand Messages
  • kaundinya_ram
    Hi Charles, Thank you for your clear reply. I understood. I had also downloaded the newest Scrum Guide and I am reading it. Regards Ram
    Message 1 of 3 , Aug 16, 2011
    • 0 Attachment
      Hi Charles,

      Thank you for your clear reply. I understood.

      I had also downloaded the newest Scrum Guide and I am reading it.

      Regards
      Ram

      --- In scrumdevelopment@yahoogroups.com, Charles Bradley - Scrum Coach CSM PSM I <chuck-lists2@...> wrote:
      >
      > Ram,
      >
      > The newest Scrum Guide ( http://www.scrum.org/scrumguides/ ) does not specify estimation units for product backlog items nor for sprint backlog work.  Also, User Stories are not a part of Scrum, but they are one technique(of several) for representing backlog items.  Finally, in the new Scrum Guide, there is no requirement that the sprint backlog be broken down into tasks.
      >
      >
      > Per the Scrum Guide...
      >
      > So, having said that, if your Scrum team chooses to do User Stories, story estimates in story points, and sprint backlog planning with tasks and hours, these tasks are typically created in the Sprint Planning Meeting and/or after each Daily Scrum when Dev Team members get together to refine the sprint backlog.  They can also be changed at any time during the sprint by the Dev Team.
      >
      >
      > During part two of the Sprint Planning meeting, typically the PO is available if the Dev Team wants to ask questions that will help the Dev Team to create the Sprint Backlog.  However, creating the sprint backlog is a responsibility of the Dev Team, and the PO generally doesn't give direct input to that.
      >
      > In practice, in my experiences...
      >
      > With a 2 week Sprint, 80-90% of the Sprint tasks will be created in the Sprint Planning Meeting, with the remaining 10-20% created as they are discovered within the Sprint.
      >
      > Velocity is a User Story Points term that is not a Scrum Term.  Using story points, there is typically no direct correlation between story points and man hours.  They are often proportionally related (i.e. a bigger story usually means a higher number of hours, but not always).  Velocity is really only a term to speak about past completion rates of stories, and to ***help*** forecast when a grouping of future stories will be done.
      >
      > Does that help?  Any other questions? 
      >
      >
      > Be sure and give a read to the newest Scrum Guide at the link above.  Another excellent source for information on these topics is Mike Cohn's book, _Agile Estimating and Planning_ .
      >
      >  
      > -------
      > Charles Bradley, CSM, PSM I
      > Experienced Scrum Coach
      > Currently Seeking engagement as Scrum Coach or Scrum Master in Denver area
      > My blog: http://scrumcrazy.wordpress.com/
      >
      >
      > >________________________________
      > >From: kaundinya_ram <kaundinya_ram@...>
      > >To: scrumdevelopment@yahoogroups.com
      > >Sent: Tuesday, August 16, 2011 7:14 AM
      > >Subject: [scrumdevelopment] When does the tasks in sprint backlog estimated in man hours?
      > >
      > >Hi,
      > >
      > >I do not have practical experience in SCRUM but I am very much interested in that.
      > >
      > >I have a question regarding estimating the sprint backlog tasks.
      > >
      > >PBI (Product Backlog Items) are estimated in story points during the ReleasePlanning and sprint backlog tasks are estimated in man hours.
      > >
      > >When does this estimation in man hours for the tasks are conducted? Is it during the SprintPlanning meeting? During this meeting, does the Product Owner also provide inputs?
      > >
      > >Or the man hours is derived from the velocity and the sprint timebox? If this is so, can you please explain how the man hours is calculated from velocity?
      > >
      > >Regards
      > >Ram
      > >
      > >
      > >
      > >
      > >------------------------------------
      > >
      > >To Post a message, send it to:  scrumdevelopment@...
      > >To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
      > >
      > >
      > >
      > >
      > >
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.