Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 31

Update drafting handbook to include estimation deadline (#13217)

Browse source
This commit is contained in:
Luke Heath 2023-08-08 15:03:10 -07:00 committed by GitHub
parent 42b1951ea7
commit b43d587d13
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
handbook/company/product-groups.md
View file

@ -50,7 +50,7 @@ The goal of the customer experience (CX) group is to make users and customers ha
| Engineering manager | Sharon Katz
| Quality assurance | Reed Haynes
| Product manager | Mo Zhu
| Software engineers (developers) | Jacob Shandling, Juan Fernandez, Lucas Rodriguez, Rachel Perkins, Eric Shaw, Martin Angers
| Software engineers (developers) | Jacob Shandling, Lucas Rodriguez, Rachel Perkins, Eric Shaw, Martin Angers, Tim Lee
> The Slack channel, kanban release board, and label for this product group is `#g-cx`.
@ -121,6 +121,8 @@ A user story is considered ready for implementation once:
- [ ] [Estimated](https://fleetdm.com/handbook/company/why-this-way#why-scrum)
- [ ] [Scheduled](https://fleetdm.com/handbook/company/why-this-way#why-a-three-week-cadence) for development
> All user stories intended for the next sprint are estimated by the last estimation session before the sprint begins. This makes sure contributors have adequate time to complete the current sprint and provide accurate estimates for the next sprint.
#### Writing a good user story
Good user stories are short, with clear, unambiguous language.
- What screen are they looking at? (`As an observer on the host details page…`)