http://blogs.msdn.com/micahel/archive/2006/05/31/ChangeTakesTime.aspxOne thing I've learned being a lead is that change takes time. And the bigger the change the longer it's going to take. Hence it follows that if your goal is to accomplish a big change in record time you had best break it into many many itty-bitty changesen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/micahel/archive/2006/05/31/ChangeTakesTime.aspx#612631Thu, 01 Jun 2006 09:01:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:612631anuttharaYou won't believe this, but I was just writing a blog about exactly this - how difficult it is sometimes to get people to change and look with an open mind towards a different approach. I was screaming down the rooftops about how SCRUM is the greatest process on earth and how all small teams should do SCRUM. It was hard for me to understand why folks were resisting something that would certainly and surely improve productivity. <br> <br>Same story here - It was later that I realised that the problem is with me trying to shove Agile down everyone's throat. A different approach to evangelize &quot;agile&quot; would work but also work much slowly than I would wish! Mgmt is very supportive and a bit more realistic than I am. :) I hope my team turns out the same way as yours did! :) http://blogs.msdn.com/micahel/archive/2006/05/31/ChangeTakesTime.aspx#612678Thu, 01 Jun 2006 10:34:16 GMT91d46819-8472-40ad-a661-2c78acb4018c:612678Phil KirkhamI also wrote a big paper with everything that I thought had to change so that we could do proper testing and have some form of QA and I too have now calmed down a bit - though it's hard to find the balance between being enthusiastic and being a pain in the *ss <br> <br>Small regular pushes, nudges and hints seem to have worked better than one huge shove. <br> <br>The one problem I have is that some of my younger allies are more impatient and want to know when when WHEN all this is going to happen and cant see that things are changing, but gradually <br> <br>What sort of timescale did your changes happen in - months ? years ?http://blogs.msdn.com/micahel/archive/2006/05/31/ChangeTakesTime.aspx#613111Thu, 01 Jun 2006 20:27:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:613111micahelAnutthara, Phil: If only I had written this post years ago and we all could have read it, it might have saved us all some pain! &lt;g/&gt; These particular changes took a couple years before they took hold. Improving my team's development process went a lot faster, about six months. Other changes I'm still working on. &lt;g/&gt;