forked from 18F/technology-budgeting
-
Notifications
You must be signed in to change notification settings - Fork 3
/
mkdocs.yml
41 lines (38 loc) · 1.75 KB
/
mkdocs.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
site_name: De-risking custom technology projects
site_url: https://how-to.usopendata.org/
site_description: A playbook for state budgeting and oversight
site_author: Robin Carnahan, Randy Hart, Waldo Jaquith
copyright: Published under a Creative Commons Zero license. No rights reserved.
repo_url: https://github.com/waldoj/technology-budgeting/
docs_dir: docs/
site_dir: site/
nav:
- Introduction: index.md
- Basic principles of modern software design:
- Introduction: basics/index.md
- User-centered design: basics/ucd.md
- Agile software development: basics/agile.md
- Product ownership: basics/product.md
- DevOps: basics/devops.md
- Building with loosely coupled parts: basics/loosely-coupled.md
- Modular contracting: basics/modular-contracting.md
- Plays for budgeting and overseeing tech projects:
- Think about risk in a new way: plays/risk.md
- Procure services, not software: plays/services.md
- Beware the customized commercial software trap: plays/cots.md
- Require demos, not memos: plays/demos.md
- Hire tech talent in-house: plays/hire.md
- Minimize the cost of change: plays/cost-of-change.md
- Measure success based on iterative outcomes, not project milestones: plays/outcomes.md
- Limit total spending: plays/limit-spending.md
- Limit contract sizes: plays/limit-contracts.md
- Fund systems, not monoliths: plays/systems.md
- Expand your vendor pool: plays/vendor-pool.md
- Share your software: plays/share-software.md
- Budget for software as an operational expense: plays/operational-budget.md
- Ask technical questions of agencies: plays/ask-questions.md
- "Appendix A: Questions to ask": appendix-a.md
- "Appendix B: Sample Quality Assessment Surveillance Plan": appendix-b.md
theme: readthedocs
extra_css:
- 'custom.css'