2 ms·
I'm not a project manager, and I most certainly haven't been involved in huge IT projects. That said, from my POV it seems a lot of software related IT project
by magicalhippo 8y ago
I'm not a project manager, and I most certainly haven't been involved in huge IT projects.
That said, from my POV it seems a lot of software related IT project failures is often correlated to two factors:
- Doing too much at once. Like replacing 6 different existing specialized systems with a single new one.
- Unwillingness to change the business procedures/workflow to cater to software.
The lure of the single do-it-all system seems strong with certain people. But at least in my experience, one could draw from software engineering and how good software is written as separated modules with well-defined interfaces at the boundaries. If you have multiple systems with good interfaces for data exchange, it's much easier to specialize where needed, and replace outdated or broken pieces.
The unwillingness to adjust the business procedures/workflow to software needs is a huge one. Complex software is fragile. By having complex rules in the business procedures you force the software to be more complex, thus invariably making the software more fragile. If business procedures were changed to be software friendly before the software is written/adapted, the software can be simpler and thus hopefully less fragile.