Working Agreements---Fluxx Team
Working Agreements---Fluxx Team
| # | WORKING AGREEMENTS | VOTES |
|---|---|---|
| 1 | Team core hours are 8:30 AM - 1:30 AM CST (This gives us the highest overlap time with onshore team) | 5 |
| 2 | Lint your code before PR’s. Everything is done locally for now. We should all be linting and fixing issues prior to pushing. | 6 |
| 3 | Update your user story/task status in the board before the stand-up | 5 |
| 4 | Always comment on the user story/task about any updates, issues or bugs found | 5 |
| 5 | Always add detailed descriptions and steps on how to reproduce bugs | 5 |
| 6 | Pull request approvals should have a minimum of 2 approvers and urgency type. (i.e. critical/urgent, non-urgent. They should also have links to the story or task in the request) | 5 |
| 7 | If there will be deployments or any code changes always let the team know especially when the ticket is still in testing phase | 4 |
| 8 | When development is done, and it is ready for QA testing, a quick demo to QA is recommended as part of the handover process | 4 |
| 9 | Meetings should be recorded to help us keep track of action items | 4 |
| 10 | For emergency leaves or PTO/Sick leaves just mention it on our group chat so everyone is informed | 4 |
| 11 | If the team member is blocked they must inform the team immediately or mention it in the daily stand-up | 4 |
| 12 | Use tags for BLOCKED, NEEDS-REVIEW, NEEDS-DETAILS, HAS-QA-EFFORTS, NO-TESTING-EFFORTS | 6 |
| 13 | The author of the pull request can use the Resolve Conversation button to address comments. When using the resolve conversation button, please include a comment with the relevant details. | |