Estimation (Agile Vs Non-Agile)

[kri shan]

Agile: SCRUM estimation based on user stories and actual developers are estimating their tasks.

Non-Agile: But NON-Agile estimates are based on work and Managers(may be non-technical person) estimation their work using MicroSoftProject/other tools.

Which one gives accurate estimate(>80% close to actual) (not expecting 100% accurate) ?

[Ilja Preuss]

The initial estimate is likely to be similar between an Agile and a Waterfall project, simply because you have the same amount of information (=not much). The most important difference is that the Agile project enables you to continuously refine that estimate, and therefore to actually *manage* the project, whereas being late with a Waterfall project is often only noticed when it's already *too* late to do anything about it.

[Badri Narayanan Santhanam]

Well, i personally think that developers shouldnt set the targets. Its for the manager to do it, be it Agile or Non-Agile

I agree, with Ilja Preuss, that for Iteration 1 the estimates should be the same. In Agile model, its iterative dev, and estimation is more complex. . in non-agile model, there are standards available to size the new requirements added / changes to exisitng functionality. One example is Function point technique, which could be used to esimate dev and application value addition services

visit http://www.ezeequote.com for software estimation services

Thanks

[Amit Ghorpade]

"eZeeQuote Estimation Services " please check your private messages for an important administrative matter.