Succeeding with Agile: Estimation and Sprint Planning

Explore why estimating knowledge work varies among similar developers due to understanding, clarity, luck, and uncertainty; complexity increases variance in completion times.

Explore how Parkinson's Law makes work expand to fill the time available, and how gold plating and Student's syndrome bias estimates and delivery.

Explore why estimating knowledge work is uncertain, showing that input and output follow a probability distribution rather than a single number, with days like five or seven as possible outcomes.

Explore no-estimation and relative estimation approaches for knowledge work, focusing on delivering value, throughput, and cycle time while managing size variation and avoiding velocity debates.

Learn story point estimation as a team-based, relative sizing method that uses a custom scale and reference stories to compare work size, not effort, and to split large stories.

Learn a practical method for story point estimation, using mid-sized reference stories and 3 or 5 points, then estimate new work by size, volume, and uncertainty without time factors.

Explore whether story point estimation is mandatory in Scrum, and learn when no estimates or size-based approaches help address variation among work items.

Estimation should be done by the dev team for size and time, with product owners abstaining (except for questions); Scrum Masters may join as developers, fostering team consensus and learning.

Avoid changing story point estimates during a sprint by default and focus on getting the work done. Consider adjusting estimates only when acceptance criteria changes cause significant size variation.

Learn why story points do not map to time, explore how size, complexity, and uncertainty shape effort, and understand team-level velocity as an approximate, distribution-based guide.

Use story points to account for size variation, track velocity, and sustain a consistent pace for long-term planning. Planning poker prompts questions and reveals differences during backlog refinement, boosting collaboration.

Revisit the wall of reference every 2 or 3 months. Refresh when team composition changes or the product shifts to keep two point, five point, and eight point stories consistent.

Learn how to estimate epics, features, and initiatives using three approaches: a constrained story point scale, separate epic or feature points for multi-team environments, or t-shirt sizing with conversion.

Plan ahead to improve readiness, alignment, and coordination by matching demand with capability, reducing effort, time, and the cost of failure.

Analyze the dysfunctions of traditional planning, from rushed meetings to overreliance on firm estimates and limited team engagement. Learn to foster collaborative, team-owned estimation for better sprint planning.

Master the scrum workflow and define a meaningful sprint goal that delivers a usable product increment. Collaborate in planning, align with the product owner, and seek fast stakeholder feedback.

Facilitate sprint planning by aligning the team around a prepared sprint goal and ready backlog items, breaking stories into subtasks, estimating effort, and confirming capacity with confidence.

Use the sample planning template to estimate sprint capacity, accounting for holidays and leaves, then break prioritized stories into tasks for developers, testers, and the scrum master.

Learn how to achieve effective sprint planning by ensuring ready items, active participation, voluntary task pulling, honest estimates, capacity-based forecasts, ownership of goals, and reliable alm updates.

Maximize sprint-level buffers to cover unknowns in knowledge work while avoiding task-level padding. Balance buffers for individuals and the team to accommodate ad hoc work and potential rework.

During sprint planning, team members estimate subtasks to plan work and log hours. Actuals tracking is optional for individuals and not for managers to protect psychological safety.