A guidebook by Brian Link

The Practical Agilist Guidebook

The agile mindset behaviors that define being agile — written for the coaches, Scrum Masters, and managers who want a team that gets it, not a team that just goes through the motions.

Scroll
The thesis

Being agile is about the behaviors behind the agile mindset.

An Agile Coach in a box

High‑performing teams that embrace modern ways of working innately understand what it means to embrace the Agile Mindset. Yet agile is frequently misunderstood — treated as a set of rules to follow inside a framework, when in truth it's a different way of thinking.

Teams that stick rigidly to Scrum, Kanban, LeSS, or SAFe without the mindset end up doing a mechanical form of agile — going through the motions, still grounded in the old ways of working.

Coaches call this the difference between doing agile and being agile. This book is a guidebook for that shift — written the way an Agile Coach would explain it to a team, one topic at a time.

The agile mindset

Seven cultures and mindsets, working together.

The Agile Mindset isn't one thing. It's the combination of seven distinct cultures and mindsets a team should understand and embody to truly be agile.

01Iterative mindsetBuild, learn, adjust. Repeat in short loops instead of betting on long plans.
02Product cultureOutcomes over outputs. Own the thing you ship, not just the tickets you close.
03Customer-centric mindsetReal users, real problems. The customer's reality is the source of truth.
04Culture of learningCuriosity is part of the job. The team studies, not just delivers.
05Culture of experimentationHypotheses, not opinions. Run small bets and let the evidence decide.
06Continuous improvementEvery week a little better. The system the team works in is also the work.
07Psychological safetyIt's safe to disagree, to be wrong, and to ask the obvious question.
All seven Together, they click. When a team understands why they're working differently — that's the moment they start being agile.

If you are just doing agile, you don't get it yet. When it clicks and a team understands why they are working differently, this is the moment the team has started being agile.

The structure

24 topics. Four sections. Read in any order.

A guidebook to discover more about the topics a team needs to improve. Pick what's relevant — every topic stands on its own.

Section 01 · 6 topics

Team culture

The human foundation underneath every framework. Trust, safety, and how the team treats each other when no one is watching.

  • Why long‑lasting product teams matter
  • Collaboration and team independence
  • Psychological safety inside teams
  • Psychological safety with leaders and SMEs
  • Team happiness and dysfunctions
  • A culture of learning on teams
Section 02 · 6 topics

Agile process basics

The mechanics done well — not the mechanical version. Cadence, flow, and the disciplines that make iteration actually work.

  • Process autonomy and mastery
  • Visualization and transparency
  • Estimation and expectation setting
  • Iterative thinking and breaking work down
  • Optimizing the flow of work
  • Continuous improvement and experimentation
Section 03 · 6 topics

Product management

Building the right thing, not just building things right. Customer intimacy, strategy, and the outcomes that prove value.

  • Customer centricity and intimacy
  • Communication channels and customer feedback
  • Feedback loops with stakeholders
  • Vision, strategy, and being value‑driven
  • Desired outcomes and reducing complexity
  • Alignment to strategy and measuring progress
Section 04 · 6 topics

Value delivery

Getting it shipped — and learning from what shipped. Flow, quality, automation, and the engineering practices that keep agility honest.

  • Repeatable, consistent, frequent value delivery
  • Deploying value and recovery from failure
  • Quality embedded in work habits
  • Work product organization, promotion, and management
  • Automated development processes and governance
  • Team process for skill sharing
Inside every topic

Five sub‑sections, every single chapter.

Each topic is framed as a question, then walked through the way an Agile Coach would walk a team through it.

01

The topic

Framed as a question. The body explains the ideas and lessons as an Agile Coach would share with a team — drawing on the Agile Manifesto, Lean, XP, Design Thinking, DevOps, and Systems Thinking.

02

Tips for leadership

Advice and context for leaders and managers — how to help the team and create the environment for their success.

03

Tips for Scrum Masters

The subtleties and techniques a Scrum Master might use to help the team understand the topic — with recommended activities to try.

04

Table of behaviors

Three or four representative behaviors per topic, described at low, medium, and high maturity — so the team can recognize where they stand and what's left to learn.

05

AI prompts & further reading

Suggested ChatGPT prompts to dig deeper, plus a curated bibliography of books, videos, and articles to keep learning past the page.

About the author

Written by a coach who's still in the room.

Brian Link is an Enterprise Agile Coach with a background in both technology and business strategy. He's helped drive large agile transformations and held multiple startup CTO roles.

Through his consulting business, Practical Agilist, he serves both large and small companies on their journey toward greater agility — and writes openly at medium.com/practical-agilist.

BL

Brian Link

Enterprise Agile Coach

“A number on a maturity scale doesn't tell a team what to do next — it just tells them where they rank. This book is the conversation I've had a hundred times with teams about why the behaviors matter, written down so a team can have it themselves.”

— Brian, on why he wrote the book

Be practical.
Stay agile.

Pick up The Practical Agilist Guidebook on Amazon — paperback or Kindle — and put a coach in your team's pocket.