Video Spotlight
Upcoming and Recent WebCasts
- Performance and Reliability Trade-Offs for Tuning ActiveMQ
- Best of Both Worlds: Enterprise ALM and Agile Parallel Development Practices
- Making the economic case for build-test-deploy automation and acceleration
- Enterprise Continuous Integration Maturity Model
- Subversion Best Practices: Maximizing Productivity
Agile Poll
Send us Feedback
Click here to send us feedbackOnline Users
What's the point in estimating? |
 |
 |
 |
| Written by Kelly Waters | |||
| Monday, 10 December 2007 05:35 | |||
 One technique used by agile development teams is the idea of estimating product features using points. This has a few distinct advantages over estimating in physical units of time, e.g. hours or days:1. Estimating is very quick because it's an intuitive estimate of a feature's size. 2. An estimate in points indicates a feature's size relative to another, and does not give the illusion of being precise. 3. Over time, and using consistent iterations (e.g. 2-week sprints), you get a strong feel for how many points a team can deliver in an iteration. Even if a team is bad at estimating, as long as they're consistently bad, this makes a team's commitments self-correcting. Some agile teams use Fibonacci numbers to do this. Fibonacci numbers are a sequence where each number is the sum of the previous two, i.e:1, 2, 3, 5, 8, 13, 21 ... Using Fibonacci adds an element of science to the concept of estimating using points, adding the laws of distribution as a dimension. If you're interested in understanding more about the scientific background of Fibonacci numbers - which weren't invented for agile development by the way! - you might be interested to listen to this Radio 4 podcast on Fibonacci... See also: How to estimate your product backlog Read the full Story >>
Set as favorite
Bookmark
Email this
Hits: 4473 Comments (0)
|
Show/hide comment form
| < Prev | Next > |
|---|
Agile Marketplace - Announcements and Special Offers
Complimentary Webinar w Forrester Analysts on Agile and Lean ALM
Complimentary webinar with Forrester Analysts Jeffrey Hammond and Dave West. Learn about Lean ALM Development, optimizing processes, cutting costs and compliance by design.
Read More
Agile CMMI – The Best of Both Worlds
Shares how a leading financial institution gains CMMI level 3 compliance and supports Agile practices.
Register for CollabNet webinar May 21
Requirements-based testing (RBT) can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage. Download the Requirements-Based Testing whitepaper