Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Product Design: when we reach capacity (#28330)

Browse source 
@eugkuo and I realized it's important to design further out than 1
sprint. Even when we reach capacity. To do this, we can convert user
stories on the drafting board to air guitars.
This commit is contained in:
Noah Talerman 2025-04-17 11:24:09 -04:00 committed by GitHub
parent eb43de817d
commit b7ac7afafc
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
handbook/product-design/README.md
View file

@ -80,6 +80,7 @@ Additionally:
- If the story has a requester and the title and/or description change during drafting (scope change), notify the requester. The customer DRI should confirm that the updated scope still meets the requester's needs.
- Each [product group](https://fleetdm.com/handbook/company/product-groups#current-product-groups) stops drafting once they reach engineering capacity for the upcoming engineering sprint. This way, we avoid creating a backlog which causes us to spend time updating soon-to-be stale designs. It's up to the product group's Product Designer to stop drafting and shift their focus to the following tasks:
- Wireframing for air guitars. This way, we can see further ahead and make better design and engineering decisions.
- Dogfooding: pick up any issues in the "New requests" or "Ready" column on the 🍽️ Dogfood board
- Run back through the test plan for unestimated user stories and make sure they're as good as we think they are
- Go through the Fleet UI and look for bad/inconsistent text