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

Re: [XP] Fixed Duration Iterations

Expand Messages
  • Tim Ottinger
    Yes, they can. Tim Ottinger http://agileotter.blogspot.com/
    Message 1 of 8 , Nov 20, 2008
    • 0 Attachment
      Yes, they can.

      Tim Ottinger
      http://agileotter.blogspot.com/



      ----- Original Message ----
      > From: Kevin Trethewey (Driven Software) <kevint@...>
      > To: extremeprogramming@yahoogroups.com
      > Sent: Thursday, November 20, 2008 8:47:44 AM
      > Subject: Re: [XP] Fixed Duration Iterations
      >
      > Thanks for the feedback Tim.
      >
      > So what you are saying is that they could set up a common pulse for the team
      > in terms of retrospectives and feedback, without actually having releases
      > corresponding?
      >
      >
      >
      > On Thu, Nov 20, 2008 at 4:11 PM, Tim Ottinger wrote:
      >
      > > 1) Retrospectives. Maybe monthly, maybe bi-weekly.
      > > 2) Get a feedback loop going (on-site customer, etc)
      > > 3) Encourage teaming/pairing on issues of common interest (structure,
      > > style, libraries, visual polish, etc)
      > > 4) To make 1-3 easier, get a common fixed pulse. I recommend no larger than
      > > 2 weeks.
      > >
      > > Tim Ottinger
      > > http://agileotter.blogspot.com/
      > >
      > >
      > > ----- Original Message ----
      > > > From: Kevin Trethewey (Driven Software)
      >
      > > >
      > > > To: extremeprogramming@yahoogroups.com
      > > > Sent: Thursday, November 20, 2008 7:57:02 AM
      > > > Subject: [XP] Fixed Duration Iterations
      > > >
      > > > I am working with a team of four domain-experts-who-also-code. They are
      > > not
      > > > working on a single unified product per se, but are building in-house
      > > > (financial modelling) tools that are consumed via excel. They need some
      > > > guidance on how to introduce a bit more process into their routines.
      > > These
      > > > are a couple of their pain points...
      > > >
      > > > * Are unable to polish code enough to get it to a point where it is
      > > > production ready
      > > > * Have an issue with duplicate code being developed because of lack of
      > > > communication
      > > > * Lack skills to develop code that is well layered, and follows proper
      > > > design principles, so code tends to be hard to extend and maintain
      > > >
      > > > I think one of the mechanisms that will address their issues is to use
      > > > continuous integration and make small regular releases to production.
      > > >
      > > > The question I have is this - the developers are all, as I mentioned,
      > > domain
      > > > experts in their own individual (but related) fields. They do not all
      > > work
      > > > on the same features at the same time, and therefore they will each
      > > > compelete their individual tasks at different points and with different
      > > > frequencies.
      > > >
      > > > Would it be proper to take a fixed team-level iteration approach with a
      > > > group like this? What is the alternative - give each developer their own
      > > > fixed duration release cycle? Avoid fixed release cycles all together?
      > > >
      > > > Thanks in advance!
      > > >
      > > > Kevin Trethewey
      > > > Driven Software
      > > >
      > >
      > >
      > >
      >
      >
      >
      > --
      > Regards,
      > Kevin Trethewey
      >
      > Driven Software
      >
      > t: +27 (0) 82 579 9154
      > f: +27 (0) 82 131 579 9154
      > e: kevint@...
      > w: http://www.drivensoftware.net
      >
      >
      > [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.