How does agile develop the right person/day to look at this matter?

Traditional software estimates the way of the functional, some use the Points, Delphi .... And so on .

Agile development, the use of mathematical gold ratio; 1, 2, 3, 5, 8, 13; The "relative" complexity of each user Stories to estimate the required user Stories .

However, just changing an algorithm , is meaningless ...

software development : Expect to use all kinds of people / Day estimation method can be delivered at 刃 time to meet the expected software.

I'm always mentioning one thing : Now human technology advances But software development for many people " pure handmade " " man/day " to anticipate when the expected software will be delivered

so Real focus Span style= "Color:black" > go estimate " A.

: How to leverage User story What effective strategy should be developed plan

people / days , is used for Product Owner do " decision Making " Use the , Not for " Simplified Management " software development That fully fills human behavior , simplified to standardized , Single Machine Operation .

How does agile develop the right person/day to look at this matter?