 Started unless people are trying to go to a different room like feel free to make your changes I'm not offended people walk out on me all the time My name is Z and I'll be talking with you a little bit about My company zinc and how we have moved on to a more asynchronous process for our distributed agile teams All of the things that we do are built on this foundation of what we believe makes an effective team The first of these is trust if you can't trust your team members or if your team members can't trust the executives or your customers Then your team will not be effective. It's a very simple formula And and building trust is the most important part of any any team in our opinion The second is respect People who respect one another do better work If I can respect that you are a diligent person who is doing the best that they can Who can quote the retrospective prime directive right now anyone? Yeah Diana So the retrospective prime directive is basically a very simple statement I believe that everyone on my team is doing the best they can with the skills abilities and experiences that they have And that is foundational to having an effective team having this respect for one another the third is alignment Knowing where you're going is much more important than knowing how you're getting there I Have a travel buddy who I sometimes visit and we just pick a destination and I just rely on them to figure out how we're going to do things and We wind up having wonderful adventures because our ideas never work out But we were aligned on this notion of having a delightful delightful trip to Thailand or a Wonderful John to Taipei or whatever And so alignment is a really important part of having a productive team having an effective team freedom Being able to express yourself and do things in the way that you are most comfortable Being free to experiment to try new technologies new techniques new ideas And within the context for alignment is is very powerful. It's a this incredibly motivating thing to be able to Take a task and say you know what I'm going to try and deliver this user story Using just purely functional programming idioms like no no object or not no object-oriented design But no state mutation in between function calls or anything like that And having the freedom to do that and to experiment Is a powerful thing because it means you get new ideas and new practices that get integrated into your teammate into your team much more quickly And finally diversity If everyone is a programmer with a background in computer science, then you're going to have a lot of computer science solutions to problems You may be surprised at this but programming isn't the solution to all problems in the world It's hard for me to say that because I am a programmer, but there's lots of problems that are solved