Bias, priming, and salience are the main psychological factors that influence our ability to estimate. Knowing what happens psychologically when we estimate, and using techniques from psychology, helps us to deal with those factors so that we can improve our estimations argued Joseph Pelrine, social complexity scientist and PhD researcher in psychology.
When developing a high speed printer based on a new print technology things change often; you need an effective and flexible solution for managing a large project with many different disciplines. Océ Printing Systems decided to customize Scrum and scale it to enable collaboration and make progress transparent.
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.
Technique of "value points" to determine the value delivered by any software project.
Debbie Madden and Vasco Duarte share their views on no-estimates.
Matt Rogish talked about using Objectives and Key Results (OKRs) for company, team, and personal goal setting at the No Pants Festival 2015 in Antwerp, Belgium. InfoQ interviewed Rogish about what OKRs are and how you can use them, their strengths and pitfalls, doing annual performance reviews and managing people with numerical goals, and starting with OKRs.
This post covers the value of estimation in large and small scale projects and views on no estimation.
If organizations want to make informed management decisions to maximize the delivered value they will need to gather evidence about value says Gunther Verheyen. InfoQ interviewed Gunther about evidence based software management and finding evidence, how Scrum relates to evidence-based managing, challenges in scaling agile, and advice for enterprises that want to adopt Scrum.
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.