Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

Overheard at the watercooler yesterday: "Scrum has no place in defense contracting."

I tend to disagree in the sense that I believe Scrum can be tailored to work in many scenarios and I can see defense being one of them. This sparked a huge debate amongst my colleagues (many of us work in defense contracting) with a fairly even split for/against.

To make this a proper question: Has anyone successfully used (or has experience working with) scrum in a defense contracting situation? What worked well, what didn't work well and what (if any) modifications to vanilla scrum did you do?

share|improve this question
2  
Agile strives to remove waste. Organizations trying to succeed with agile must be aligned with that goal. Political organizations tend to have other priorities. –  Martin Wickman Aug 11 '11 at 7:27

1 Answer 1

"Scrum has no place in defense contracting."

In my experience, the main impediment is the customer. Most government agencies have the waterfall model in their DNA. Even contracts are done in waterfall phases -- first we'll fund the requirements, then the design, then implementation. In classic waterfall theory they may even think they can get different companies to do different phases.

There's ways to get around that though IMO. Do an upfront reqs and design like waterfall, then in implementation break requirements up into iterative user stories. Use internal test/expert users evaluate each iteration. Depending on the customer, they may or may not be interested in participating. Not pure scrum, but it may be the best you can do.

share|improve this answer
2  
I worked as an intern for three teams at an Air Force Reseach Laboratory facility, once in developing production software, once in rapid prototyping, and a third time in verification and validation of contract work. Both development positions were agile. In fact, the production position was very close to Scrum, with less customer interaction (software delivered every few iterations, customer on-site every 3-6 months), and this was in 2006. I agree that customer buyin and understanding is the biggest problem, but some government agencies (or at least teams) are indeed embracing Agile methods. –  Thomas Owens Aug 10 '11 at 12:37
    
@Thomas Owens This comment would be a good answer. –  Hugo Aug 10 '11 at 18:54

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.