Scrum
312 bites tagged Scrum — interview questions with model answers, and 60-second explainers.
Communities of Practice: Scaling Knowledge Across Teams
A Community of Practice is a cross-team guild for a specific skill, like 'frontend' or 'testing'. It's how large orgs prevent knowledge silos, standardize tooling, and mentor juniors. The footgun: they fail without dedicated time and a clear charter.
Nexus Integration Team: Air Traffic Control for Scrum
The Nexus Integration Team is like air traffic control for multiple Scrum teams, guiding them to a single, integrated product. It's used in the Nexus framework to coordinate 3-9 teams on one product, resolving cross-team dependencies and integration failures.
Nexus Framework: Scaling Scrum Without Breaking It
Nexus is a lightweight wrapper for 3-9 Scrum teams working on one product. It adds a coordinating Nexus Integration Team and shared events to manage dependencies and deliver a single, integrated increment each sprint.
Right-Shifting Forecasts: Why Your Deadlines Keep Moving
A forecast is like a GPS ETA in traffic; new tasks are like accidents ahead, pushing your arrival time further out. This happens when initial estimates are treated as fixed deadlines, ignoring new scope. The footgun is anchoring on the first date given.
Throughput: Measuring What Gets Done
Throughput measures how many work items a team *finishes* in a time period, not how busy they are. It's used for forecasting future work and spotting bottlenecks. The footgun: never compare throughput between different teams, as item sizes and context vary.
Agile Facilitation: Guiding Teams to Outcomes
An Agile Facilitator is a neutral guide, designing the *process* for a team to reach its own conclusions, not just running the meeting. They are crucial for sprint planning, retrospectives, and conflict resolution.
Evidence-Based Management (EBM): Measure Value, Not Just Velocity
Evidence-Based Management (EBM) is like a fitness tracker for your organization, using data to guide decisions instead of gut feel. It helps you measure progress toward goals and improve outcomes.
Product Vision: The Why Behind Your What
A product vision is your team's North Star—an aspirational goal answering 'Why are we building this?' It guides the roadmap and aligns stakeholders by describing the future you're creating, ensuring everyone pulls in the same direction.
Scrum Master Stances: A Situational Toolkit
A Scrum Master isn't just a meeting facilitator. They're a situational leader who adopts different roles—teacher, coach, impediment remover—to serve the team. This toolkit helps them decide when to teach, when to coach, and when to clear a path for the team.
Shu-Ha-Ri: A Model for Mastery
Shu-Ha-Ri is a model for mastery: first follow the rules (Shu), then break them (Ha), and finally make your own (Ri). It's used to guide agile adoption, starting with strict adherence before innovating.
Feature Teams: Ship Value, Not Layers
A feature team owns a customer-facing feature from start to finish, unlike component teams that own a single tech layer. This reduces handoffs and speeds up delivery.
Sprint Capacity Planning: Committing to Achievable Work
Sprint capacity planning is like checking your team's fuel tank before a road trip. It calculates your team's actual available work hours for a sprint, accounting for time off, to make a realistic commitment.
Kaizen: The Art of Continuous Improvement
Kaizen means "continuous improvement," making small, frequent changes instead of big, risky ones. In Scrum, this is the heart of the Sprint Retrospective, where teams inspect their process and define concrete actions for the next sprint.
Agile Maturity Models: A Map, Not a Race
An Agile Maturity Model is a report card for your process, assessing adherence to Agile values through defined levels. Teams use it to benchmark progress and find weak spots.
Disciplined Agile: A Toolkit, Not a Prescription
Disciplined Agile (DA) is a toolkit, not a rigid framework, for choosing your own process. It helps teams blend practices from Scrum and Lean when one method doesn't fit. The footgun is treating DA as a prescription instead of a decision-making guide.
Cycle Time Scatterplot: Visualize Your Team's Predictability
A Cycle Time Scatterplot visualizes delivery speed by plotting how long each task took against its completion date. Agile teams use it to spot predictability trends and set realistic delivery forecasts.
Swarming: The Team Tackles One Thing at Once
Swarming focuses the entire team's effort on a single work item to finish it fast, rather than having everyone work on separate tasks. Use it to unblock a critical feature or push the most important story over the finish line at the end of a.
The Scrum Board: Visualizing the Sprint's Workflow
A Scrum board is a visual snapshot of a team's work in a sprint, making progress and bottlenecks obvious. Teams use it to track tasks from "To Do" to "Done," ensuring alignment. The footgun: mistaking the board for Scrum itself; it's a helpful tool, not.
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.
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.
Get Scrum bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.