From f6bb1ada1ddbea4f3b115791b7cc49b42f4829fb Mon Sep 17 00:00:00 2001 From: Aidan Feldman Date: Sun, 7 Apr 2024 18:22:37 -0400 Subject: [PATCH 1/2] fix modular contracting link --- content/derisking/state-field-guide/2-basic-principles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/derisking/state-field-guide/2-basic-principles.md b/content/derisking/state-field-guide/2-basic-principles.md index f9b00e7e..8a25ffbf 100644 --- a/content/derisking/state-field-guide/2-basic-principles.md +++ b/content/derisking/state-field-guide/2-basic-principles.md @@ -100,7 +100,7 @@ Building IT systems using loosely coupled parts, connected by open and available ### Modular contracting -By combining user-centered design, agile, product ownership, DevOps, and building with loosely coupled parts, it’s possible to break up a large, risky contract into a handful of smaller contracts. A contract should be small enough that the agency will have no compunction about giving no further work to a non-performing vendor, replacing them with a new vendor. (See "[Procure services, not software]({{ "/derisking/state-field-guide/#procure-services-not-software" | url }} for how this is done.) The rest of the vendors will continue working, so the total loss of velocity will be minimal. A new vendor should have no difficulty taking over for the old one, since the old one was delivering completed, documented, tested software every two weeks. Another benefit is that small contracts may come in under your state’s simplified procurement threshold, meaning that agencies can write a request for proposals, publish it, and award a contract, all within 90 days or so. +By combining user-centered design, agile, product ownership, DevOps, and building with loosely coupled parts, it’s possible to break up a large, risky contract into a handful of smaller contracts. A contract should be small enough that the agency will have no compunction about giving no further work to a non-performing vendor, replacing them with a new vendor. (See "[Procure services, not software]({{ "/derisking/state-field-guide/#procure-services-not-software" | url }}) for how this is done.) The rest of the vendors will continue working, so the total loss of velocity will be minimal. A new vendor should have no difficulty taking over for the old one, since the old one was delivering completed, documented, tested software every two weeks. Another benefit is that small contracts may come in under your state’s simplified procurement threshold, meaning that agencies can write a request for proposals, publish it, and award a contract, all within 90 days or so. There are vendor teams that specialize in working as we’ve described here. As a rule of thumb, an agile development team of 5–9 people costs between \$1–2M/year, depending on their geographic location. From e13d2b01d097900c503be920b60d47eb320b6362 Mon Sep 17 00:00:00 2001 From: Aidan Feldman Date: Mon, 8 Apr 2024 22:21:14 -0400 Subject: [PATCH 2/2] fix link to "Procure services, not software" --- content/derisking/state-field-guide/2-basic-principles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/derisking/state-field-guide/2-basic-principles.md b/content/derisking/state-field-guide/2-basic-principles.md index 8a25ffbf..8cb1259b 100644 --- a/content/derisking/state-field-guide/2-basic-principles.md +++ b/content/derisking/state-field-guide/2-basic-principles.md @@ -100,7 +100,7 @@ Building IT systems using loosely coupled parts, connected by open and available ### Modular contracting -By combining user-centered design, agile, product ownership, DevOps, and building with loosely coupled parts, it’s possible to break up a large, risky contract into a handful of smaller contracts. A contract should be small enough that the agency will have no compunction about giving no further work to a non-performing vendor, replacing them with a new vendor. (See "[Procure services, not software]({{ "/derisking/state-field-guide/#procure-services-not-software" | url }}) for how this is done.) The rest of the vendors will continue working, so the total loss of velocity will be minimal. A new vendor should have no difficulty taking over for the old one, since the old one was delivering completed, documented, tested software every two weeks. Another benefit is that small contracts may come in under your state’s simplified procurement threshold, meaning that agencies can write a request for proposals, publish it, and award a contract, all within 90 days or so. +By combining user-centered design, agile, product ownership, DevOps, and building with loosely coupled parts, it’s possible to break up a large, risky contract into a handful of smaller contracts. A contract should be small enough that the agency will have no compunction about giving no further work to a non-performing vendor, replacing them with a new vendor. (See "[Procure services, not software]({{ "/derisking/state-field-guide/budgeting-tech/#procure-services-not-software" | url }}) for how this is done.) The rest of the vendors will continue working, so the total loss of velocity will be minimal. A new vendor should have no difficulty taking over for the old one, since the old one was delivering completed, documented, tested software every two weeks. Another benefit is that small contracts may come in under your state’s simplified procurement threshold, meaning that agencies can write a request for proposals, publish it, and award a contract, all within 90 days or so. There are vendor teams that specialize in working as we’ve described here. As a rule of thumb, an agile development team of 5–9 people costs between \$1–2M/year, depending on their geographic location.