Mind Map of Building Teams

Establishing a Team
Practices and Principals
Leadership
Composition ✅

Predictability

Sentiment captured in 1:1s

DORA

Signals

Imperfect data that SIGNALS an action

Flow Metrics

Trust

Coaching - Growth and Development

Defect Rates

Boundary setting

Performance

Weekly - Monthly Cadence

1:1s

Things change when folks move

Up to about 20-23 is fine.

Its a lot more than 2 pizzas, and it is fine.

YAGNI

Kent Beck's Rules

Aggressively isolate frameworks

Integration test at boundary

Hexagonal

Interfaces at boundaries

"Whats so hard about writing a line of code, proving it works, and pushing it?"

Coding

Building Amazing Software Teams

Refactor EVERY time you touch code

Practices & Principals

Retrospectives

Trunk-Based Development

TDD

Test Automation

In Production 😱

Smoke Tests

Test data management

Focus on the why and how we'll know

Options > Direction

1 Sprint Ahead

Establishing a team

Avoid "requirements" trap

Needs to be as mature as new team or bad things happen

Dynamics

Product alignment

Reinforce engagement

Find the seams (team -> Leadership, team -> product, leadership->senior leadership)

Show & Tell

Team Launch

Forecasting. Work-break-down rates, throughput, etc.

Clearing a path (Leadership, stakeholders, etc)

When things go wrong

Conflict

Outages

Long-standing technical entropy

Translate for the seam, points become hours, etc.