I often tell people that I have been acquiring agile development before I even knew what it was. As a Contracting Officer I am first and foremost a business advisor. So when my customers changed their requirements from traditional waterfall system requirements, to those with evolving technical functionality, I adapted my contracting approach as well. Don't get me wrong, I didn't just magically end up where I am today with regards to acquisition strategies for agile program

Okay you are probably wondering what leadership has to do with agile acquisitions. The truth is, leadership has everything to do with being agile. Trying to change the way people buy what they need or even describe what they need is culture change, and you can not change culture without leadership. I had the great opportunity of going fishing this weekend with one of the greatest leaders I have had the privilege of working for. Amidst the scenic bay view I took the opport

What is the best contract type for agile development? This is sort of like asking which wine to pair with meat or fish? Well that may depend on whether your'e cooking with it or drinking it alongside. Even then it is largely up to the end user. Of course this may be a bit more complicated with regard to contract type since the implications go far beyond your tastebuds. I suppose the best way to answer this question is to start with your options. FAR 16 "Contract Types" provid

The following story (or stories) describe a hypothetical application of both waterfall and agile development/contracting methodologies to a westward journey in an imaginary world where transportation options do not already exist. The scenario, may be a fantasy but the problems faced are all too real. Imagine you need to get across the country and there is no existing transportation (no such thing as planes, trains, or automobiles). So your objective is to “Head West.” Now,