Team Working Agreement
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
Still loading...
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
How To Use This
2
This is a starter set of team working agreements for production phase projects, including defaults. We expect each team to customize as appropriate to their team.
3
1. Make a copy of this document (File->Make a Copy) and rename it something like "X Team Working Agreement"
4
2. Meet as a team to customize the agreement to your team. Where possible, include the client in this discussion.
5
3. Store your finalized agreement here:

(Note that you may need to choose "Add to My Drive" for the folder before you can save your agreement there.
(link to where team agreements are kept)
6
4. Where appropriate, include links to specific tools/sites/documents that support this (e.g. Pivotal Tracker points to specific project)
7
5. Review and update your customized team agreements regularly as part of the team retrospective process.
8
6. You can share your individually customized team agreement with the client via Google Drive sharing.
9
10
11
Process Overview
12
Agile Process StyleScrum/XP
13
Iteration Length1 week
14
20% TimeYes
15
16
Ceremonies
17
Stand UpDaily at 10am ET via videoconference
18
Pre-IPM MeetingMondays at 10am ET with PM, engineering and design leads
19
Iteration Planning MeetingMondays at 10am ET via videoconference
20
Demo and OKR ReviewFridays at 4pm ET via videoconference
21
RetrospectivesEvery other Thursday at 4pm ET for 60 minutes with notes saved in Google Drive
22
Roadmap PlanningOnce a month
23
24
Communication/Tools
25
Project DiscussionSlack
26
Document Sharing / Artifact SavingGoogle Drive
27
Story ManagementPivotal Tracker
28
Design ResearchTrello
29
Roadmap PlanningPhysical board with cards (photograph and email / store in Drive)
30
31
Typical Working Hours
32
Team Overlap Time11am-5pm eastern
33
Team Work Day9am-6pm local time
34
35
User Research
36
Customer InterviewsAt least 2 individuals, bi-weekly; more for bigger initiatives
37
Usability TestingPrior to any major change
38
Pre-Build ExperimentsFor all major new feature sets
39
40
User Stories
41
Ready For Estimate
User story identifies:
- business outcome desired
- acceptance criteria
- identification of out of scope elements where needed to avoid confusion
- if relevant: UI assets ready
42
Primary user story writerproduct manager
43
Primary chore writerAny team member
44
Primary bug writerAny team member
45
Prioritization byproduct manager, open for debate in Pre-IPM and IPM
46
47
Development
48
Pair ProgrammingFlexible
49
Testing expectations- Test Driven Development
- Unit Tests
- Integration Tests
- Continuous Integration
50
RefactoringContinuous (Red-Green-Refactor model)
51
Git Branching ModelGithub flow
52
Merge PolicyIndependent reviewer merges based on pull request
53
Ready for pull request when
- Acceptance criteria met
- Tests written/passing
- Primary development branch merged in
- All tests passing
54
55
Work In Progress Limits
56
Backlog SizeCurrent iteration plus next iteration
57
Icebox Size20 stories
58
In Development1 story per pair
59
Waiting For Acceptance4 stories
60
61
Deployment
62
Release cadenceAnytime, upon product owner acceptance
63
AcceptanceDeployed in staging, tested and signed off on by product manager
64
Deployed byDevelopment team or product manager
65
Production supportnone
66
67
68
Additional Agreements
69
Assume good intentions but always be on the lookout for process improvement opportunities
70
Be present with each other even when working remotely
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Sheet1