Code / GitHub organization [20 pt for everyone, +3pt for Juli, +2 pt for Kelly, +10 pt for Dana]

[julihcho]

As an HKS student in this class,

I want to meet the technical requirements for the final project,

so that I can learn from the course as it was designed.

[julihcho]

INVEST

• [x] Independent
• [x] Negotiable
• [x] Valuable
• [x] Estimable
• [x] Small
• [x] Testable

TASKS

Juli [3 pt] [Done 1/12]

• Set code organization standard
• Set file structure - overall style.css, styles for each chart, html pages
• Set D3 standards + color schemes

Everyone [20 pts]

• Each dataset with original source data, transformation steps (or python script), and final data that your visualization consumes for each dataset [everyone]
• Follow defined file structure [everyone]
• Not conflicting D3 versions [everyone]
• Some changes to D3 codes [everyone]

Product owner [10 pts]

• Backlog board - all stories we didn't get to ordered from smallest to largest, with smaller ones fleshed out (definitions of done + INVEST) [product owner]
• Sprint 1 and 2 boards - stories we did take on with columns for TODO, DOING, BLOCKED, DONE [product owner]

Scrum master [2 pts]

• Burndown [scrum master]

DEFINITION OF DONE

• A team member to go through this document and check off the requirements met

[julihcho]

Sprint planning notes

• Data transformation can take longer than expected
• D3 debugging can take longer than expected

For individual tasks, each person decides the # of points

[julihcho]

@danmek Please edit the first comment with # of points for the product owner tasks!

[julihcho]

Code / Github Organization Rules are posted here!

[julihcho]

@kellyyun FYI, I actually added a few tasks to my portion and changed my points allocation to 3 pts (from 1pt) - I realized I also needed to set D3 conventions, and that took longer time to figure out.