• The customer's changing requirements are viewed as a risk that need to be managed
  
• Team member's roles are clearly defined.

What's the key thing here? The process is first and the people second. This may be fine for building space shuttle software, but does it work for the bulk of normal software development?

The answer is a resounding no!

So what's the best way to deliver quality software on time in the face of changing requirements, variable skill levels, and technology churn.

For one thing your project team needs to be light on their feet, adaptable, mmmm…. Agile, that's the word!

• Short iterations: How to deliver fully working software to your customer every one to three weeks.
  
• Embrace Change: How to use change as an opportunity to improve system design and not turn it into a brittle mess.
  
• High Quality: How to deliver on time without sacrificing quality.
  
• Have fun: How to avoid Ed Yourdon's "Death march" and put back the fun into software development.
  

The event will specifically look at the techniques that underpin documented Agile Development approaches. These include refactoring, test first programming, and pair programming. The event will also show how a heavy process, the Unified Process, can be made more agile.