I use what ever the client mandates. I certainly wouldn't use any methodology that I wasn't forced to. Where no local standard has been imposed I've always been able to get by with a minimum of simple documents appropriate to the place and the project. My default approach is data-oriented RAD.
I think you need to list what methodologies you are thinking of.
I've worked for many large organisations and they all have their own. I did some work for the UK Government and they claimed to use Prince II ( and old fashioned product-based waterfall scheme) but in fact they used the opposite. Everything was done in reverse-order ie specs were generated after the design etc. The specifications weren't worth the paper they were written on. Complete bollox and needless to say, the budget grew by 10% every month and the chances of achieving anything diminished by the same factor.
My experience is methodologies depend on religion rather than project type. Companies choose a governance approach for political reasons rather than what type of situation they are in.
I'd love to be more constructive but almost exclusively IT is chaotic and illogical. There are exceptions but they are rare.
My most common methodology is CVP, which has origins in contruction trades/projects but also seems to bolt up nicely to IT projects of many sorts. Strong on benefits analysis and stage-and-gate reviews for governance. Weak on enforcing stakeholders' total buyin. I know there are things like OPM3 etc that might be of merit.
D.E.R. Management - IT Project Management Consulting
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.