NoEstimates articles to get you started - Software Development Today. The #NoEstimates hashtag on twitter has caused a whirlwind of discussion about the role of estimates in software development.
There’s so much controversy that I decided to write a book about it. The book is now available for purchase as a digital package, including 9 video interviews, and 2 extra mini e-books exclusively written to be companions to the NoEstimates Book. You can find all the content in the NoEstimates Book page. I’ve written many posts on the topic of #NoEstimates over the years (started practicing in 2005), but there are many others who have also written on the subject. Here’s a collection of their posts. NoEstimates posts by the most active authors on the topic Posts by Woody Zuill (@WoodyZuill on twitter) No Estimates: Let's Explore the Possibilities - Woody Zuill. Decision Making Strategies of No Estimates. A recent Harvard Business Review article revealed that one in six IT projects has a cost overrun of 200%.
Debbie Madden, CEO and Cofounder at Stride Consulting, shares her views on no-estimates, in her blog on “Your Agile Project Needs a Budget, Not an Estimate”. She says that because of the high rate of failure for estimation, stop estimating and start budgeting. Every software development project starts with some common questions like how much is this going to cost? The #NoEstimates Movement. 'No Estimates: Let's Explore the Possibilities' by Woody Zuill. Free people search and contact details for Roy L Zuill. Life, Liberty, and the Pursuit of Agility » Blog Archive » Notes From A Conference Session On No Estimates in Software Development.
I’ve done 12+ sessions at Agile and Developer “user groups”, Agile or Dev conferences, college classes, and code camps where the main topic (or a big component) of the session was Estimates in Software Development.
Here are the notes from one such session I facilitated last year at an Open Space event (Agile Open California, North) Session Title: Estimates – Can’t Live With Them, Can We Live Without Them? The title was my own. .NET Rocks! Carl and Richard try something new - doing a mob style interview about mob programming!
Mob programming takes agile to a new extreme where several people (more than two) work together to write code... resulting in very high quality code! The conversation digs into the actual process of writing code (drivers and navigators), the various roles that participants fall into, how more minds end up with more code reuse, testing, QA and the great sense of connection that comes with mob programming. You gotta try this! Gordon Pu has been a software programmer for over thirteen years. He shifted from RPG language to Microsoft .NET VB and then C#. Dexter Baga is a software developer who loves to develop software on and off work hours, enjoys experimenting with various software development techniques and thrilled to be working with the Hunter Mob programming team.
Chris Lucian is the creator of Enliven, an Augmented Reality colorblindness aid. Links from the Show 51 minutes. How does the mob get away with no estimates? « Mob Programming. How much do you estimate to get across?
Life, Liberty, and the Pursuit of Agility » Blog Archive » Agile2013 Lightning Talk: NoEstimates. NOTE: This was a lightning talk proposal for Agile 2013 in Nashville.
My main purpose in this post was to have a chance to give a lightning talk on “No Estimates” at that conference. An additional purpose is to encourage people to be thinking about the sort of estimates we use in software development, why we think they are useful, why we depend on them so heavily, and some of the reasons we might want to re-think our dependence on estimates. Fortunately for me, I was chosen to present this lightning talk, which challenged me to put together a focused slide deck and talk on the subject, which then grew into the talk which I gave at Oredev 2013. Going forward, my is goal to expose the sort of thinking and questioning I have been doing over the last 10+ years so that others who have been asking can use these questions as a starting point in their own exploration of estimate-driven software development.
I am not offering to answer these questions for you. Now: the original post: Woody Zuill on Mob Programming and No Estimates. 3.
You are a manager at Hunter Industries. So what are they about, what do they do? Yeah. So Hunter makes sprinklers and they are sort of the … I would say, they are very innovative in what they do and they have a very high quality standard, so it’s a wonderful place to work. They really understand the idea that we need to do quality work.
Craig: So, one of the presentations that you have been giving here, in fact I first came across the mob programming, as you call it, at an Open Space session at last years conference. Yeah, so the basic idea is that pair programming keeps two eyes on the code at all times and increases the ability to communicate to each other about the code. Craig: That’s the key, right? Yeah, that’s correct. 4. Life, Liberty, and the Pursuit of Agility » Blog Archive » Why do we need estimates? [NOTE: This post is about software development.
You might need estimates in some other field or domain and this article is not related specifically to any other domain, and especially not the one you want to complain about.] Life, Liberty, and the Pursuit of Agility » Blog Archive » My Customers Need Estimates, What Do I do? It seems a lot of people have an argument against the “No Estimates” idea that goes something like this: “Our Customers Need Estimates” There are many variations on this, but they typically come down to the same thing: We need customers, customers need estimates, therefore, we do estimates.
Life, Liberty, and the Pursuit of Agility » Blog Archive » Estimation is Easy and Useful: Estimate a game of Chess. Estimating Software Development Anyone who knows me will know that the title of this post is meant as a bit of a joke.
For software development, it is my experience that estimating** is rarely useful and always easy. Well… a little clarification: estimating is NEVER useful but ALWAYS easy the way I have typically seen it done, which uses the WAG* method of providing some numbers that seem plausible and that will allow the decision makers (stakeholders and managers) to approve the start or continuance of a project with a clear conscience. That is, when things sour later on they can always blame the developers for giving them inaccurate estimates (and not living up to their “commitments”). And the developers can always blame the “requirements people” for giving them unclear, incorrect, or incomplete requirements.