Maria's presentation on the practices and pitfalls of integrating UX methods into an Agile development process. This is one of the best treatments of the subject I have seen recently, reminiscent of Austin Govella's writing from a year or two ago.

agile-usability: Agile Usability

The companion website for the book Agile Management for Software Engineering - applying the Theory of Constraints for Business Results - by David J. Anderson published by Prentice Hall PTR

This was not so much a redesign, or even a relaunch, but more of a resurrection of a site that had become tired, old and ineffective.

In an agile process with a rolling series of sprints, UX requires two, parallel work streams, clear expectations, and constant status reports.

Agile's focus on small iteration needs a team that can build the now, remember the future, and recognize the gap between the two.

What can you learn about your agile project from this Gannt chart? The one above looks out two years. It shows task dependencies and concurrencies. If you’re iteratively developing software, do you really expect to know what you’ll be doing two years from now, to know if you truly have a dependency? [...]

Jeff Lash on how to product managers can approach Agile methods