Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    Dare I say you've never worked for a company that makes it's money from Government contracts. (edit) You did say Commercial software.. My statement is meaningless now. Commented Sep 6, 2011 at 17:48
  • @Andrew Finnel: The truth is so painful, on so many levels. Commented Sep 6, 2011 at 17:52
  • 2
    @Andrew - I have worked to DOD2167. It was horrible and unproductive as it was practiced. Later I worked for another company that is doing agile development for the government with frequent deliveries. The client is wildly happy. They had a useful application in six months and get new features quarterly. Commented Sep 6, 2011 at 17:57
  • @Andrew I have over 2 years of experience in US DoD work, as a government employee and as a contractor. Agile methods are being adopted. One team I worked on was actively using Scrum, producing "just enough" documentation "just in time". Yes, documentation (even "just enough" documentation) is significantly more extensive than many other places, but that's typically driven by the number of involved parties (contracts can change hands, other parties can develop other systems, and so on) and/or the safety or life criticality and importance of the systems being development. Commented Sep 6, 2011 at 18:01
  • 2
    @Andrew it's not just governments. I've seen 40 pages specifications for "products"; normally can you select everything from this table and give it to me pipe delimited please. No one can ever be bothered to read them... Commented Sep 6, 2011 at 18:29