4 ms·

If working at a major DoD contractor taught me any anecdotal lessons about software development for the government, its that you are basically disqualified, by

If working at a major DoD contractor taught me any anecdotal lessons about software development for the government, its that you are basically disqualified, by logistical means, from making software for the government if the dollar amount in question is anything more than a drop in the bucket for your budget. That may just be a DoD reality, but I wonder how true it probably is for Federal entities. I'm with markus2012 here. I have a profitable product already in place that would give me a significant head start on those requirements, but I'm still not at all prepared to head down that thorny trail.

ww520 14y ago
It's not too bad in my experience. Though in my case, the Federal agency granted the money to a local agency and they were pretty much hand-off since then. I work with the local agency to build the product and they have been great. We set requirements, feature, and schedule together, and they left it to me to manage the entire development process. I convinced them to do a XP-like iterative process to get involved and give feedback. It had work well. If they actually get involved actively with the teams for this competition, I think they will get good result.