3 ms·
A big reason for this is include that public IT projects tends to have more relaxed deadlines than private sector projects. Private sector projects are often ma
by ToFab123 8y ago
A big reason for this is include that public IT projects tends to have more relaxed deadlines than private sector projects. Private sector projects are often managed by people who has chainsaws fitted to their elbows and that has zero tolerance for delays. There is a degree of flexibility in public IT projects that I rarely come across on private projects.
On the other hands, I have seen more huge project failures on the public sector jobs than on private sector projects. Those elbow chainsaw people often catch fundamental flaws earlier than their public sector counterparts.
Given the choice I would pick to work on public sector projects than private sector simply because the much lower stress level and that you have more time to produce quality;Like the NHS guys has been able to on this project.
Disclosure: I have spent the last 18 years working as systems architect / technical leads on countless large government and private sector projects (web/intranet)
- arctangent 8y agoI'm the tech lead for the NHS website (www.nhs.uk) and I oversee the team who are building this frontend library. I largely agree with what you have written above, however things work very differently now in NHS Digital. Every piece of work we embark upon is based on strict requirements from a commissioning body (typically NHS England or Public Health England) and is managed tightly according to budget and demonstrated realised benefits. We have a highly capable layer of delivery managers who help translate and interpret these "business goals" into things which our agile teams of developers can work towards. It's not perfect, but we're improving all the time. If we fail then the money taps get turned off quickly, and we move onto something else.