Have you seen many projects completed on schedule? Neither did I. Here are a few ideas that hopefully may help.
Let’s first have a look at how a Project schedule is established and the progress measurement is made.
via www.toblog.fr
This blog is from LinkedIn for the AACE group. The critical concept here that is lost in most IT projects is to start with the end in mind and define the predecessor dependencies. When those are all connected and their durations estimated along with the cost estimates, you can answer the question "when should we have started this project?"
This approach is essentially Scrum, but focuses on defining DONE first and working right to left. Most planning processes not based in this technique or the US DoD IMP/IMS process, start on the left and plan to the right. When the "real" date is discovered and it is unacceptable to the stakeholders and they demand a completion date, you get "schedule compression," and head down the path of being late and over budget before you start.
