Estimation for Agile Projects |
||||||||||||||||||||||||||||||||||||
|
|
Home > Articles >
While there has been much already written on agile estimation, it is an area that comes up time and time again. This article will cover the big picture view of upfront estimates and ways to engage more stakeholders in the estimation process.
First of all we need to understand that estimating software projects will always be problematic. It does not matter if it will be a traditional project or an agile one; software development projects are unique (we do not repeatedly build the same system) and the evaluation difficulties that make gathering upfront-requirements tricky also make scoping and estimating hard, too. So approach the problem conscious of the issues and limitations of any approach; keep in mind that early estimates will have wide ranges of variability.
![]() As shown by Barry Boehm’s estimate convergence graph (above), at the time of Requirements Specification estimates are only likely to be in 1.5x to 0.6x of the final project cost range.
Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Use WorkLenz PPM to Manage Agile Software Development
|
| ||||||||||||||||||||||||||||||||||