Follow IW:
Comments
Newest First | Oldest First | Threaded View
Agreed in full, but...
One of the things we should get out of the problems with federal software procurement is a sense of the dangers of overreliance on outsourcing (we should get that out of the Snowden incident as well). Organizations typically employ a fair number of intelligent people with good ideas and not all of them are managers. And unlike contractors or consultants, regular employees have invested part of their working careers in the organization and are likely to be there to pick up the pieces when the contract is finished. Ergo, the regular IT staff in both federal agencies and elsewhere should have the freedom to experiment and develop programs and systems that help them do their own jobs better and help the front line employees do their jobs better. IT makes sense to outsource for big ticket items, but the careerists should be actively involved in developing the specifications, and they're the ones who should be administering the systems when they go on line (there's really no valid excuse for outsourcing system administration in a large organization).
The general principles should be:
1. Contractors should handle temporary needs. Permanent employees should handle permanant ones.
2. Core governmental functions (especially the ones involving the use of force) should always be in the hands of regular government employees (who might be temporary or part time); never contractors.
The general principles should be:
1. Contractors should handle temporary needs. Permanent employees should handle permanant ones.
2. Core governmental functions (especially the ones involving the use of force) should always be in the hands of regular government employees (who might be temporary or part time); never contractors.
How Enterprises Are Attacking the IT Security Enterprise
To learn more about what organizations are doing to tackle attacks and threats we surveyed a group of 300 IT and infosec professionals to find out what their biggest IT security challenges are and what they're doing to defend against today's threats. Download the report to see what they're saying.
White Papers
Current Issue
2017 State of IT ReportIn today's technology-driven world, "innovation" has become a basic expectation. IT leaders are tasked with making technical magic, improving customer experience, and boosting the bottom line -- yet often without any increase to the IT budget. How are organizations striking the balance between new initiatives and cost control? Download our report to learn about the biggest challenges and how savvy IT executives are overcoming them.
Video
Slideshows
Twitter Feed
Everything You've Been Told About Mobility Is Wrong 
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.
Flash Poll
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2017 UBM, All rights reserved
Tweet This
User Rank: Ninja
1/17/2014 | 7:07:02 AM
For government projects and that includes IT projects the procurement rules are designed to spread the wealth. That is why over 50 contractors were in the mix for healthcare.gov. That alone needs a massive effort in project management to have the 25 left hands know what the 25 right hands do. Congress needs to put measures in place where the number of contractors for a project can be reduced to a manageable number. Spreading the wealth is still possible by ranking those who got a deal lower the next time a project is up for bid. The UK government already put measures like this in place and has most IT projects succeed. But I guess the US will continue using Europe simply as whiping boy rather than as source of knowledge...