Mike Cohn explains how to prevent estimate inflation.
InfoQ spoke to Vasco Duarte on how the #NoEstimates technique may apply to a contracting environment, facing tipical needs of sizing a project, establishment of agreements, signature of contract and building of trust.
At the Agile Tour London 2015 Doug Talbot gave a talk titled "Do you know how fast you're going?". InfoQ interviewed him about difficulties with estimation and planning, the measurements that agile teams use, objectively measuring productivity, his view on the #NoEstimates movement, and asked him for ideas that can help teams to make measurement more meaningfully.
Product backlog refinement is a practice in which product backlog items are split and often re- estimated. This post is based on user story splitting and re-estimations.
Vasco Duarte suggests that people should experiment with #NoEstimates to learn and find ways in which it can help them to deliver value on time and under budget. He is writing a book on #NoEstimates in which he explains why estimation does not work and how you can use #NoEstimates to manage projects.
An interview with Yaniv Yehuda, Co-Founder and CTO of DBmaestro, about how they are doing agile development and using DevOps, how they implemented continuous delivery, on agile practices that turned out to be difficult to implement, and the benefits that they are getting for using agile and DevOps practices.
Debbie Madden and Vasco Duarte share their views on no-estimates.
This post covers the value of estimation in large and small scale projects and views on no estimation.
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.
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.
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.
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.
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.
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.