A tailored course, built for your situation
Sources and specific examples on hand when peers push back
Build unshakable reasoning for Agile and Lean choices , grounded in field patterns, not opinion
The situation this course is for
Who this is for
Senior Agile and Lean practitioners leading transformation efforts in complex technical environments
Who this is not for
Those new to Agile coaching or seeking introductory frameworks
What you walk away with
- Articulate the historical and empirical roots of each method you recommend
- Reference specific projects and implementation trade-offs when challenged
- Distinguish when a method fits , and when it doesn’t , using field data
- Ground team resistance in context-specific reasoning, not abstract doctrine
- Turn pushback into a structured dialogue using proven decision frameworks
The 12 modules (with all 144 chapters)
- Origins in Toyota’s production system
- First software adaptation at IDX
- How Spotify’s model diverged
- Lean Startup’s pivot from customer development
- Extreme Programming’s test-first mandate
- SAFe’s enterprise translation
- Misinterpretations in mid-tier rollouts
- When cadence replaced reflection
- The cost of skipping retrospection
- Scaling frameworks vs. scaling mindset
- From co-location to distributed teams
- Reconstructing intent from diluted practices
- Reading standup notes for decision clues
- Mapping board swimlanes to org structure
- Tracking scope changes in Jira exports
- Inferring leadership pressure from sprint goals
- Finding constraints in velocity plateaus
- How planning poker shapes delivery
- Detecting political compromises
- Uncovering hidden dependencies
- Tracing RACI drift over time
- Identifying where autonomy was ceded
- Diagnosing cultural resistance points
- Linking metrics to incentive structures
- Regulated vs. startup environments
- Safety-critical retrospectives
- Audit trails in healthcare Agile
- Sprint zero in fintech
- Compliance as a backlog item
- Pair programming in regulated code
- Change control vs. continuous deploy
- Documentation debt in Lean UX
- Risk burndown charts
- Incident-driven backlog grooming
- BAU integration challenges
- Vendor-managed Agile pitfalls
- Signs of cargo cult Agile
- Velocity without value tracking
- Retrospectives as box-ticking
- Daily standups as status reports
- Backlogs filled with IT requests
- Mandated cadence without autonomy
- Certification-driven adoption
- Leadership using Agile for control
- Misaligned promotion criteria
- Tool-driven process design
- Over-indexing on metrics
- Ignoring emotional debt
- Pre-mortem for new rollouts
- Stakeholder-specific framing
- Linking methods to business outcomes
- Including counterargument sections
- Citing original authors
- Benchmarking against peer firms
- Mapping to regulatory expectations
- Including exit criteria
- Documenting assumptions
- Versioning rationale over time
- Embedding sources in templates
- Making it team-owned
- Classifying types of resistance
- Technical vs. political objections
- When data resolves the debate
- When values are in conflict
- Reframing 'this won’t work' statements
- Using historical examples
- Comparing to similar teams
- Inviting co-investigation
- Naming the real constraint
- Offering pilot alternatives
- Knowing when to let go
- Documenting dissent gracefully
- Starting the decision log
- Capturing context at rollout
- Updating after incidents
- Linking to incident reports
- Including dissenting views
- Archiving deprecated choices
- Tagging by risk type
- Annotating with metrics
- Cross-referencing tooling
- Versioning with tool changes
- Making searchable
- Training new members
- When execs demand faster
- Handling budget-driven cuts
- Justifying investment in retrospection
- Explaining technical debt
- Pushing back on scope creep
- Linking quality to velocity
- Defending team autonomy
- Showing cost of churn
- Naming opportunity cost
- Using competitor benchmarks
- Balancing innovation and stability
- Measuring cultural debt
- Structuring pattern entries
- Including failed experiments
- Adding context tags
- Rating confidence levels
- Linking to original authors
- Versioning across cycles
- Integrating with onboarding
- Connecting to tooling
- Automating capture points
- Curating by domain
- Updating based on audits
- Sharing across geographies
- Workshop on decision tracing
- Running pattern analysis sessions
- Creating team charters
- Documenting local adaptations
- Running internal critique forums
- Rotating facilitation roles
- Building internal case studies
- Linking to business KPIs
- Encouraging dissent logs
- Rewarding reasoning over compliance
- Measuring understanding
- Avoiding cult formation
- Designing the audit framework
- Scoring depth of rationale
- Including counterfactuals
- Evaluating source usage
- Assessing adaptation logic
- Reviewing decision logs
- Testing team understanding
- Benchmarking against field data
- Highlighting strong examples
- Reporting upward with nuance
- Avoiding punitive tone
- Incentivizing transparency
- Standardizing rationale templates
- Curating cross-client libraries
- Training new coaches
- Onboarding client teams
- Aligning with client audit cycles
- Conducting joint retrospectives
- Building client-specific pattern banks
- Managing IP boundaries
- Adapting to regulatory regimes
- Linking to ThoughtWorks assets
- Updating per feedback loops
- Measuring adoption depth
How this maps to your situation
- When rolling out a new Agile framework
- During internal audit cycles
- Facing leadership skepticism
- Scaling across geographies
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 2 hours per week over 12 weeks
How this compares to the alternatives
Unlike generic Agile certifications, this course focuses on depth of reasoning, not rote frameworks. It’s designed for practitioners who already lead transformations , not those learning the basics.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.