Posted on 10/22/2013 10:43:31 AM PDT by Cincinatus' Wife
They hired another govenment guy for oversight to fix it.
What the Obamadork really means is that they are “...experts in giving me illegal funding under the table.”
He is an incompetent, undereducated, technically illiterate piece of excrement.
Slime, he is, pure slime.
LOL.
Of course.
AT BEST, the next layer is ready to seamlessly interface with that front-end. If they change the front-end (and that's what they're struggling to do) then they will mess up the interface to the next processing layer.
Fixing the current problem will both create and reveal the next layer of problems.
We are multiple iterations away from having anything that might function.
What typically happens when you crank the pressure on IT guys up to 11 is that they’ll build a Hollywood Set App that has the look and feel of working, but is all done with dummy data and does not actually link-up to any working system. Just like the buildings on a movie lot have no back or sides.
Keeps the heat off your back for at least a little while longer.
You clearly know what you’re talking about. If your assignment were to fix it, how would you approach it?
But before starting over, they need to debrief the low level programmers and ask "What did we do wrong?" The worker bees tend to know the fundamental mistakes either when they are made or shortly thereafter -- but management doesn't want to hear about it (they don't have time to do it right, they'll just take the time later to fix it).
A debrief of the existing team would likely reveal a better architectural and organizational approach for the next attempt.
... and covering up.
IT projects have a surprisingly high failure rate. Some analysts suggest that as many as 1/3 of all development projects fail to reach a successful rollout. You can be sure that a project with 41 contractors and a gubmint official as the contract officer will be amongst the 33 percent. It’s like trying to re-architect a skyscraper when you’re building out the top floor.
Agreed but the problem usually isn't the IT team. Most of the time it's an uncertain and changing scope of work that kills a project. There have been reports of constant changes right up to the release date for HealthCare.gov.
A review of internal architectural diagrams obtained by the AP revealed the system's complexity. Insurance applicants have a host of personal information verified, including income and immigration status. The system connects to other federal computer networks, including ones at the Social Security Administration, IRS, Veterans Administration, Office of Personnel Management and the Peace Corps.".......... Insiders who worked on US health website describe high stress, complaints about major problems
. . . but you have to admit: it has certainly CHANGED THE SUBJECT !
Like WHERE HAS BENGHAZI GONE ?!
That makes way too much sense for government. I’m glad you’re on our side.
I’m not an IT guy but I have extensive management experience. Your approach would be spot on
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.