We previously looked at how to perform agile estimation, we also dipped into the cone of uncertaintyand explained how it is used in the development lifecycle (and the weather in our intro to agile estimation).
Let me give you a bit of advice, whether you are in a product position, a developer or business analyst never give the business an estimation for the delivery of a thing based on time. Don’t even mention days/weeks/months or even years! Get the message?!
A user story is a short description of functionality, sometimes written by an actual user but more often written by a proxy for the user, either a product manager or digital business analyst. They are generally small, and strive to outline a single piece of functionality, the general structure for a user story is as follows:
Lets quickly recap the definition of ‘Estimation’:
The cone of uncertainty is the result of statistics from software projects over the past 60 years. It has roots in the engineering and chemical engineering from the 1950’s and was brought into software development in 1981.
To highlight the problem we’ll create an example project.