I was thinking about some of the discussions I’ve been having lately about how the methodology (gasp – I used the M word) we are using to manage a software project doesn’t exactly conform to the organisational standard.
The funny thing is – what we are doing is currently working whereas the previous methodology (even allowing for other influences on the project) wasn’t. I’ve been in this situation before, quite often organisations buy into one particular project management methodology – they even hire experts in its application to guide their staff in its use on an ongoing basis. Its a huge $$$ investment.
Then – into my head poped a term – SunkCostDrivenMethodology. Its very similar to the SunkCostDrivenArchitecture that Martin Fowler documented. I think we have a meta-anti-pattern here.