2) Team Culture Rules / Constitution
The team culture or constitution helps the agile team charter establish the handling of activities and how a team will ultimately collaborate and work together. At the heart of these culture rules is the Agile Manifesto’s principles, which discusses project development processes through small innovations and team collaboration at a high level.
Anjuan Simmons, the Agile Project Manager at Assemble Systems and a Certified Scrum Master and owner of AnjuanSimmons.com, prefers to use a Code of Conduct and Constitution document instead of a charter because an agile team charter finds its roots in the waterfall methodology, an outdated method of project management. However, his Team Constitution fits nicely into our full charter with regards to culture:
The code of conduct or culture rules of your agile environment establishes how the team will communicate with one another. This is an important element to ensure each member is respected and their ideas are heard.
Here’s Anjuan’s Code of Conduct:
You’ll also see some rules that discuss the frequency of meetings, attendance requirements and, if minutes are taken, when they’ll be sent out.
Overall, the goal of your agile charter is to build an awesome product for your end-user that solves a problem by keeping your team focused. Everybody’s agile charter is a little different, and some people, like Anjuan, choose to call it something completely different. Regardless, you need a foundation for your project team to ensure that everyone is moving in the same direction in a quick and respectful manner that solves the end-user’s problem.
"Why an Agile Team Charter is Essential to Success"