1759e6d388
While I haven't seen this exact story point mapping to expected completion time, it intuitively makes sense from an Agile/iterative dev perspective, and accounts for e.g. longer tasks being disproportionately more uncertain than shorter tasks. Let me know if I got the rationale correct here, as spelling that rationale out feels like a useful thing to have in the handbook, particularly for engineers coming from environments where story points might've been converted more linearly to expected level of effort. --------- Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com> Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Welcome to Fleet
Introduction
The Fleet handbook is the living source of truth for how we run the company. This handbook is open to the world and feedback and contributions are welcome from everyone. Feel free to click "Edit this page" to suggest an improvement anywhere you see fit. (The right reviewer will be automatically notified, and will reply to you promptly. Your change will go live on the website ≈10 minutes after it is merged.)