File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Agile and Other Processes and the fly likes Estimation  (Agile Vs Non-Agile) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Estimation  (Agile Vs Non-Agile)" Watch "Estimation  (Agile Vs Non-Agile)" New topic

Estimation (Agile Vs Non-Agile)

kri shan
Ranch Hand

Joined: Apr 08, 2004
Posts: 1432
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

Joined: Jul 11, 2001
Posts: 14112
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.

The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Badri Narayanan Santhanam

Joined: Nov 24, 2008
Posts: 2
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 for software estimation services

Amit Ghorpade

Joined: Jun 06, 2007
Posts: 2851

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

|Asking Good Questions|
I agree. Here's the link:
subject: Estimation (Agile Vs Non-Agile)
It's not a secret anymore!