AgileKiwi
Practical Agile Software Development
This site is about connecting agile development with customers. As developers we know agility works better, but sometimes our customers don't. To explain its benefits we must address difficult issues like contracts and trust, we must adopt inclusive definitions of agility, and we must focus on customers' interests as well as our own.
I think of it as "negotiated agility" -- tailoring the process to the customer, to the team, and to the constraints of the project.
You'll notice this site is mostly not about Extreme Programming (XP). If anything, you'll detect a slight anti-XP bias, which is my way of sticking up for all the other forms of agile development, such as Crystal Clear, Scrum and FDD.
Featured Articles:
A reminder to value "individuals and their interactions over processes and tools".
Vital social elements are often dismissed as “emergent properties”, expected to take care of themselves as long as we follow the right processes. They deserve more attention than that.
|
|
There's a self-organising "conference" about agile development, in Wellington on 30 Nov 2007.
Check out this page for details: http://barcamp.org/BarCampAgileWellington
Notes from my session are here.
|
|
Agile Development encourages a style of negotiation which has proven itself at the highest levels of business and international politics. It's great for software too.
|
|
Do you want a better way to track your team's progress? Instead of time-consuming Gantt charts, try a simple yet powerful "time and budget" chart.
|
|
Can you use agile development under fixed-price contracts? Martin Fowler says you can't; Alistair Cockburn says you can. Who's right?
|
|
Crystal Clear is a methodology that summarises 10 years of research into successful software teams. Which things really matter? Which things most influence the project outcome?
|
|
Does agility improve more than our software? Does it also improve us, the programmers?
|
Last significant site update: 3 Oct 08
AgileKiwi - Practical Agile Software Development
Copyright (c) 2003-2006, John Rusk.