The disconnect between software development and government contracting.

There’s a big disconnect between modern software development practices and government contracting. It can seem intractable, but there is a solution. It’s the job of contracting officers to get government the best value for their money. That means being sure that they’ll get precisely what they need, within budget and on time. Normally, the best …

Never contract for story points.

When contracting for Agile software development services, sometimes contracting officers make “story points” the thing that they’re buying. This is an enormous mistake, on a couple of levels, and nobody should ever do it. Let’s talk about why. First, let’s define “story points.” Agile development teams need to figure out what they’re going to work …

Reduce bids by reducing uncertainty.

When government agencies procure custom software, the price tag is often driven up because the agencies are unwilling or unable to reduce the complexity prior to beginning the acquisition process. The complexity and associated uncertainty is obvious to vendors, so when asked to provide a firm fixed price bid, they’re going to price it for …

Government should procure custom software as open source.

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 …