Mind Map of Building Teams

Predictability

Sentiment captured in 1:1s

DORA

Signals

How to accurately forecast a software team's performance

Imperfect data that SIGNALS an action

Data
Measures, Metrics, and Signals

Flow Metrics

Trust

One Metric To Start

Coaching - Growth and Development

Defect Rates

Leadership

Building Self Managed Teams

Boundary setting

Performance

Weekly - Monthly Cadence

1:1s

Skill Composition

Things change when folks move

Team Size

Learning Team Capability

Stability

Up to about 20-23 is fine.

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

Skill Liquidity Assessment

Cross-Functionality

Why I Love Tell Dont Ask

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

Constant Wip Limits

Practices & Principals

3 Questions To Better Actions

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

Get People on the Same Page in Under a Minute

Reinforce engagement

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

Show & Tell

Team Launch

What is my software team's capacity

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

Clearing a path (Leadership, stakeholders, etc)

Ultimate Guide To Horizon Planning

Get Started With Dev And Product Metrics

Make One Adjustment To Your Roadmaps

Don't Start Work, Start Teams

When things go wrong

Conflict

Outages

Long-standing technical entropy

Translate for the seam, points become hours, etc.