Advanced concepts in Agile & Scrum
Toyota Production System (TPS): The Original Lean
The Toyota Production System (TPS) is a complete socio-technical system, not just a toolkit. It organizes manufacturing and logistics from suppliers to customers.
Empirical Process Control: Steer by Observing, Not by Plan
Empirical process control means steering by observation, not by a rigid upfront plan. Scrum uses this to tackle complex problems, inspecting real work in Sprints to adapt. The footgun is fake transparency—if artifacts hide problems, you're steering blind.
Value Stream Mapping: Find the Waste in Your Process
Value Stream Mapping visualizes your entire process, from request to delivery, to separate value-adding work from wasteful delays. It's used to find bottlenecks in manufacturing or software, like code waiting for review.
Weighted Shortest Job First (WSJF): Prioritizing for Economic Impact
WSJF prioritizes work by its economic impact over time, not just its total value. It sequences backlogs in SAFe by dividing the "cost of delay" by job size. The footgun is getting bogged down in precise estimates instead of using relative sizing.
Psychological Safety: The Foundation of High-Performing Teams
Psychological safety is the belief you won't be punished for speaking up or making mistakes. It's the top predictor of team effectiveness, enabling the risk-taking and candor needed for innovation.
Liberating Structures: Rules for Unleashing Group Intelligence
Liberating Structures are simple rules that replace default meeting formats, ensuring everyone participates. Use them in retrospectives or planning sessions to move beyond presentations.
The Four Stances of an Agile Coach
An agile coach isn't just a senior Scrum Master; they operate from four stances: teaching, mentoring, facilitating, and professional coaching. This model helps them choose the right approach to develop a team's capability, not just run ceremonies.
The Boy Scout Rule: Leave Code Cleaner Than You Found It
The Boy Scout Rule applies a simple principle to code: always leave it a little cleaner than you found it. When fixing a bug, make a small improvement like renaming a variable.
The Technical Debt Quadrant
The Technical Debt Quadrant reframes debt not as one problem, but a 2x2 matrix: prudent vs. reckless and deliberate vs. inadvertent. This distinguishes a strategic choice to ship early from a simple mess. The footgun is treating all debt as equally bad.
Mob Programming: The Whole Team on One Computer
Mob programming is like pair programming for the whole team: everyone works on one task, on one computer, at the same time. It's used for complex problems or onboarding. The footgun is letting it become a passive meeting instead of an active collaboration.
Buy a Feature: Prioritize by Making Customers Spend
Buy a Feature turns prioritization into a game where customers spend a limited budget on their desired features. It's used in product planning to force trade-offs and reveal true value.
Cost of Delay: Quantifying the Price of Waiting
Cost of Delay puts a price tag on waiting, quantifying the value lost for every week a feature isn't shipped. It helps prioritize work by its economic impact, not just effort.
Impact Mapping: From Business Goals to Code
Impact Mapping is a visual roadmap that connects business goals directly to features, forcing you to answer "Why?" before "What?". Use it to align stakeholders on a new vision or prioritize a backlog. The footgun is starting with features and working backward.
Emergent Architecture: Build Just Enough, Just in Time
Emergent architecture lets design evolve as you build, prioritizing adaptation over upfront planning. It's used in agile teams where requirements are unclear.
Continuous Delivery vs. Deployment: The Final Step
Continuous Delivery automates releases to a staging environment for a manual go-live decision, while Continuous Deployment automatically pushes every passing build to production. Use Delivery for business-timed releases; use Deployment for maximum velocity.
Double-Loop Learning: Question the 'Why', Not Just the 'How'
Double-loop learning means questioning the 'why' behind your work, not just fixing the 'how'. Instead of only correcting errors, you challenge the underlying goals. This is crucial in retrospectives when a team realizes their entire approach was flawed.
Actionable Agile Metrics: Predicting 'Done'
Stop guessing 'done' and start forecasting with data. Actionable Agile Metrics use historical flow data—like cycle time and throughput—to answer 'When will it be done?' for customers who need predictability.
Strangler Fig Pattern: Replace Legacy Systems Safely
The Strangler Fig pattern lets you replace a legacy system by gradually growing a new one around it, eventually choking out the old code. It's used for modernizing critical systems where a "big bang" rewrite is too risky, routing traffic feature by feature.
Contract Testing: Test Interfaces, Not Integrations
Contract testing ensures services work together without slow integration tests. It's a formal agreement where a 'consumer' defines its needs, and a 'provider' proves it can meet them.
ATDD: Aligning Code with Business Needs Before You Build
Acceptance Test-Driven Development (ATDD) is a communication framework where business, developers, and testers write acceptance tests together *before* coding begins. This ensures everyone understands the requirements.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles