On Wed, May 18, 2011 at 6:19 AM, Joey Stanford <[email protected]> wrote: > Hi Gang, > > There is a bit of uneasiness and confusion surrounding the move to > monthly releases so I thought I'd offer up some commentary. Part of > the cause of this anxiety is due to a general desire to explore the > Agile methodology and best practices and see if what we could adopt > inside Linaro.
Some thoughts on agile: * What do our members want? They seem like a traditional, feature focused bunch * How will we get the tight customer focused feedback loop? * How does the current 'estimate the next six month' method fit in with a short horizon agile method without having a large overhang at the end of the six months? * Most agile techniques need the team in one room. How do we apply them to a distributed group where the communication costs are higher? * Our current tools (blueprints, status.l.o) either assume one methodology or aren't sufficient. What will we use? * The XP guys claim that the whole is greater than the sum of the parts and this might be true for most agile systems. We'll have to be careful that we don't cherry pick and get no advantage. I'm happy to do this but we need to measure the cost and benefits, and we mustn't add any overhead or duplication to the engineers. Something agile would be a good fit to the toolchain performance work as it's naturally iterative. -- Michael _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
