To date, there has been minimal focus and attention on addressing the largest culprit of poor acquisition outcomes: inadequate requirements definition.
Big government IT is broken and (slowly) dying. Too many projects cost too much and don’t actually deliver for the American people. In the face of greater budgetary pressure and higher citizen expectations, government buyers, program staff, and IT managers must change their approach.
Several employees across different levels of government suggested one of those primary departments that proves to be a roadblock is IT.
Brig. Gen. Greg Touhill said that his concerns stems from grouping the Defense Department’s (DoD) cybersecurity assets in one place.
The Air Force’s investment in DevOps means delivering critical IT functionality to airmen within hours and days instead of years.
In the spring of 2018, OMB released a memo instructing agencies on steps they need to take to comply with the White House’s Category Management initiative. Here’s what agencies should do.
Insight into things you should know.
To maximize the potential of the cloud, state and local departments need to centrally manage their policies and procedures that should apply to all systems.
Although the mandates surrounding operational effectiveness are all intended to promote the adoption of private-sector best practices, it is not always clear how best to implement them within the federal environment. This creates an interesting opportunity for forward-thinking leaders to design implementation approaches that will work best for their environment.
In most IT contracts the first phase requires the contractor to develop a set of requirements. If the requirements weren’t known when the Request for Proposal (RFP) was written, how can we expect a valid bid in the contractor’s proposal?