I've also heard of contractors selling nearly identical software to multiple agencies and charging each the full price of development (one reason open source has faced opposition), and sometimes decent excel macros can solve the actual problem.
You're totally right that if the incentives don't change, the choices made by execs won't change either. For example, a contracting officer I've met saved their agency a billion dollars by not continuing a failing contract, and was punished (to the point of leaving that agency) because that wasn't what the incentives supported.
How can USDS/18F be helpful to you and others in your position? The messages you list at the end are all true.
Re:USDS Digital Services Playbook
by throwafed98 on Friday January 01, 2021 @12:02PM
(#25604621)
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!
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.