Document how complexity based weight relates to velocity
Why
As we are planning 15.11, the group was asked if we feel the amount of planned work is realistic.
I want to know how our issue weighting system relates to our velocity as a group in order to make an informed decision about whether the workload is realistic. Because we have a complexity based approach, it's not as simple as summing the values.
What
Document a shared understanding of how our issue weighting system relates to group velocity.
After this Merge Request
In order to be a more effective manager of one, I want to understand the expected/budgeted weight of maintenance, bug fixes, feature development, and documentation. This will allow me to self-serve to align my efforts with the groups goals more efficiently.
- Document how to see the historical and current velocity of the group.
- Document how the weight see the current planning issue weight according to our complexity based approach.
- Document how to know the budgeted weight for each milestone as it relates to maintenance, bug fixes, feature development, and documentation.
Edited by Hunter Stewart