Skip to content
This repository has been archived by the owner on Dec 8, 2017. It is now read-only.

Hypotheses

Jump to bottom
Michelle Hertzfeld edited this page Jan 25, 2016 · 15 revisions

Hypotheses

Reusable tools

  • We believe that many of the tools we build
    Will be really useful for people who work at a variety of organizations
    We will know that we are right when TBD

  • We believe that surfacing those tools, writing about them more, and identifying the parts of our work that are generic
    Will TBD
    We will know that we are right when TBD

  • We believe that decoupling them from the applications we developed them for
    Will make it easier for others to reuse them
    We will know that we are right when TBD

Code health

  • We believe that: surfacing metrics on %age of passing builds; %age of testing coverage; existence of linting; automated code quality diagnostics score; dependency status (systems that track if your dependencies are current, and secure)
    Will: enable us to identify the pain points we should address first, or the projects most in need of assistance
    We will know we are right when: we see product leads and 18F folks using the surfaced data to track project health

  • We believe that: partnering with project leads
    Will: enable us to identify the pain points we should address first, or the projects most in need of assistance
    We will know we are right when: we get actionable feedback

  • We believe that: resolving issues identified by our metrics
    Will: ensure code quality; improve the team’s ability to deliver features quickly and at high-quality; ensure sustainable development velocity
    We will know we are right when: the team expresses confidence in making changes to code

Clone this wiki locally