Agile Contracting
Started by cwilliams · Feb 22, 2013 · 11 replies
- cOriginal post
cwilliams
Feb 22, 2013 · 13y ago
With increasing interest in agile project management, I'm seeing increased concerns that the normal contracting process won't support this method of product development. Is that a real concern? Does anyone have experience with this issue that they could share?
- G
Guest Vern Edwards
Feb 22, 2013 · 13y ago
What is the "normal" contracting process, and why wouldn't it support agile project management?
- D
Don Mansfield
Feb 22, 2013 · 13y ago
"Agile contracting"? I sense a new fad. Just wait til the policymakers hear someone speak those words.
- F
FAR Fetched
Feb 22, 2013 · 13y ago
I use "Dexterous Contracting" to handle Agile Project Management.
- G
Guest Vern Edwards
Feb 22, 2013 · 13y ago
Agile Contracting:
http://www.agilebok....racting_Methods
http://www.cutter.co...h/apmu0617.html
http://www.infoq.com...agile-contracts
http://www.cornelius...ile-contracting
http://agile.dzone.c...ile-contracting
http://www.twobirds....nt projects.pdf
There's a lot more. Don't tell OFPP or DPAP.
- F
FAR Fetched
Feb 22, 2013 · 13y ago
Okay, my serious response. This isn't a method of 'Contracting' per se but more of company's business processes.
- s
shinaku
Feb 22, 2013 · 13y ago
I would like some of these socks with support.
- B
Boof
Feb 22, 2013 · 13y ago
I read several of the articles and it made my head hurt. And I still don't understand it. Maybe I am dense but I probably need a sample SOW/PWS and a sample pricing structure to get it.
- a
apsofacto
Apr 16, 2014 · 12y ago
Hi, Boof.
I'm researching this myself- the first step seems to be that you just acknowledge that you will never be able define your requirement sufficiently in advance, and are therefore paying your Contractor by the hour (or on a cost reimbursible basis). I don't understand why the normal procurement process can't accomodate this- it seems very simple. There is probably an art to packaging the work via task order that I'm not fully appreciating, but again, nothing that the current processes cannot accomodate.
There are also some claimed efficiencies in consolidating the deliverables (e.g. annotating source code sufficiently enough to eliminate reports) that I don't claim to understand.
- B
Boof
Apr 17, 2014 · 12y ago
Apsofacto
Gee, I posted over a year ago. I didn't expect this topic to be resurrected. Thanks for the added information.
One thing my Agency is definitely good at is awarding work by the hour without knowing what the outcome should be. Nothing like good old Time and Material for those who don't know where they are going.

- f
formerfed
Apr 23, 2014 · 12y ago
The last two comments about use of T&M/LH or cost reimbursement contracts are right on the mark. One problem is many agencies over reacted to the mandate to reduce "high risk" contract types. Consequently they want to force everything into fixed price arrangements even when it doesn't make sense.
The existing procurement process is fine. The problem is the existing culture puts up artifical barriers - the push for fixed price contracts for everything, the need for requirements to be precisiely defined before starting out, the need for constant government oversight without meaningful involvement, and the need for delivery of detailed status reports and documentation.
- a
apsofacto
May 9, 2014 · 12y ago
Hello, Boof,
I just recently set up an account with the forums here- should have done that long ago!