Thursday, March 08, 2007 1:52 PM
Evaluating your agile team
[tags: Agile Software Development, Project Management, eXtreme Programming, Crystal, Agile Team]
Just read this article http://dan-thinks.blogspot.com/2007/03/agile-team-evaluations-if-you-didnt.html by the agile jedi. It got me thinking how a team could be evaluated. Now we are just about finished with our first release using a XP style methodology. We're not totally XP, but we do stories, iterations, and partially customers on - site. And while I am not a manager doing evaluations (I'm the project lead/manager on this project), I am thinking how we could do evaluations. I like Dan's idea of listing out the XP practices. I would also add some type of category about the number of new methods that are learned. For instance, in our case, there is a learning curve for some of the new technology we use, plus all developers learning our brand of agile.
I don't know about having the whole team evaluate each other. In our case, our projects last generally less than a year, so developers can be on different projects throughout the year. Team evaluation sounds good in theory, but how often is this done? After each project? That's the only way I believe this could work. Otherwise, each project has different team members. If we implement anything like this, I'll try to post any feedback I can on the process, not on specifics.