Work smarter, not harder. Easier said than done.
However, in agile software development, there are some things teams can do to begin working smarter and more efficiently.
Many companies still estimate the amount of time a project will take in hours. But this approach, typical of the waterfall methodology, can lead to cost overruns and missed deadlines. "(Humans are) terrible at estimating how long something is going to take. We're just not good at it," said Christopher Pepe, Chief Technology Officer at Praecipio Consulting. "But what we are good at is estimating the relative sizes of things." And so he makes this point in his story above on story points vs. hours, and why companies should adopt this agile concept of planning and managing development projects.
But first, what is a story point? According to Dan Radigan in his article The secrets behind story points and agile estimation, "Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100." Story points provide an abstract way of understanding how complex a project is, and how much work a project will take.
In a comparison between agile and waterfall time estimates, Steve Cooke at Swarm Online writes "The reasoning behind using points rather than hours, is that it might be difficult to estimate in units of time at speed. Also, the speed at which the team can deliver points of effort will depend on the skills of the individuals in the team. Team A might not be as fast as Team B but the relative size of the stories remains the same."
If you want to know more about how using story points could help your team with project estimation, reach out to us today.