veyepar: Explicit is Better than Implicit: Making Culture Visible with Team Charters

Author(s):	Christopher T. Miller
Location	Cartoon 1
Date	jul Sat 27	Days Raw Files
Start	12:00	First Raw Start	11:32
Duration	0:30:0	Offset	0:27:21
End	12:30	Last Raw End	12:32
Chapters	00:00 0:03:01
Total cuts_time	24 min.

https://www.pyohio.org/2019/presentations/132
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Explicit_is_Better_than_Implicit_Making_Culture_Visible_with_Team_Charters.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

*Beautiful is better than ugly.* There is more to a team than just throwing people together and telling them to ship code. The culture of the team matters, Not company culture, but the culture and operating rules of the group of people that spend their days together. That culture can be amazing when it is mindfully considered. So how does that happen?

*Explicit is better than implicit.* A team charter is documentation written by a group of people to capture their purpose, their values, their working rules, and their general processes.  Making the invisible visible is the purpose of the team charter.

*There should be one-- and preferably only one --obvious way to do it.* Your team charter will provide an anchor to keep your team true to their ideals, even and **especially** during periods of great stress by providing a written record of how they aspire to work together.

*In the face of ambiguity, refuse the temptation to guess.* Whether it is establishing priorities or onboarding new team members, your team charter will take the guesswork out of the non-code parts of working together.

In this talk, we'll explore what a team charter is, how to create one, and view examples of charters teams have created and used in their day-to-day work.

If you’ve ever joined a new team, you know that there are hidden rules for how the team operates: what they value in their day-today work, what is important to them.

Breaking news: teams are hard. We document our code... shouldn't we document our team's values and ideals?

Comment:

production notes