InfoQ Homepage Agile Estimation Content on InfoQ
-
Decision Making Strategies of No Estimates
Debbie Madden and Vasco Duarte share their views on no-estimates.
-
No Estimation in Small And Large Scale Agile Projects
This post covers the value of estimation in large and small scale projects and views on no estimation.
-
Velocity-Driven Versus Commitment-Driven Sprint Planning
There are different opinions for conducting sprint planning. Long debate is happening between velocity driven sprint planning and commitment driven sprint planning. Mike Cohn, founder of Mountain Goat Software, shared his views in his recent blog on Why I Prefer Commitment-Driven Sprint Planning.
-
Empirical Measurement of Cycle Time by Slicing Heuristic
Agile teams which use noestimates, can use slicing heuristic to empirically measure cycle time to help them predict how much, can be done before doing the actual work.
-
Concerns about Measuring Velocity for Team Improvement
Agile teams measure the velocity of their sprints. It helps them to plan and track their progress and provides insight for product owners to plan product releases. Can teams also use velocity data when they want to improve themselves? Several authors have written about velocity and shared their concerns on measuring velocity to improve the productivity of teams.
-
New Scrum Kickoff Planner Aims To Help Agile Teams Start on The Right Track
A new "Scrum Kickoff Planner" has just been released by Adam Weisbart with the aim of facilitating team discussion around the important facets of starting a new Agile team or project.
-
The Planning Poker Prevents Fallacies in Effort Estimates
In his recent blog posting “Planning Poker: Avoiding Fallacies in Effort Estimate” Hayim Makabee discusses a common problem of effort estimation called planning fallacy and why planning poker helps to avoid it.
-
Is Velocity Killing Agile?
Velocity, the measure of work completed by the team divided by the time taken to complete it, is increasingly being used to manage the productivity of a team and as a comparison between teams. Jim Highsmith, Mark Levison, and Scott Ambler discuss the misuse of velocity as a productivity measure.