Agile Experience Design

Integrating the Agile and Experience Design Practices

Jason Furnell

Agile Card Wall - the process itself made UX design a more inclusive activity

Here is a list of reasons why it think this simple method of placing cards on a wall is so essential to team collaboration, trust, personal empowerment and ownership. The process itself made design a more inclusive activity.

* in the end its all about making the abstract concrete – developing software is an ethereal thing, it needs a high level of understanding and trust between everyone working on the product. the card wall, and the wider principals of agile allowed team members to develop a shared understanding of what we are doing and how we will get there. Its not something that is dictated to us in a command and control sort of way – we are the masters of our own destiny. We collectively decide what matters, whats most important to focus effort on and whos best placed to tackle the tasks.

* daily standups occurred just near this wall, the entire team could at a glace be reminded of where were were in the project, and what we had achieved so far

* physically embodying task on cards means that people can really take ownership of a task -this simple act of “owning a card” focused activity – at the end of each iteration the card owner talked about progress and moved the card into the appropriate row (the top row is completed – and the rows below show where the task is at – in progress, dev ready, awaiting estimation, more information needed)

* as we moved through the iterations (from left to right on the wall) we could see how much we had done, and collectively felt proud of the momentum and progress

* at the beginning of an iteration, we all stood around the wall and prioritized cards and allocated them to team members – this meant everyone understood what everyone else was doing – and again this helped develop trust and a true feeling of team work. the simple act of physically moving cards around, and being empowered to really take ownership of how to progress has real benefits

* i should make it clear that the wall was owned by everyone on the project, not just the developers. James (Our product manager), me (UX), damien (project management), Brenden(dev lead), all the devs, all the testers – we all collectively owned this “space”.

* It helped me focus on what i needed to do to support the dev team – in terms of knowing exactly what UI and Interaction specs were needed when.

* i should also mention that the process itself made design a more inclusive activity – a change from design dictator to design facilitator – and with the input of all members the product is far better for it.

from http://jasonfurnell.wordpress.com/
Austin Govella Comment by Austin Govella on September 28, 2009 at 7:20pm
Jason,

Would you be interested in turning this into a case study for Boxes and Arrows?

Comment

You need to be a member of Agile Experience Design to add comments!

Join Agile Experience Design

© 2010   Created by Anders Ramsay.   Powered by .

Badges  |  Report an Issue  |  Terms of Service