"Why would they spend that much money on describing the process?" Well the usual hope is to launch software to automate it, which is generally more-or-less impossible, because describing the thicket of exceptions, set-asides, etc that various parties have gotten is beyond us.
-
-
Show this thread
-
This thread inspired by the HN threads on: NYC spends $600 million on payroll system unsuccessfully: https://news.ycombinator.com/item?id=2715410 Canada spends $185 million on payroll system unsuccessfully: https://news.ycombinator.com/item?id=15303555 … Just kidding it was a billion: https://news.ycombinator.com/item?id=16494387 …
Show this thread -
There's a lot of blame to go around in government contracting, but payroll systems (and employee benefits / retirement / etc) is *specifically* destined to fail.
Show this thread
End of conversation
New conversation -
-
-
I worked on a payroll resignation system that eventually succeeded. It was the third attempt at this system. When we started we were given an estimate of 3 months by some exec with no clue. It took about 4 devs 2 years. Despite politics, distrust, sabotage, resistance 1/
-
incompetence, mainframe issues and lots of other stories, we got there. We eventually bypassed the project manager and ran our own agile process under him. The payroll department’s KPIs went down overnight when we finally released, and we found 2/
- 1 more reply
New conversation -
-
-
Ok, but it would have been much cheaper to hire people to literally do nothing except enter data twice for a few months than to fix all the paycheques after the fact when they switch over to a buggy system.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.