Mirrors/inspec
2
0
Fork 0
mirror of https://github.com/inspec/inspec synced 2024-11-23 21:23:29 +00:00
Code Issues Projects Releases Packages Wiki Activity

Team working agreement - Estimation (#4735)

Browse source 
Team working agreement - Estimation
This commit is contained in:
Clinton Wolfe 2019-11-26 13:33:04 -05:00 committed by GitHub
commit 0b9903bf91
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
inspec_team-working_agreement.md
View file

@ -39,6 +39,11 @@ While the key audience of the working agreement is the Chef InSpec product and e
* When working on a contribution, we create a short-lived topic branch that contains the topic contribution.
* Naming convention: `<initials/name>/<shortname>`
* Remember when creating an issue to add plenty of context - even things that are "obvious". Depending on when the issue is addressed, you may not be the one working on it so giving context to the assignee is important.
* When estimating work, we use story points as follows:
* Estimates are generally to be made by the engineer doing the work and can always be revised by that individual. No one will ever be expected to work to an estimate created by another.
* Story points are consecutive integers, 1,2,3,4,5...
* Story points have a concrete meaning on this team: the rough number of work days that the engineer doing the work believes it will take to complete the work, from start to merge.
* A work item estimated at more than 5 days should go directly into Breakdown to be decomposed into smaller tasks.
## Issues
* __SLA: 3 business days__