Wayne, as specialist consultants in Agile adoption, I must say that the recommended approach is to employ a Mentor: someone who has been through the process before, and so knows what to expect and whether things are going right. Often, things are going right: but, if it's your first time, the lightweight nature of Agile will make you nervous.

Michael Durrant gives some very good advice. It is about 'people'. However, you're also correct to identify the need for a process. So, Wayne, choose one and adopt it! As simple as that. The point being that any process is better than no process. And, once you've adopted a process, you can then evaluate how wll it is working. Only then can you decide what to tweak or change. Agile is about being daring; yet, because you'll be running in short iterations, it's easy to correct any errors.

As for producing 'usable' software from a three week iteration cycle. Yes, that is possible. You need to focus on measurable Requirements. That way you'll deliver something meaningful. However, you will not produce a complete software suite with the piecemeal approach -- iterative development is about riquirements discovery (exploration) and risk management -- but, as your intuition is telling you, there's a bit more to it than simply piling iterations on top of each other. Also, as you're using XP, don't forget about the project's future documentation & training needs!

Most Agile adoption consultancies, like Gatethorn, will give some free advice to people who are getting going. Don't be afraid to give them a call. After all, we only know what help our customers need by answering questions on Forums or taking calls. So, Wayne, keep coming back to this forum if you need help.

All the best, Richard (CEO Gatethorn Agile thinking)

Wayne, as specialist consultants in Agile adoption, I must say that the recommended approach is to employ a Mentor: someone who has been through the process before, and so knows what to expect and whether things are going right. Often, things are going right: but, if it's your first time, the lightweight nature of Agile will make you nervous.

Michael Durrant gives some very good advice. It is about 'people'. However, you're also correct to identify the need for a process. So, Wayne, choose one and adopt it! As simple as that. The point being that any process is better than no process. And, once you've adopted a process, you can then evaluate how well it is working. Only then can you decide what to tweak or change. Agile is about being daring; yet, because you'll be running in short iterations, it's easy to correct any errors. Being Agile applies as much to tweaking the process as it does to tweaking the software you're developing.

As for producing 'usable' software from a three week iteration cycle. Yes, that is possible. You need to focus on measurable Requirements. That way you'll deliver something meaningful. However, you will not produce a complete software suite with the piecemeal approach -- iterative development is about riquirements discovery (exploration) and risk management -- but, as your intuition is telling you, there's a bit more to it than simply piling iterations on top of each other. Also, as you're using XP, don't forget about the project's future documentation & training needs!

Most Agile adoption consultancies, like Gatethorn, will give some free advice to people who are getting going. Don't be afraid to give them a call. After all, we only know what help our customers need by answering questions on Forums or taking calls. So, Wayne, keep coming back to this Forum if you need help.

All the best, Richard (CEO Gatethorn Agile thinking)