4 The Team Working Agreement
This chapter covers
- What a Team Working Agreement is
- Why your team should want their own Team Working Agreement
- What to consider in your Team Working Agreement
- Understanding the meaning of a “living” document
As guidelines are established and things are set in motion, it can get difficult to enforce and remember everything your team may have discussed, debated, and ultimately decided on for your code review. Having an official, public, documented, and referenceable record that your team acknowledges can ease the burden—it could even be the key to many interpersonal issues that crop up between team members.
Can only a document of policies and agreed-upon standards by the team really be meaningful? This chapter aims to show that, if implemented successfully, taken seriously by the whole team, and effortless to change, it may be the greatest thing your team incorporates into your culture.
4.1 What’s a Team Working Agreement?
While its origins come from the Scrum framework (a set of values, principles, and practices that help cross-functional teams deliver products and services in short cycles [1]) and facilitated by product owners or product managers, the Team Working Agreement (TWA) has found a fitting home within engineering teams as well.
A TWA transforms implicit social expectations into explicit enforceable ones. And with the code review process, plenty of expectations—which can turn into annoyances—can and should be handled properly through a TWA.