Create Coda views for tracking capacity/workload

[jkarpen]

The goal here is to have views in Coda that we can use to check if people are overloaded going into a new sprint.

[jkarpen]

Initial metrics created but still need to review them with Jason. Meeting scheduled for 4/15 to do that.

[jkarpen]

Initial metrics are created here: https://coda.io/d/Data-Services-Engineering_dY5Oul8-jdi/Workload-Capacity-Metrics_susmb#_lusHv

Metrics are controlled by the assignee and sprint filters at the top of the page.

What's missing is the context of being able to see people's past avg # of issues closed and avg. closed using the multiplier score. This will be useful to show is the work assigned this sprint above someone's usual baseline effort.

I believe the way to add these will be to create a new table built on top of the GitHub Project Items sync which summarizes these counts by person. This will likely need to use the "Assignee is X" columns I created for everyone on the team in the Project Items table. I envision the new table would look like this:

• Person's name (you might manually populate a table with these)
• Sprint
• Issues Closed (use a formula): If "assignee is [person]" AND Status = "Done" THEN count of issues (this is pseudo-code, actual Coda syntax will be a bit different)
• Avg. Issues Closed Multiplier (use a formula): If "assignee is [person]" AND Status = "Done" THEN sum(Multiplier Closed)

Then create a chart on the Metrics page showing the summarized average by person, by sprint.

Once that gets done, work with Jason to create a process for reviewing this each new sprint to make sure nobody is overloaded.

@junlee-analytica

[jkarpen]

Closing this as a baseline set of metrics has been created here: https://coda.io/d/Data-Services-Engineering_dY5Oul8-jdi/Workload-Capacity-Metrics_susmb#_luaNC

There are some additional tweaks I plan to make to improve this which I will create new issues for.