▲ | Jtsummers 4 days ago | |||||||
One thing that would help, but only help, not solve, is to train the people writing requirements. I've seen so much overfitting. "We developed on a Dell 1234ABC, so that's what we need 200 of when we deliver this to the field." That's not how computers work, but that's how they end up writing requirements. That can even make it into the TO for systems so now they have a drawing of the back of a Dell 1234ABC and the front, showing how it's installed at a desk and cabled up. Once that happens, if the system lasts more than a year, they have to start sourcing Dell 1234ABCs with the same specs. However, that's an item that's no longer sold. So then they switch to maintaining the ones they have, which means a support contractor is hired to staff locations to handle these repairs (because the local IT staff is already responsible for a lot of things, and maintaining obsolete hardware is not their priority). When what's needed is any computer with X GB of RAM, X GB (or TB these days) of storage, and so on. Set the minimum specs, go acquire it from whatever vendor, and move on. It'd cost a fraction of the amount of that multi-million support contract whose entire job is to maintain obsolete computers. | ||||||||
▲ | zbentley 4 days ago | parent | next [-] | |||||||
That would help a tiny amount. The bigger problem, which GP alluded to and which is very, very frustrating to entangle, is the incentives around accountability. Pahlka’s writing puts it better than I could: | ||||||||
| ||||||||
▲ | lmm 4 days ago | parent | prev [-] | |||||||
We get the project management we pay for. You can outsource implementation but you can't outsource accountability; ultimately, the only way to get effective government is to build up project management expertise in-house, and to do that you need to be willing to match the pay and conditions (including but not limited to reliable long-term employment) that skilled project managers could obtain in private industry. |