Collaboration over Contracting? How to Really Do Agile Contracting in Government

During a 3 day workshop, 18F can take clients from concept to solicitation. This presentation from years of work while at 18F gives the audience an overview of best practices learned working with Federal, State, and local clients on IT acquisition contracts of all sizes. If we can do it, so can you. We'll provide best practices for how to merge modern contracting principles with agile concepts to enable agile acquisition enabling actual development with real world examples.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

Dynamic lecture outlining major principles and methods. Usually there are so many shocked questions from disbelief that it leads to an interesting back and forth with many knowing chuckles.

Learning Outcome

Become equipped with tools and samples to be able to use at your agency or advise agencies on how they can better structure the acquisition process and artifacts to enable agile.

Target Audience

Anyone who works for a government agency or anyone who is with a company that does work with Federal, state and local governments.

Prerequisites for Attendees

None. If you've done true agile but have tried to do it in government but run into issues with acquisitions and contracting this is for you.

schedule Submitted 10 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  10 months ago
    reply Reply

    Hi, Mark,

    Your teaser abstract may be sufficient to attract significant interest, given that writing Agile-friendly contracts is so hard to do. You might consider expanding it a little to give prospective attendees a little more detailed understanding of what they'll learn in this session.

    As a reviewer, I want even more detail on what you'll be presenting. Your outline/structure doesn't say much about the content. I read your article "Improving government outcomes through an agile contract format," but it is an article, not a description of your talk. And it left me questions, such as how much agility are you achieving if you need to specify your product backlog in your Statements of Objectives? I've had clients who are struggling with writing multi-year contracts where the requirements are not known at contract time, but will be discovered over the contract in interaction with agency "business owners."

    The outline/structure is the place where you sell your session to the reviewers. Help them recognize that you'll deliver on your abstract. Give them details about the content and the way that you'll present it to convince them that you'll do a good job.

    See also https://threadreaderapp.com/thread/1028714041349263360.html for an independent description of submitting a successful proposal.

    - George, AgileDC Program Chair