Skip to content

Project Timeline

ellenfranceszakreski edited this page Dec 17, 2016 · 3 revisions

This is a rough, subject to much change, timeline for the project.

Roles; Start: December, Finish: January 10, 2017

  • identify the types of work that will need to be done and define roles to be filled.
  • recruit folks to take on those roles.
  • (note that some roles will be added/changed as the project proceeds and we figure out more of what we’ll actually need.)

Prepare Surveyor Questions Start: December, Finish: December 23

Prepare Candidate Survey Questions Start: December, Finish: December 23

Research; Start: December, Finish: January 23, 2017

  • review past surveys to identify surveying features needed/used and other relevant details.
  • interview surveyors and candidates to identify issues, wants, and ideas.

Technology side

Design; Start: January, Finish: early February

  • gather and/or come up with a pile of ideas for features & functions for the project.
  • draw out the comprehensive vision of what the ideal system would look like, based on our current understanding.
  • select a subset of features that will constitute the “minimum viable product” (mvp) for the first release to be used for the 2017 election.

Look for existing tools; Start: late January, Finish: early February

  • review existing tools (e.g., web survey tools) to see if any could be used to meet the mvp.

If using existing tool…

Develop; Start: early February, Finish: March

  • if there is a suitable existing tool, do the customization needed for our application.
  • build any additional things needed to enable the project (e.g., a website wrapped around the survey tool).

If building new tool/platform…

Develop; Start: early February, Finish: early May

  • what goes on in this part will be determined by the design phase’s mvp.

Process Side

In addition to the technology needed for the project, we will also have to develop some human-involved processes to support various project tasks.

Design; Start: January, Finish: late February

  • identify the various human roles in processes for the project (e.g., contacting and supporting community groups to get involved, tracking down candidate’s and their contact information, herding folks to get their surveys in, working with question writers to optimize the questions, etc.…)
  • document those roles in a way that can be used for reference by people who might fill those roles.
  • develop guidelines/directions for people to fill those roles.

Recruit; Start: February, Finish: April

  • get the word out to potential recruits.
  • get people signed up.
  • do any necessary training.

Implement

  • get folks doing the work of their roles.