To be fair... I have worked on many software projects in my life and have also worked with government software projects. A simple fact of life is that government funded software projects are only given to blood sucking leeches that intentionally underbid and lie their asses off about delivery schedules. Legitimate software houses who actually can plan projects and meet schedules are never evaluated.
I'll let you in a little secret. Plans and schedules mean exactly dick on government software projects. You'll have idiots and imbeciles with no technical experience making major changes a week before a deliverable. You'll get reports that your software doesn't work when deployed, and find out a week later that they didn't bother to inform you that they decided to move to a completely different environment. You'll get new requirements on the day of delivery. You'll meet deadlines and won't hear anything for days or even weeks until you get some angry email from somewhere asking why a problem that was never reported hasn't been fixed yet. You'll be forced to use their dev environments, but not given the privileges necessary to actually use them. You'll get countless technical decisions made...without anyone actually consulting the technical team. And I'm just getting started.
It doesn't matter how competent your team may be. If the government side of the project is managed by a bunch of monkeys on meth, you're going to have a bad time. Double that if your company is hell bent on getting their foot in the door that they're willing to bend over backwards just to keep them happy.
And guess who gets tarred and feather when everything goes to hell? I'll give you a hint. It's not that G15 manager who needs a Garmin in order to find where to put the Charmin.
A successful government software project requires competence on both sides. It is a rare circumstance when that is the case.