I’m cleaning out old lingering drafts. This one’s on why I dislike Team Charters. Recently an email came in asking about writing team charters. I’ve worked at a number of companies that asked teams to write charters, and I think it’s an interesting project. That said, it’s not a project I’d generally prioritize. If you pushed me on this topic, I’d probably suggest you write an engineering strategy document from the perspective of your team. A few thoughts on what team charters try to solve, and then why I think they’re generally not very useful.
Review: Team Topologies
Many organizations are struggling with their business agility transformation. One of the reasons is the way they have organized their teams. The focus was probably on efficiency and if these teams …
Adopt and scale Team Topologies: platform-as-a-product, templates, more. — Team Topologies - Organizing for fast flow of value
Accelerate value with Team Topologies: measure cognitive load, define team boundaries, apply inverse Conway, readiness assessments, and more for fast delivery.
Case Studies — Team Topologies - Organizing for fast flow of value
Examples of Team Topologies used in industry
Outline – Team knowledge base & wiki
A modern team knowledge base for your internal documentation, product specs, support answers, meeting notes, onboarding, & more…
[Proposal] WG for group/community standards and infrastructure in ATProto
TLDR: I’m proposing a working group to develop shared interoperable standards for community infrastructure within ATProto. Many teams are independently making foundational design decisions about group/community membership, governance, and infrastructure. Without coordination, a de facto standard will calcify from momentum rather than deliberate evaluation of the ranges of community needs. I provide initial questions and principles to start discussion. Many people, apps and projects in developme...
MiniApps Working Group Charter
The mission of the MiniApps Working Group is to produce specifications that facilitate the development of interoperable and robust MiniApps.
Technical Charter
This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, Open Responses (the “Project”), an open, vendor-neutral specification for large language model APIs.
How to manage a remote team | Zapier
If you want some ideas on how one team has set up their team to be successful at remote work, then stick around. This chapter is for you. Read more.
Optimize Onboarding
A guide to scaling product & engineering teams from $0 to past $100M ARR
Bye Bye Velocity! Kanban metrics as an alternative to story points & velocity.
cooperative/Formation Documents at main · NorthskySocial/cooperative
Information about our Cooperative. Contribute to NorthskySocial/cooperative development by creating an account on GitHub.
Shepherding v3.1
For open source projects, it can be difficult to find balance between a number of factors: the free time of contributors, the desires of the communities using the project, the ability to on-ramp and mentor new contributors, and to provide necessary guidance and feedback. The Rust Project, and multiple sub-teams and working groups have found success in use of the RFC Process for making informed, high level decisions. However, the RFC process does not address the work necessary for exploratory projects before a decision is made, the work necessary to implement made decisions, or the work necessary to maintain and overhaul parts of the projects in the long run. To address these needs, I'd like to propose a general concept and approach called Shepherding, which aims to assist maintainers of these projects with this aspect of managing the project. By enumerating core goals and putting a name to concepts, but specifically NOT mandating every aspect of implementation, I hope that this technique can be applied across many teams inside and outside of the Rust Project. The "Shepherding v3.1" name comes from a blog post written by Niko Matsakis titled Shepherds 3.0, which also does an excellent job describing the motivations regarding these efforts. This post instead makes a few clarifications and additions to the 3.0 post, and aims to be a "reference manual" for the concept, defining terms and important goals, rather than discussing motivations. Discuss on Reddit Discuss on Twitter
TeamTopologies/Team-Topologies-Community-Materials
A list of materials relating to Team Topologies (articles, tools, canvases, etc.) generated by the community.
The Delightful Storybook Workflow
How productive teams get the most out of Storybook
Building Growth: Product, Process, and Team | Reforge Blog
Reforge drives team performance, with the most actionable learning from vetted operators that your team will actually use and apply.
