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

47016Re: [scrumdevelopment] Status Reporting, scheduling & estimation in Scrum

Expand Messages
  • George Dinwiddie
    May 30 7:29 AM
    • 0 Attachment
      AB,

      b_aashish wrote:
      > Hi Reporting status in Waterfall projects is easy - you have the
      > milestones (e.g. Req Doc completed/sign-off, Design docs completed,
      > coding finished etc.. You have an overall plan and schedule against
      > which you report that the projecy is 25% comeplete etc.
      >
      > How does one that in Scrum projects? Specially if it is a greenfield
      > project. Does one do a high-level estimate/schedule of the entire
      > Product backlog at the start? What kind of estimation would help
      > here? How does one tell the customer how many sprints would be
      > required to finish the complete the complete project? Any
      > recommendations for status reporting? How can one apply EV here?
      >
      > Any insight please?

      I think
      http://blog.gdinwiddie.com/2010/04/22/projecting-into-the-future/ will
      help. If you've got any questions after reading that, ask away.

      BTW, the traditional EV calculations make the assumption that value
      received is equal to the cost expended. It must make that assumption,
      because in a traditional all-or-nothing project, there is no value
      actually received until the end. When value is received throughout the
      project, you can see that this assumption is not warranted.

      - George

      --
      ----------------------------------------------------------------------
      * George Dinwiddie * http://blog.gdinwiddie.com
      Software Development http://www.idiacomputing.com
      Consultant and Coach http://www.agilemaryland.org
      ----------------------------------------------------------------------
    • Show all 24 messages in this topic