On 29/10/10 19:29, Teyo Tyree wrote: > On Oct 29, 7:32 am, Paul Nasrat <[email protected]> wrote: >> On 28 October 2010 23:39, Teyo Tyree <[email protected]> wrote: >> >>> Like to note a few things about our development shift that we >>> unfortunately did not communicate effectively in our initial email. >>> We are iterating on our internal development process in order to more >>> rapidly deliver complete features across our projects. In order to be >>> as transparent as possible and to provide the community with enough >>> context to understand our desire to shift the way we send patches to >>> the list, I'll summarize our new process. None of these processes are >>> set in stone. We plan to improve and refine our internal processes >>> each week. >> >>> We have moved to short iteration cycles that deliver real value. (We >>> are testing one week iterations at the moment.) >> >> I think it's probably good news that you are adopting xp practices as >> part of your development. It'll certainly mean the puppetlabs team has >> a better shared understanding of the code base. I realise that it's >> hard to figure the detail of involving the community. >> >> One thing I'm curious about is were these changes started before >> puppetcamp? As that would have been a great opportunity to discuss >> workflow in person and figure out some details and set expectations. >> If not it's just unfortunate timing, maybe should try something with >> the community and have regularish opportunities to improve the process >> - ie retrospectives but aimed at ensuring the puppetlabs/open source >> community workflow is continually improving. >> >> Paul > > The switch happened after Puppet Camp. I agree that the timing was > unfortunate. We are indeed experimenting with XP. > > We can totally include a public retrospective at the end of each > iteration. Our backlog is not fully populated at the moments. We > just picked the inventory service because it is damn useful and we had > it pretty well characterized. As Nigel pointed out, we are justing > getting started and it is all a little rough around the edges. We are > going to work hard to find something that works for everyone.
Just a side question: how does the bug-fix work you are doing fit in this kind-of-scrum model? -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
