Skip to content

Instantly share code, notes, and snippets.

@thirdy

thirdy/teamleading.md

Last active July 15, 2019 10:58
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save thirdy/b93837bd6aa5e1692fb9bd986ac5aafb to your computer and use it in GitHub Desktop.
Save thirdy/b93837bd6aa5e1692fb9bd986ac5aafb to your computer and use it in GitHub Desktop.
Download ZIP
Notes on Team Leading in Tech
Raw
teamleading.md

Team Leading

  1. Get to know members individually so they can easily communicate complex issues
  2. Regularly assess individual progress, provide guidance and coaching
  3. Clearly communicate goals and context
  4. Regularly inform management of progress and potential risk
  5. Shield team from feature creep and premature requirements
  6. Establish clear development process
  • All code committed must be code reviewed
  • Maintain reliable automated test suite and act as living documentation
  • Maintain architecture documentation
  • Establish best practices like using immutable data and pure functions for domain logic, such practices can result in exponential increase in productivity
  • Encourage continuous improvement to existing process
  • Establish onboarding process for new hires, they should be able to produce production code in 1 or 2 week(s)
  • Document the development process and maintain it
  1. Listen to members' issues, individually. Asking feedback during team meeting is unproductive and possibly destructive
  2. Enable team members by getting them what (via their feedback) they need in order to be productive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment