Intermediate everything in Product Management, page 45
Story Splitting: Delivering Value in Smaller Slices
Story splitting breaks large user stories into smaller, independent pieces that still deliver value, like slicing a cake vertically so each piece has all layers. This is crucial for fitting work into a sprint and getting faster user feedback.
Story Points: Estimating Effort, Not Time
Story points measure effort, not hours. They combine a task's complexity, uncertainty, and volume into a single relative number. Agile teams use them to forecast work capacity.
The 3 Cs: Card, Conversation, Confirmation
A user story isn't a spec; it's a promise for a conversation. The 3 Cs model this: the Card is a placeholder, the Conversation clarifies requirements, and the Confirmation defines "done" with acceptance criteria.
Agile Spikes: Time-Boxed Research to Reduce Uncertainty
A spike is a time-boxed investigation to answer a question or reduce uncertainty. It's a story whose deliverable is knowledge, not shippable code. Spikes are used to de-risk complex stories or evaluate technical options.
Agile Velocity: A Forecasting Tool, Not a Target
Agile velocity isn't about speed; it's a measure of a team's predictable output per iteration. It's used to forecast how much work can be done in future sprints and to estimate release dates. The footgun is treating it as a productivity KPI.
Systems Thinking: Optimize the Whole, Not the Parts
Systems thinking means optimizing the entire system, not just its individual parts. In large-scale development, siloed teams create local efficiencies that harm the overall delivery pipeline.
Conflict Management in Agile Teams
Agile's tight, high interaction cadence, standups, planning, retros, surfaces disagreement constantly. Conflict management means treating friction as raw material for a better decision, resolved openly, not avoided to keep the sprint looking smooth.
Sprint Planning: Committing to a Goal, Not Just Tasks
Sprint Planning isn't just picking tasks; it's the team committing to a valuable Sprint Goal. This ceremony kicks off every sprint, aligning everyone on what to build and why.
WIP Limits: Stop Starting, Start Finishing
WIP limits force teams to finish existing work before starting new work, creating a pull system that exposes bottlenecks. This is a core Kanban practice to reduce context switching and shorten lead times.
The 12 Agile Principles: Guiding Values, Not Rigid Rules
The 12 Agile Principles are values that prioritize customer satisfaction, working software, and team collaboration over rigid plans. They inform daily stand-ups and retrospectives, helping teams adapt to change.
Bimodal IT: Running Your IT Org at Two Speeds
Bimodal IT runs IT at two speeds: a stable, predictable "Mode 1" for core systems and an agile, experimental "Mode 2" for innovation. This allows enterprises to build new digital products without breaking the essential legacy systems that run the business.
Kotter's 8-Step Change Model
Kotter's 8-Step Model treats organizational change as a campaign, not a memo. It's used for major shifts like mergers or new AI strategies. Skipping steps like creating urgency or celebrating small wins is a common failure mode, causing momentum to fizzle out.
Humble Inquiry: Ask Questions You Can't Answer
Humble Inquiry means asking questions you don't know the answer to, building trust by showing genuine curiosity. Use it in 1-on-1s or retrospectives to uncover hidden assumptions. The footgun is asking a leading question disguised as an open one.
Intent-Based Leadership: The Leader-Leader Model
Instead of waiting for orders, teams declare their intent to act. This leader-leader model, born on a nuclear sub, shifts the default from 'ask permission' to 'act unless vetoed,' empowering distributed decision-making.
Intent-Based Leadership: State the Goal, Not the Steps
Instead of giving orders, leaders declare their intent, empowering teams to figure out the 'how.' It's used in agile teams or military units where frontline context is key. The footgun is giving control without clarity, which leads to chaos instead of results.
Management 3.0: Manage the System, Not the People
Management 3.0 treats leadership like tending a garden, not commanding an army. You manage the system—the environment and constraints—to let empowered teams flourish. It's used in agile contexts to boost engagement with hands-on tools and games.
Inspect & Adapt: SAFe's Formal Improvement Event
Inspect & Adapt is a formal 'pit stop' for an entire Agile Release Train (ART) to improve its process. At the end of each Program Increment, teams demo the solution, review metrics, and identify improvements.
Scrum@Scale: Agile for Teams of Teams
Scrum@Scale treats your organization as a network of Scrum teams, aiming for "minimum viable bureaucracy." It coordinates multiple teams working on one complex product.
RTE: The Conductor of the Agile Release Train
The Release Train Engineer (RTE) is the master facilitator for a group of agile teams, acting as a servant leader and coach. They orchestrate large-scale planning and ensure smooth value delivery.
PI Planning: Aligning an Entire Agile Release Train
PI Planning gets an entire 'team of teams' (an ART) in one room to plan the next 8-12 weeks. This two-day event aligns development with business goals and identifies cross-team dependencies.
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