Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update techfar-online.md #47

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Update techfar-online.md #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions _includes/techfar-online.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
<!-- TechFAR, built from "8 7 14" version -->

<!-- Suggest creating an editorial stylesheet for this document, and related documents. Agile, for example is typically not capitalized in most of the project management literature. -->
# The TechFAR Handbook for Procuring Digital Services Using Agile Processes

## Executive Summary
Expand All @@ -10,9 +10,11 @@ One tool is the [Digital Services Playbook](http://playbook.cio.gov "Link to Dig

The vision for the TechFAR is that it will be expanded in future iterations to address many areas of IT. This edition of the TechFAR is aligned with the [Digital Services Playbook's](http://playbook.cio.gov "Link to Digital Services Playbook") guidance to use contractors to support an iterative development process. In particular, it emphasizes Agile software development [4], a technique for doing modular contracting and a proven commercial methodology that is characterized by incremental and iterative processes where releases are produced in close collaboration with the customer. This process improves investment manageability, lowers risk of project failure, shortens the time to realize value, and allows agencies to better adapt to changing needs. Agile software development is geared towards projects where significant design and development are needed, such as digital services (e.g., healthcare.gov or recreation.gov) as well as internal digital services and business systems. It is not designed to be used for commodity IT purchases, especially where commercially available off-the-shelf items can be used as-is at a lower cost and lower risk to the Government.

In every agency, there are multiple stakeholders who share in the responsibility for achieving successful results from their IT investments and who form the acquisition team, including program officials, IT officials, acquisition officials, and agency legal counsel. Agencies need to ensure adequate resources are dedicated to these stakeholders involved in Agile software development efforts. The TechFAR is designed to facilitate a common understanding among these stakeholders of the best ways to use acquisition authorities in making these investments to level set expectations and maximize the likelihood for success. The TechFAR consists of a handbook, which discusses relevant FAR authorities and includes practice tips, sample language, and a compilation of FAR provisions that are relevant to Agile software development.
In every agency, multiple stakeholders share in the responsibility for achieving successful results from their IT investments. They form the acquisition team, including program officials, IT officials, acquisition officials, and agency legal counsel. Agencies need to ensure adequate resources are dedicated to these stakeholders involved in Agile software development efforts. The TechFAR facilitates a common understanding among these stakeholders of how to bestuse acquisition authorities while making these investments so they can to set reasonable expectations and maximize the likelihood for success.

Definition: The TechFAR consists of a handbook, which discusses relevant FAR authorities and includes practice tips, sample language, and a compilation of FAR provisions that are relevant to agile software development.

This handbook is not intended to usurp existing laws, regulations, or Agency policy. It calls out specific sections of the FAR as examples, but the TechFAR should not be read too narrowly to only apply to the sections specifically mentioned. All Federal agency stakeholders are encouraged to use this guidance. It is a living document; users are urged to provide feedback, share experiences, and offer additional strategies, practice tips, policies, or contract language that may be used to assure that IT acquisitions achieve their desired results. This feedback will be used to inform where additional guidance or reference materials may be appropriate.
Scope: This handbook is not intended to usurp existing laws, regulations, or agency policy. It calls out specific sections of the FAR as examples, but the TechFAR should not be read too narrowly to apply only to the sections specifically mentioned. All Federal agency stakeholders are encouraged to use this guidance. It is a living document; users are urged to provide feedback, share experiences, and offer additional strategies, practice tips, policies, or contract language that may be used to assure that IT acquisitions achieve their desired results. This feedback will be used to inform where additional guidance or reference materials may be appropriate.

## TechFAR Handbook Table of Contents

Expand Down