SaaSHub helps you find the best software and product alternatives Learn more →
Ways-of-working Alternatives
Similar projects and alternatives to ways-of-working based on common topics and language
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
awesome-engineering-team-management
👔 How to transition from software development to engineering management
-
the-engineering-managers-booklist
Books for people who are or aspire to manage/lead team(s) of software engineers
-
awesome-engineering
A curated list of awesome engineering blogs, handbooks and open source repos from top technology companies
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better ways-of-working alternative or higher similarity.
ways-of-working reviews and mentions
Posts with mentions or reviews of ways-of-working.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-27.
-
The unwritten laws of engineering at Stedi
Written ways of working can help teams internally, and it turns out can also greatly help with managing up the chain of command.
If you have ways of working, then I would love to know about them. I maintain a repo of help for tech teams here: https://github.com/joelparkerhenderson/ways-of-working/
-
We Don't Do That Here
> are your ground rules and team values always open for debate
Yes including asynchronous e.g. on a chat channel, and synchronous e.g. during a retrospective.
> on Friday afternoon when all your services have gone belly up
Yes. For example some teams choose a way-of-working for emergencies that uses the abbreviation "ANC" for the priority order of Aviate, Navigate, Communicate. If there is an emergency,then the team focuses first on keeping the system running, second on figuring out where to go and how to get there, and third on talking. Afterward, then the team does a causal analysis e.g. postmortem or after-incident report, including fielding any ways-of-working areas that came up in the channels because of the emergency.
> when someone new (a vendor say, or an intern) violates those ground rules and values do you shut them down with some variant of "we don't do that here" like "you have violated the ground rules"?
Yes. For example there are sometimes fast-moving high-urgency multi-team meetings that include many new people who don't know about ways-of-working. We open the meeting by saying e.g. "This meeting's moderator is Alice." then Alice quickly explains the ways-of-working: one person talks at a time; debate the issue not the person; focus on the agenda not side tasks; call a timeout if something important is amiss; etc."
> Are your ground rules explicitly enumerated somewhere and all team members familiar with them in enough specific detail to know whether or not something violates them?
Yes, such as using docs, or wikis, or README files, etc.
You can see many of the public ones in the repo at https://github.com/joelparkerhenderson/ways-of-working where there are a bunch of them collected across many teams.
If there's anything in the repo that you believe can be improved, or clarified, or grown, then I welcome constructive criticism. Likewise if you have opinions of different ways to handle team values, or skip them, I'm interested in knowing what you think.
- Ways of Working: ground rules and aspirations for beter teamwork
-
A note from our sponsor - SaaSHub
www.saashub.com | 25 Apr 2024
Stats
Basic ways-of-working repo stats
4
614
3.8
11 days ago
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com