Mind Map of Building Teams

Data

Predictability

Sentiment captured in 1:1s

DORA

Coaching - Growth and Development

Things change when folks move

Signals

How to accurately forecast a software team's performance

Imperfect data that SIGNALS an action

Defect Rates

Flow Metrics

Weekly - Monthly Cadence

Trust

Leadership

Building Self Managed Teams

One Metric To Start

Boundary setting

1:1s

Performance

YAGNI

Kent Beck's Rules

Coding

Skill Composition

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

When things go wrong

Conflict

Outages

Long-standing technical entropy

Aggressively isolate frameworks

Integration test at boundary

Why I Love Tell Dont Ask

Hexagonal

Interfaces at boundaries

Team Launch

Building Amazing Software Teams

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

Refactor EVERY time you touch code

In Production 😱

Constant Wip Limits

3 Questions To Better Actions

Smoke Tests

Test data management

Practices & Principals

Retrospectives

Trunk-Based Development

TDD

Test Automation

Dynamics

Product alignment

Options > Direction

Show & Tell

1 Sprint Ahead

Establishing a team

Avoid "requirements" trap

Reinforce engagement

What is my software team's capacity

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

Get People on the Same Page in Under a Minute

Clearing a path (Leadership, stakeholders, etc)

Focus on the why and how we'll know

Ultimate Guide To Horizon Planning

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

Make One Adjustment To Your Roadmaps

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

Get Started With Dev And Product Metrics

Translate for the seam, points become hours, etc.

Don't Start Work, Start Teams