Skip to content

Project Management

Mark McDonald edited this page Jan 29, 2020 · 3 revisions

Communications

Communications are done via Slack.

Action Items

Action items are reviewed in each meeting before new topics are discussed. New action items are documented and agreed at end of meeting.

Team Meetings

Team meetings are in-person each week. ~2 hours. On-line meetings during week are ad-hoc. Team meetings will review actions and next steps. Each team member will review his/her topic(s) of responsibility in the project and will lead discussions related to that specific area.

Documentation / Web Page

Project documentation will be done as much as possible in parallel to development. Each member documents his/her topic of responsibility.

General Timeline

SETUP (15%)

  • Project Setup / Determine Objective and Scope
  • Documentation Structure and Requirements
  • Repo structure, management and processes

DEVELOPMENT (70%)

  • Initial Data/Model/Software Design - "Master" Design Plan (30%)
  • Weekly Development Loop: Develop->Test->Document->Design (40%)

IMPLEMENTATION (15%)

  • Clean up and fine-tune final design
  • Final Documentation

Roles

Roles will likely overlap in a small group; however, we will try to separate tasks as much as reasonable. Areas to consider for separating responsibilities include:

  • Data handling and design
  • Documentation coordination (web page development)
  • Project coordination (communication, tracking, planning, scheduling)
  • Git repo management / Version management
Clone this wiki locally