Health Data Project Toolkit a Guide for CA Health Data Ambassadors

VI. An Iterative, Agile Process

The California Health Data Project is working closely with CHHS to implement an “Agile Development” process into the work they are doing. The effort is being led by our Statewide Health Data Ambassadors, Ash Roughani and Joel Riphagen.

Originally used by software developers, this new way of thinking promotes adaptability, cross-collaboration and continuous improvements to create products and services that benefit communities throughout the state. In the first phase of the project, the California Health Data team developed an Asthma Data Visualization Product ( using the agile method in collaboration with CHHS. In October 2015 the Asthma product was recognized by Government Technology as one of the 4 Key Takeaways from Code for America’s 2015 Summit.

The goals for the various Health Data projects we’re working on are not only to demonstrate best practices for effective communication through data visualization, but also document an iterative, agile software development process. In other words, the process is just as important as the end product. By focusing on collaboration, we hope to create more durable products, and engage CHHS so that they can learn too, about how to integrate this concept into their own technology work.

This new methodology differs from traditional sequential software development (also known as “waterfall”), where every requirement of a project is decided on before any actual development starts. Agile on the other hand, allows developers to develop software in stages or “sprints,” where they can actually see in real-time how the product they’re creating is working, and make necessary changes based on that.


In agile development, weekly or biweekly sprints are the frequency at which new, working features are released for the purposes of validating with users. At the end of each sprint, a standup meeting (or call) should occur to reflect, adjust, and iteratively refine the product roadmap as a better understanding of user needs emerges across all stakeholders. Because the process involves iteratively determining features as the product is built, it is not advisable to specify interim deliverables at the outset of the project.

Below is an example of the agile development process the California Health Data Project used to create the Asthma Data Visualization Product, that visualizes emergency department visits for asthma by county and zip code.

Sprint 1: Monday, June 29 to Friday, July 10 (2 weeks)

  • Research asthma data and stakeholder needs/use cases
  • Brainstorm 3-5 written data visualization concepts with wireframe examples
  • Initial development exploration to determine feasibility of data visualization concepts

(Slide Deck, 1st Mockup, 2nd Mockup)

Sprint 2: Monday, July 13 to Friday, July 24 (2 weeks)

  • Perform major feature design for up to two data visualization concepts
  • Perform major feature development for one data visualization concept
  • Possible design and development work for additional concepts if feasible under project budget and timing constraints

(First Iteration, Second Iteration)

User Testing: Monday, July 27 to Friday, August 7 (2 weeks)

  • Convene user testing group to collect user feedback
  • Distill feedback and validate/refine product roadmap

(Video: User Tester Training Session)

Sprint 3: Monday, August 10 to Friday, August 21 (2 weeks)

  • Perform feature refinement, product development, and bug fixes
  • New feature development is not included in this sprint unless feasible under project budget and timing constraints

(Third Mockup)

Sprint 4: Monday, August 24 to Friday, September 4 (2 weeks)

  • Perform minor feature refinement
  • Extensive testing across devices and platforms and bug fixes identified through end client review

(Third Iteration)

User Testing: Monday, September 7 to Friday, September 11 (1 week)

  • Convene user testing group to collect user feedback
  • Distill feedback and define minor feature improvements

Sprint 5: Monday, September 14 to Friday, September 25 (2 weeks)

  • Perform minor edits and bug fixes
  • Final delivery to end client

(Fourth Iteration)

Final Product:

Additional Resources