I’ve seen a lot of projects becoming agile. In the beginning change to agility was pushed by development teams themselves, lately management layer became aware of the benefits agility can potentially bring. Unfortunately blind appliance of agile methodologies (as with anything else) can do harm to team performance rather than making any improvement. Migration to agility is supposed to result in better performance, but how do you prove that money and effort spent on introduction of a modern agile methodology was actually fruitful? That’s the question that I was asking myself for quite some time now, and finally I hope I will get an answer from a very respectful person in IT world – Ivar Jacobson International. I had a pleasure of meeting him and listening to one of his lectures and I was really impressed by this bright-minded Swede with a Swiss citizenship. I think that he was considering St.-Petersburg as a possible location for one of his representative offices, but unfortunately oil prices in Russia were too high already. Anyway, here is the email notification that I received about the upcoming series of three webinars. Everybody wants to be agile – but how do you demonstrate that new agile projects are more effective than their non-agile predecessors? In particular, how can you measure the performance of all your projects in a way that allows their achievements to be compared independently of the practices they use, and in a way that is accessible to your business partners? Ivar Jacobson International is pleased to present a three-part free series covering the essentials of measuring in agile software development organizations. Join us as Ian Spence presents each of these informative sessions. Seminar #1: April 27, 2010: Better, Faster, Cheaper, Happier: Measurements for Agile Software Development Organizations Seminar #2: May 27, 2010: Better, Faster, Cheaper, Happier: Succeeding with Measurements in a large Software Development Organization Seminar #3: June 29, 2010: Creating an Iterative Dashboard: Making sense of burn-downs, burn-ups and other practical project measures Read more here. Software Development