3 ms·
I'm a fan of repeatability and process. Here's my take on why they don't work: 1) You can't get around that things don't work as planned, and too many method
by mathattack 13y ago
I'm a fan of repeatability and process. Here's my take on why they don't work:
1) You can't get around that things don't work as planned, and too many methodologies assume that things will.
2) It is better to have a PM with A level content and B level process, than the other way around. Professional PMs don't have the intuition to solve the daily project problems, but they're the ones selling the methodologies.
3) Too much focus on tools. Using MS Project to keep the plan doesn't work when 90% of the project doesn't know how to use it.
4) Too much change. Rather than settling on a decent methodology that everyone agrees to, companies keep re-inventing their process every few years.
5) Wrong methodology for the wrong purpose. Waterfall methodologies don't work in research. Agile methodologies aren't the "fits every project" panacea.
I can go on, but you can't enforce excellence with formality. The formality can help outstanding people achieve excellence though.
- fishtoaster 13y ago#1 and #3 sound like they're right out of http://agilemanifesto.org/ http://agilemanifesto.org/
- mathattack 13y agoTyped from memory w/out referencing it. (I'm not agile certified, or anything to that effect)