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

Jump to bottom

Create derisking-guide-update.md #4083

Merged
merged 2 commits into from
Sep 12, 2024
Merged

Create derisking-guide-update.md #4083

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a967dd
Create derisking-guide-update.md
ameliaswong Aug 24, 2024
da22482
Create derisking-guide-update.md (#4102)
ameliaswong Sep 12, 2024
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
33 changes: 33 additions & 0 deletions content/posts/2024-09-12-derisking-guide-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
title: A revised and expanded guide for de-risking government technology projects
date: 2024-09-12
authors:
- amelia-wong
tags:
- best practices
- how we work
- lessons learned
excerpt: |
New content on vendor management and a streamlined structure make one of 18F's most popular guides even more useful for government staff.
image:
---

Today we launch a new version of the [De-risking Government Technology Guide](https://guides.18f.gov/derisking-government-tech/), its first update since being published in 2020. Find all the recommendations from the original guide’s two parts—the State Software Budgeting Handbook and the Federal Field Guide—now in one unified package. Plus, there's a new, in-depth section on vendor management!

Government technology projects face challenges to successful delivery from budgeting through post-award. To lower risk of failure at any stage, the guide offers methods, models, and examples that reflect:
- Best practices in modern software development
- 18F’s experience working with federal and state partners
- Input from state employees

Topics covered include:
- The differences and trade-offs between commercial and custom software
- Key principles for effective custom software development
- How (and why) to buy custom software development services using performance-based services contracting
- How to work with a vendor development team to deliver human-centered software quickly

These changes respond to current government agency needs. As part of the Office of Management and Budget’s [Facing a Financial Shock initiative](https://www.performance.gov/cx/life-experiences/facing-a-financial-shock/), an 18F team talked with state employees about challenges to procuring and developing state benefits technology systems and possible improvements. Staff expressed a strong desire for federally authored resources about managing technology projects and enabling successful vendor performance. The revised guide is a resource for both.

The changes also reflect the core 18F value to iterate. The guide's original authors hoped it would be revised over time. As we're able, we'll continue to do so.

Check out the [new guide online](https://guides.18f.gov/derisking-government-tech/) and in [PDF](https://guides.18f.gov/assets/derisking-government-tech/dist/18f-derisking-guide.pdf). Share it around. Suggestions, questions, and feedback are welcome! Please reach out through the [18F Guides GitHub repo](https://github.com/18F/guides/issues/new/choose).

Loading