Discussion: using Deliverable and Stretch labels
Overview
During a recent Platform planning meeting, discussion emerged on how we currently use the Deliverable and Stretch labels:
- We overschedule the number of issues we mark as Deliverable in each cycle with the intent of hitting ~75% of these in each release.
- Q2's goal is going to be hitting 100%.
In order to accomplish this, we're making a couple of changes to how we plan:
- We're going to reduce the number of issues (more accurately, the aggregate weight of issues we commit to) that we make Deliverable in a given release cycle. We should be hitting 100% of these.
- We're going to use the Stretch label to indicate issues we'd like to start on this release, but are fine with letting them slip and get finished in the following release.
In a given release, we'll need to keep an eye on both 1) issues that are Deliverable for the upcoming release (with a goal of shipping 100% of these), and 2) issues that were Stretch from the previous release (with a goal of shipping ~100% of these).
Open questions
Is there anything worth adding to the handbook on this, or is label usage too discretionary from team to team?