Planning capacity audit
During the PM & Engineering discussion concerns were raised about feature velocity. The following items were communicated out as engineering requests.
- We should plan capacity for each release based on recent throughput (not using any assumptions about what new headcount will do for throughput). Conduct local retros to hold peers accountable in a safe space.
- Emphasize working through milestone items in priority order, and finishing the most important things before picking up bits and pieces elsewhere. Perhaps measure “release post items per engineer”.
- Investigate POCs and whether they are being used appropriately.
I'd like to start with an audit (not exactly sure what form this takes) of how our capacity planning is done for each group and how work is prioritized. I would like to do this group by group. Also, any POCs being done or done in the last 6 months we should discuss as part of the audit as well. I'm open to ways we can make this as efficient as possible while still gaining some understanding.
Edited by Cynthia "Arty" Ng