throwafed98

The Playbook is helpful. So is the DoD’s Detecting Agile BS. More publish references similar to these that can be presented to management. Another Avenue would be to engage GAO and OMB in order for their reports to align with above. Thank you!

Contractors can also be part of the problem. Very few contracting firms with access to blanket purchase agreements are willing to dump proprietary tech—as it’s their cashcow. For example, Oracle is huge in the federal gov, and Oracle DBAs are billed at a premium over a dev who can just make Postgres work. Worse, Oracle isn’t the problem rather the problem is some legacy tech or middleware no one has ever heard of that is incredibly fragile and has been hacked into a partially working solution by a vendor over a five year period and management isn’t willing to expend the financial, social, nor political capital to correct and forget about management acknowledging sunk costs.

IMO, USDS makes this worse as someone like Matt Cutts has the cachet to bring in the playbook and get execs to listen. Whereas, I’ve been doing this for 3 years and routinely have to fend off coup attempts as the term “mvp” sounds like a joke to other career employees. As such, it’s often easier to check the box of the federal acquisition requirements and collect a paycheck versus hustling to build a vanilla web app using JavaScript a rest api and Postgres before the checkbox folks shut you down because the baselined version of Jenkins is 5 years old and you installed version 2.26x without a request for change.

So how do we scale this story? Inform politicals and bureaucrats that incentives matter, successful tech start-ups are exception not the rule, sunk costs are real, and you don’t need a catchy name like 18f nor the catchet of celeb dev to right a failing project.