Wayne Allen's Weblog

Regarding my previous post on version control, I thought I give a little update on what we finally decided to do.

On Ward's suggestion we made a change to our iteration planning around the velocity & task sign-up process.

Looks like I'll be attending XP/Agile Universe in New Orleans Aug. 10-13. Any other bloggers going to be there?

In discussions with Ward and others in our QA group I'm starting to see another possible arrangement for an agile QA team.

We have the great pleasure of having Ward Cunningham on-site this week to help us fine tune our implementation of XP/agile process.

One of the roles we have defined in our agile process is the "Customer Advocate". This is a distinct role from Customer or Customer Proxy in that the advocate is looking after the customer's needs from a quality perspective. The need for an advocate is seen in many agile implementations. The usual symptoms are a customer that needs to do their "real" job or where the customer needs assistance writing appropiate stories and acceptance tests. The advocate him/herself may or may not have any specific domain knowledge.

ScottW asked What are you reading? For all the reasons he mentioned I think it a good idea.

We've been having an interesting discussion internally about whether our development and QA groups should be part of the same agile team or seperate with a half iteration offset. So far we've developed a list of pros and cons to help us decide where to go.