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

Handbook: Rename emergency drafting to expedited drafting (#12433)

Browse source 
It seems like we’ve been incorporating “emergency drafting” more
frequently into sprint cycles. This totally makes sense given that we
want to be an agile, design-driven company. It might be an easy cultural
win to instead call it something like “expedited drafting” to soften the
dissonance that comes from the sense of being in a constant state of
emergency.
This commit is contained in:
gillespi314 2023-06-21 12:19:24 -05:00 committed by GitHub
parent 1f455055a1
commit befda0d435
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
handbook/product/README.md
View file

@ -48,17 +48,17 @@ Once the draft has been approved:
Learn https://fleetdm.com/handbook/company/development-groups#making-changes
### Emergency drafting
### Expedited drafting
Emergency drafting is the revision of drafted changes currently being developed by
the engineering team. Emergency drafting aims to quickly adapt to unknown edge cases and
Expedited drafting is the revision of drafted changes currently being developed by
the engineering team. Expedited drafting aims to quickly adapt to unknown edge cases and
changing specifications while ensuring that Fleet meets our brand and quality guidelines.
You'll know it's time for emergency drafting when:
You'll know it's time for expedited drafting when:
- The team discovers that a drafted user story is missing crucial information that prevents contributors from continuing the development task.
- A user story is taking more effort than was originally estimated, and Product Manager wants to find ways to cut aspects of planned functionality in order to still ship the improvement in the currently scheduled release.
What happens during emergency drafting?
What happens during expedited drafting?
1. Everyone on the product and engineering teams know that a drafted change was brought back
to drafting and prioritized.
2. Drafts are updated to cover edge cases or reduce functionality.
@ -77,7 +77,7 @@ Product Managers prioritize all potential product improvements worked on by cont
Bugs are always prioritized. (Fleet takes quality and stability [very seriously](https://fleetdm.com/handbook/company/why-this-way#why-spend-so-much-energy-responding-to-every-potential-production-incident).)
If a bug is unreleased or [critical](https://fleetdm.com/handbook/engineering#critical-bugs), it is addressed in the current sprint. Otherwise, it may be prioritized in the sprint backlog for the next sprint. Bugs are never carried more than one sprint. If a bug requires drafting to determine the expected functionality, the bug should undergo [emergency drafting](#emergency-drafting).
If a bug is unreleased or [critical](https://fleetdm.com/handbook/engineering#critical-bugs), it is addressed in the current sprint. Otherwise, it may be prioritized in the sprint backlog for the next sprint. Bugs are never carried more than one sprint. If a bug requires drafting to determine the expected functionality, the bug should undergo [expedited drafting](#expedited-drafting).
> Anyone can [suggest improvements](#intake).