Agencies can ward off lousy software developers and attract better ones by owning copyright, publishing open source, and issuing smaller contracts.
There are some enormously compelling arguments in favor of agencies preemptively publishing source code, which results in reduced cost, increased trust, and higher-quality results.
Scrum-team years give program teams, budgeting, procurement, and oversight a common currency of understanding.
When an agency principal lacks the knowledge to understand and control major software projects, they are handing their control of the agency to some consulting firm’s project manager.
An Agile vendor team cannot be successful unless the agency has prepared for them.
When presented with a disastrous, multi-year, failing, mission-critical software project, a governor will double down on the failing strategy. Here’s why.
Government software becomes vastly better when it’s procured as open source. Normally, government buys closed-source custom software. Government never looks at the source code. The public can’t inspect it. Is it any good? No, it is not. There is no incentive to make it good. In fact, there’s a perverse incentive: hard to maintain means …
Hey, competent tech folks: your country needs you. Your knowledge, your experience, and your connections can improve the United States for everybody. I’m not asking you to go work for the federal government. I’m not asking you to go work for a non-profit. I’m asking you to become a government technology vendor. I want you to sign up at …