Mikko's done this: Agile Dinner in Tampere

Yet another agile dinner in Tampere is over. Good food and discussion. Below a short summary of the points made on the theme and links to material I mentioned on other topics discussed.

http://confluence.agilefinland.com/display/af/Agile+Dinner+in+Tampere+20090819

Physical task board got most attention, spreadsheets was distant second.
Buy extra sticky post-it notes (from a good bookstore) or use a special glue to get index cards stick.
Updates can be done as often as team likes, but usually at least once a day.
Co-located teams usually like task boards, as it is easy to maintain and fits the purpose of showing them how much work is left.
Updating burndown chart by computing the remaining effort from task board manually does not take much time.
Documenting changes (for communicating them to distributed stakeholders) can be done by taking a photo.
If someone wants to document daily changes when using a physical task board, changed notes can be turned upside down.
There is seldom need for saving backlogs for further analysis after the retrospective.
Estimates are usually in hours in sprint backlogs (not in story points).
You can present the size by giving bigger tasks a bigger post-it note! However, usually a number on the corner will do.
Tasks in Sprint backlog are usually refinements / breakdowns of product backlog items.
Team should do the estimates (not managers or such) in order to better understand the work to be done.

Mikko's done this