2 quote from referenced link
source | link

The idea of doing a schedule estimate at the phase of the cycle where you get to do it is ludicrous. 

Since you are time-boxed from the outset, you should look at an Agile methodology like SCRUM which tries to provide visibility and transparency for project progress in hopes of simple forecasting based on prior code deliveries.

See article http://www.cprime.com/community/articles/whentousescrum.htmlWhen to Use Scrum for software projects?

Scrum is often contrasted with the so-called “Waterfall” approach, which emphasizes up-front planning and scheduling of activities, followed by execution. Both approaches require careful planning, followed by execution and tracking, but the details of how these steps are accomplished are different...

Why Choose Scrum versus Waterfall for Software Projects?

The two approaches make different assumptions about the priorities and practicalities of the work to be accomplished...

In general, if you have to figure out how to do a significant amount of the work in the project because you haven’t done it before, so you cannot estimate accurately, go with a Scrum process. If you’ve done it many times before, and know how to do it again, go with a waterfall process...

The idea of doing a schedule estimate at the phase of the cycle where you get to do it is ludicrous. Since you are time-boxed from the outset, you should look at an Agile methodology like SCRUM which tries to provide visibility and transparency for project progress in hopes of simple forecasting based on prior code deliveries.

http://www.cprime.com/community/articles/whentousescrum.html

The idea of doing a schedule estimate at the phase of the cycle where you get to do it is ludicrous. 

Since you are time-boxed from the outset, you should look at an Agile methodology like SCRUM which tries to provide visibility and transparency for project progress in hopes of simple forecasting based on prior code deliveries.

See article When to Use Scrum for software projects?

Scrum is often contrasted with the so-called “Waterfall” approach, which emphasizes up-front planning and scheduling of activities, followed by execution. Both approaches require careful planning, followed by execution and tracking, but the details of how these steps are accomplished are different...

Why Choose Scrum versus Waterfall for Software Projects?

The two approaches make different assumptions about the priorities and practicalities of the work to be accomplished...

In general, if you have to figure out how to do a significant amount of the work in the project because you haven’t done it before, so you cannot estimate accurately, go with a Scrum process. If you’ve done it many times before, and know how to do it again, go with a waterfall process...

1
source | link

The idea of doing a schedule estimate at the phase of the cycle where you get to do it is ludicrous. Since you are time-boxed from the outset, you should look at an Agile methodology like SCRUM which tries to provide visibility and transparency for project progress in hopes of simple forecasting based on prior code deliveries.

http://www.cprime.com/community/articles/whentousescrum.html