Working with Scott? Here's what to expect!
Caveats:
- I'm pretty aware of my faults - this document isn't my attempt at excusing them.
- This document also isn't an attempt to build trust. That happens as we work together.
- Small-town raised, lived-all-over, Millennial-leaning Gen-Xer (Xennial) who loves music, cooking, dad jokes, and technology.
- I'm pretty much down the middle blue/green. (Supporting or Observing Coordinator)
- I'm ISTJ-ish.
- Pragmatist - What works for our team? People > Process. True Agile!
- Overcommunicate - No going dark - It's ok to say things more than once - Written communication helps solidify your thoughts (see: https://basecamp.com/guides/how-we-communicate #6 and #7).
- Dig yourself (and others) a pit of success
- Continuous improvement - Little by little let's make things better
- Process is good - When it's just enough to ease the pain and no more
- When it comes to human interaction, boring is bad. Emojis, gifs and cool project names are it.
- When it comes to technology boring is good.
- We are not paid to write code. We are paid to solve problems and sometimes that means coding.
- Data - Let's establish some OKRs and start collecting data. Keep data in front of you. How do we measure what we care about?
- If it matters enough to be careful, it matters enough to build a system around it.
- Don't be a Hero - Problem Prevention > Problem Solving - Planning and Pre-Mortems rock!
- Be Assertive - Not passive aggressive or plain old aggressive. Tact and open communication go a long way.