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

Re: [scrumdevelopment] Re: Sprint deliverables

Expand Messages
  • Charles Bradley - Scrum Coach CSM PSM I
    Agreed, with the caveat that a team should strive for the minimum amount of documentation that could possibly work.   ... Charles Bradley, CSM, PSM I
    Message 1 of 61 , Jun 9, 2011
    • 0 Attachment
      Agreed, with the caveat that a team should strive for "the minimum amount of documentation that could possibly work."
       
      -------
      Charles Bradley, CSM, PSM I
      Experienced Scrum Coach
      My blog: http://scrumcrazy.wordpress.com/

      From: JackM <jack@...>
      To: scrumdevelopment@yahoogroups.com
      Sent: Thursday, June 9, 2011 11:41 AM
      Subject: [scrumdevelopment] Re: Sprint deliverables

      However I'd like to comment if the team determines that some documentation is required then by all means produce the required documentation as part of the Sprint deliverables. I wouldn't put a focus on documentation though but that doesn't mean No documents.

      Jack
      www.agilebuddy.com
      blog.agilebuddy.com

      --- In scrumdevelopment@yahoogroups.com, Charles Bradley - Scrum Coach CSM PSM I <chuck-lists2@...> wrote:
      >
      > > If you are in the requirements business, then you need to ship a
      > > draft of the complete requirements, not just chapter one. But if the
      > > product is software, ship software.
      >
      > Ron,
      > I'm not a big fan of trying to apply Scrum to other disciplines than software,
      > but I don't think you have your analogy correct here.
      >
      > If requirements is your product, then you need to ship something more than a
      > draft.  You need to ship a "done increment" of your requirements.  I'm not sure
      > how the chapter metaphor applies to requirements.  This is one of the major
      > problems with applying Scrum to things other than software development... the
      > principles don't always translate easily or even at all.
      >
      >  -------
      > Charles Bradley, CSM, PSM I
      > Experienced Scrum Coach
      > My blog: http://scrumcrazy.wordpress.com/
      >
      >
      >
      >
      > ________________________________
      > From: Ron Jeffries <ronjeffries@...>
      > To: scrumdevelopment@yahoogroups.com
      > Sent: Fri, May 20, 2011 5:01:32 AM
      > Subject: Re: [scrumdevelopment] Sprint deliverables
      >
      > Hello, poojawandile.  On Friday, May 20, 2011, at 3:37:01 AM, you
      > wrote:
      >
      > > hi, We have a debate going on in our company. Some Scrum teams are firm
      > > believers that increamental shippable product at the end of the sprint
      > > is what should be the sprint deliverable. The other section believs that
      > > a design document, a requriemebnts document cud also be the sprint
      > > deliverable, especially when the project is new and it needs to work on
      > > the requreiments doc and design doc before coding can start. Can a req
      > > doc or a design doc be a sprint deliverable?
      >
      > Scrum asks for a potentially shippable increment of product. If your
      > product is software, that means software, yes even in the first
      > Sprint.
      >
      > If you are in the requirements business, then you need to ship a
      > draft of the complete requirements, not just chapter one. But if the
      > product is software, ship software.
      >
      > Ron Jeffries
      > www.XProgramming.com
      > The central "e" in "Jeffries" is silent ... and invisible.
      >
      >
      >
      > ------------------------------------
      >
      > To Post a message, send it to:  scrumdevelopment@...
      > To Unsubscribe, send a blank message to:
      > scrumdevelopment-unsubscribe@...! Groups Links
      >
      >
      >
      >    http://docs.yahoo.com/info/terms/
      >




      ------------------------------------

      To Post a message, send it to:  scrumdevelopment@...
      To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links

      <*> To visit your group on the web, go to:
          http://groups.yahoo.com/group/scrumdevelopment/

      <*> Your email settings:
          Individual Email | Traditional

      <*> To change settings online go to:
          http://groups.yahoo.com/group/scrumdevelopment/join
          (Yahoo! ID required)

      <*> To change settings via email:
          scrumdevelopment-digest@yahoogroups.com
          scrumdevelopment-fullfeatured@yahoogroups.com

      <*> To unsubscribe from this group, send an email to:
          scrumdevelopment-unsubscribe@yahoogroups.com

      <*> Your use of Yahoo! Groups is subject to:
          http://docs.yahoo.com/info/terms/



    • Charles Bradley - Scrum Coach CSM PSM I
      Agreed, with the caveat that a team should strive for the minimum amount of documentation that could possibly work.   ... Charles Bradley, CSM, PSM I
      Message 61 of 61 , Jun 9, 2011
      • 0 Attachment
        Agreed, with the caveat that a team should strive for "the minimum amount of documentation that could possibly work."
         
        -------
        Charles Bradley, CSM, PSM I
        Experienced Scrum Coach
        My blog: http://scrumcrazy.wordpress.com/

        From: JackM <jack@...>
        To: scrumdevelopment@yahoogroups.com
        Sent: Thursday, June 9, 2011 11:41 AM
        Subject: [scrumdevelopment] Re: Sprint deliverables

        However I'd like to comment if the team determines that some documentation is required then by all means produce the required documentation as part of the Sprint deliverables. I wouldn't put a focus on documentation though but that doesn't mean No documents.

        Jack
        www.agilebuddy.com
        blog.agilebuddy.com

        --- In scrumdevelopment@yahoogroups.com, Charles Bradley - Scrum Coach CSM PSM I <chuck-lists2@...> wrote:
        >
        > > If you are in the requirements business, then you need to ship a
        > > draft of the complete requirements, not just chapter one. But if the
        > > product is software, ship software.
        >
        > Ron,
        > I'm not a big fan of trying to apply Scrum to other disciplines than software,
        > but I don't think you have your analogy correct here.
        >
        > If requirements is your product, then you need to ship something more than a
        > draft.  You need to ship a "done increment" of your requirements.  I'm not sure
        > how the chapter metaphor applies to requirements.  This is one of the major
        > problems with applying Scrum to things other than software development... the
        > principles don't always translate easily or even at all.
        >
        >  -------
        > Charles Bradley, CSM, PSM I
        > Experienced Scrum Coach
        > My blog: http://scrumcrazy.wordpress.com/
        >
        >
        >
        >
        > ________________________________
        > From: Ron Jeffries <ronjeffries@...>
        > To: scrumdevelopment@yahoogroups.com
        > Sent: Fri, May 20, 2011 5:01:32 AM
        > Subject: Re: [scrumdevelopment] Sprint deliverables
        >
        > Hello, poojawandile.  On Friday, May 20, 2011, at 3:37:01 AM, you
        > wrote:
        >
        > > hi, We have a debate going on in our company. Some Scrum teams are firm
        > > believers that increamental shippable product at the end of the sprint
        > > is what should be the sprint deliverable. The other section believs that
        > > a design document, a requriemebnts document cud also be the sprint
        > > deliverable, especially when the project is new and it needs to work on
        > > the requreiments doc and design doc before coding can start. Can a req
        > > doc or a design doc be a sprint deliverable?
        >
        > Scrum asks for a potentially shippable increment of product. If your
        > product is software, that means software, yes even in the first
        > Sprint.
        >
        > If you are in the requirements business, then you need to ship a
        > draft of the complete requirements, not just chapter one. But if the
        > product is software, ship software.
        >
        > Ron Jeffries
        > www.XProgramming.com
        > The central "e" in "Jeffries" is silent ... and invisible.
        >
        >
        >
        > ------------------------------------
        >
        > To Post a message, send it to:  scrumdevelopment@...
        > To Unsubscribe, send a blank message to:
        > scrumdevelopment-unsubscribe@...! Groups Links
        >
        >
        >
        >    http://docs.yahoo.com/info/terms/
        >




        ------------------------------------

        To Post a message, send it to:  scrumdevelopment@...
        To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links

        <*> To visit your group on the web, go to:
            http://groups.yahoo.com/group/scrumdevelopment/

        <*> Your email settings:
            Individual Email | Traditional

        <*> To change settings online go to:
            http://groups.yahoo.com/group/scrumdevelopment/join
            (Yahoo! ID required)

        <*> To change settings via email:
            scrumdevelopment-digest@yahoogroups.com
            scrumdevelopment-fullfeatured@yahoogroups.com

        <*> To unsubscribe from this group, send an email to:
            scrumdevelopment-unsubscribe@yahoogroups.com

        <*> Your use of Yahoo! Groups is subject to:
            http://docs.yahoo.com/info/terms/



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