racexp: focus on features
noahehall opened this issue · comments
add copy related to the focus on features, not points
- everything is related to features, fk points, and assigning arbitrary points to incomplete deliverables to win second place trophies
- its a paradigm shift on changing the metric from points delivered, to features consumed by users and impact being measured by product
- keep the focus on
- features
- managing the team winning races
- drivers groove and keeping the team in their groove, whatever that may be for an individual driver
- each race being a deliverable feature, dont break it down smaller than a deliverable feature
- nothing should be merged to develop that isnt a fkn deliverable feature
- building a race team that can win races
- we should understand our product in a such a way that everything is positioned from the perspective of a feature
- feature delivery estimation should be based on each individuals swimlane, rooted in historical data and not arbitrary point estimation
- status quo:
points / duration->trend line - racexp:
- slow lane:
total features delivered / duration->trend line - groove:
total features delivered / duration->trend line - fast lane:
total features delivered / duration->trend line
- slow lane:
- the delivery expectations for slow lane, groove, and fast lane will differ for each driver based on there own capabilities
- e.g. the difficulty and speed for my javascript GROOVE is far different than it is for bujilding a webapp in binary
- status quo:
- this pattern requires more thought because the complexity of product mgmt increases but thats just
the second law of thermo dynamics- the benefits outweigh the cost of the learning curve
- the focus changes
- from:
- managing points in a sprint
- treating point delivery as a proxy for feature delivery
- to:
- understanding feature delivery deadilnes
- assigning features ( races ) to drivers (developers) who historically can meet those deadlines
- managing drivers swimlanes
- from: