I have released a course on Pluralsight called Agile Fundamentals that talks about Agile Software Development in detail.
I have also written an article on Common Agile Misconceptions.
Recently, I have been doing lots of recruitment for .NET consultants. Each of the CV’s we receive all stress that they are experienced in working in agile development shops. This is great. We are an agile development company so these people sounds like a great fit.
So we get them into an interview and ask them, ‘What does agile mean?’, ‘How do you know if your team is truly agile?’ It’s at that point we get the standard list of responses:
- We do Test Driven Development.
- Daily stand-ups.
- We pair program.
- We use continuous integration.
- We use SCRUM, KanBan, XP etc.
- Use work in iterations.
- We use story points.
- We calculate team velocities.
These answers are all well and good, but they don’t describe what an agile team is. These are all just facilitators to being agile. What’s even worse is that these interviewees seem to have not heard of the agile manifesto.