Skip to content

Tech Deliverables

Jimmy McBroom edited this page Jun 21, 2017 · 2 revisions

Tech Deliverables Roadmap

Iteration 1 (4 weeks, ending 7/28)

Core components

  • Map: points and choropleth, legend, tooltips, and search by street address
  • Data visuals: tables, summary stats, and charts
  • Narrative: “About” page, “Welcome” view with data disclaimer, or similar

Filtering (basic)

  • Category: nested incident types determined by DPD
  • Temporal: month, day of week, and time of day
  • Area: neighborhood, precinct, council district, and city

Data export and print (basic)

  • Link to original Socrata source and download csv of whole dataset
  • Ability to print static summary views

Iteration 2 (4 weeks)

Incorporate feedback from user testing

  • May include: clarifying content in map tooltips, adjusting symbology, etc

Filtering (enhanced, as requested)

  • Draw your own polygon
  • Custom time ranges
  • Comparative analysis

Data export and print (enhanced)

  • Link to and download filtered views of data
  • Improve content, style and layout of print views
  • Add filtering parameters to URL for sharing online

Mobile design

  • Improve default content layouts and styles for mobile users

Iteration 3 (2 weeks)

Incorporate feedback from user testing

Prepare app for production / public launch

  • Write tests and documentation, minify and bundle code
  • Coordinate with web team or others to host files and serve the app

Communication

The tech team will share updates biweekly. At the end of Iteration 1 and 2, we will share a URL for user‐testing. Iterations 2 and 3 will begin after user testing is completed. We assume that DPD will coordinate user‐testing (including participant outreach, scheduling and hosting) and DoIT will support by helping to write test questions, facilitate, and compile feedback. During Iteration 3, we’ll determine a final completion date together as early as possible so that DPD can work in parallel to prepare a communication plan for public launch.

Throughout development, we’ll also host weekly or biweekly “code‐share” type meetings for the project team where we can coordinate development roles, share how we build out features, and ask for help solving bugs. This will be a space for all interested team members to learn about various libraries we use, explain more about the technology decisions we make throughout development, and anticipate technical challenges early on.