Recently I saw a brief set of questions from Nokia to assess whether or not a team is ‘agile’.

And by ‘agile’, I think they meant to what extent the team was following agile practices Scrum and XP (eXtreme Programming), not whether or not they could touch their toes :)

I’m not sure if it was deliberately brief to emphasise the things that are the real *essence* of agile, but we’ve developed the questions into a more comprehensive set of statements. A set of statements that make a fuller assessment of someone’s status with agile principles and methods.

Here they are…

This is the second of several posts in which I’d like to share some of the things we learned throughout more than 14 sprints of Agile development using Scrum. Some of them might appear as open doors, but I wish I knew or thought about those before I started that project. Just by looking back at the mistakes a team of 10 made in a period of 12 months, they apparently aren’t that obvious. So after having discussed requirements management, let’s talk about the sprint planning.

One year ago, at the Agile 2010 conference, I came up with the idea to publish a Top 100 Agile Books. Like many of my other top 100 lists it was a great success (in terms of blog traffic).

This year I am not at the Agile 2011 conference (for various reasons, both good and bad). But nevertheless, I decided to publish a new edition of the Top 100 Agile Books, especially for my friends at Agile 2011 who are enjoying a great conference without me.