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

Re: [XP] Re: How does the work in iteration gets inspected in XP?

Expand Messages
  • Adam Sroka
    1-4 weeks with preference for the shorter... Though eventually most of the community came to favor one-week iterations. Some now have dropped iterations.
    Message 1 of 10 , Mar 21, 2012
      1-4 weeks "with preference for the shorter..." Though eventually most
      of the community came to favor one-week iterations. Some now have
      dropped iterations.

      On Wed, Mar 21, 2012 at 7:01 PM, Joshua Partogi <joshua.java@...> wrote:
      > Thanks Ron. From what I understand, an iteration is 2 weeks long. So what
      > happens at the end of the iteration?
      >
      > On Thursday, March 22, 2012, RonJeffries <ronjeffries@...> wrote:
      >>
      >>
      >> On Mar 21, 2012, at 9:31 PM, Joshua wrote:
      >>
      >>> Sorry to confuse you. In Scrum the work within the Sprint gets inspected
      > during Sprint Review.
      >>
      >> In Sprint Review the stakeholders see the accepted backlog items for the
      > Sprint. They do not inspect the code. The Sprint Review is used to get
      > ideas for new things to do and to learn a bit from what has gone before, in
      > preparation for Sprint Retrospective.
      >>
      >>> How does the work in the XP Iteration gets reviewed? Is there any
      > dedicated ceremony in XP to review the work done?
      >>
      >> No. XP has no such named ceremony. The Planning Game / Small Releases /
      > Customer Tests / Whole Team cycle provides the visibility. If I were
      > writing it up today I would emphasize retrospectives but would personally
      > not add a Sprint Review equivalent.
      >>
      >> If I were to read between your lines, it sounds to me as if you are
      > trying to find out about a specific process to do. Neither Scrum nor XP are
      > specific processes in that sense. They create an environment where the team
      > (which includes the business-side people) can see what is going on and
      > improve it. The specifics are up to the team.
      >>
      >> Ron Jeffries
      >> www.XProgramming.com
      >> Everything that needs to be said has already been said.
      >> But since no one was listening, everything must be said again. -- Andre
      > Gide
      >>
      >> [Non-text portions of this message have been removed]
      >>
      >>
      >
      > --
      > @jpartogi
      >
      >
      > [Non-text portions of this message have been removed]
      >
      >
      >
      > ------------------------------------
      >
      > To Post a message, send it to:   extremeprogramming@...
      >
      > To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe@...
      >
      > ad-free courtesy of objectmentor.comYahoo! Groups Links
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.