At Readify we use a mixture of MSF Agile and Scrum as our project methodology but I've very much come to the belief that methodologies are the tools of procrastination (other than KPI's (Key Procrastination Indicators) but that's another story
). It's actually funny the things that people will tell you that methodologies can give you:
- Improve your estimations
- Improve the quality of your software by writing tests
- Get your customers more engaged in the process
- Get your planning process nailed
- Putting the "fun" back in Functional Specs!

I'll bet that all of your projects sound like that right? Hrm, no eh? Maybe you'd better go and buy another shopping trolley full of those methodology books:
- Testing debunked
- Estimation demystified
- Gantt charts for guru's
- Mastering scheduling
- Project Plans for Dummies
Reading all of those books sounds like fun right? Blech! No way, me either. I can almost guarantee that no matter how many books you buy on estimation that your estimates will not get better - just your excuses. Regardless of the number of books you read on project planning and Gantt chart creation, your charts will be wrong - and you will be constantly need to change your scheduling.
Here's a little story about something that I've observed in the last year. It amazes me, the number of developers who come onto projects and, before they've even had time to sex-up their cubicle, they're out adding a whole heap of stuff into the solution for tests. Projects, tools, widgets, reports... you name it. And it's not enough that they add all this gunk in with our code, they then proceed to spend the next few days feverishly working out how to automate their tests and publish data to the test report database. Regardless of all these heroics the number of projects that achieve their stated testing goals is a very, very small number indeed. And even for the chosen few that do manage to get some tests written against them... nobody reads those reports or runs the tests anyway. Heck, when new developers come onto those projects the very first thing that they do is to cast doubt over the meaningfulness of the tests anyway. I know that I go against the crowd when I say this... but it must make you wonder!
I've decided to announce that methodologies should not be taken so seriously - not in large doses anyway. The thing that none of those books ever tell you is this... you either have it, or you don't! You will rarely learn this in books, but to be successful in your projects (and it probably doesn't hurt in general life either) the main thing that you require is self-awareness. Without it, you will unfortunately almost always fail. And a good healthy dose of being decisive doesn't hurt either.
Good self-awareness will actually lead you to find the right answers and discover problem areas well before those TFS cubes ever kick into action. And decisive decision making and communication will ensure that you do the right things too. Next time you are on a project, listen to the heartbeat, use your eyes to see what's happening, and use your brain to think about your next moves. You won't need a methodology to tell you something is broken or healthy. Throw away your functional specs, cast your Gantt charts to the wind and deploy your app today!