managers-playbook
ways-of-working
managers-playbook | ways-of-working | |
---|---|---|
5 | 4 | |
5,287 | 614 | |
- | - | |
6.8 | 5.6 | |
6 months ago | 21 days ago | |
Creative Commons Attribution 4.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
managers-playbook
- The Manager's Playbook: How to be an effective engineering manager
-
Frisch als Führungskraft, Tipps?
Welche Branche? Für SWE gibt es hier interessante Lektüren: https://github.com/ksindi/managers-playbook
- Ask HN: Tips for Engineering Manager
- Excellent "management playbook" reference.
-
Scrum master with no dev experience
Title aside (“manager” - I agree with other commenters, don’t focus on being a manager), this is a food resource https://github.com/ksindi/managers-playbook
ways-of-working
-
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
What are some alternatives?
typora-issues - Bugs, suggestions or free discussions about the minimal markdown editor — Typora
questions-for-employers - A big collection of useful questions to ask potential employers.
awesome-cto - A curated and opinionated list of resources for Chief Technology Officers, with the emphasis on startups
hn-search - Hacker News Search
Issue-Tracker - The public issue tracker for the EarthMC Minecraft server.
awesome-leading-and-managing - Awesome List of resources on leading people and being a manager. Geared toward tech, but potentially useful to anyone.
httptoolkit - HTTP Toolkit is a beautiful & open-source tool for debugging, testing and building with HTTP(S) on Windows, Linux & Mac :tada: Open an issue here to give feedback or ask for help.
degoogle - A huge list of alternatives to Google products. Privacy tips, tricks, and links.
wisdom - Merlin Mann attempts to capture the best advice he's heard and learned from.