People need Project Plans/ Project schedule to showcase how a particular
work execution can be completed in given time and to highlight associated
assumptions/ risks.
Different PMs/ Organisation uses different
scheduling software tools like MS Excel, MS Visio, MS Project, Primavera, Open
Work Bench, Soho Project, Attack, Bright Work, Hyper Office and many others
however due to lack of trained project managers these tools often end up
showing some schedule which is more of illusion of reality rather a dynamic
execution model to guide the project team.
Understanding of key scheduling concepts and
knowledge of applying them using some scheduling software can provide really
very effective results.
Often people making project schedules, do not
know enough about given project context and unable to model that project
information into a project schedule which can show how entire project journey
can be completed.
All schedules are based on some key assumptions
and risk mitigation plans, often this information is not captured and shared
with key stakeholders for their agreement and as a result this project schedule
becomes irrelevant very soon.
They merely serve as PM support tool to manage
some project reporting/ briefing obligation rather than a project execution
guiding model.
Project schedules need to evolve as we gather
more and more details about execution of work packages/ risks and should have
enough clear tasks for team for next 1-2 months.
Project Schedule should be capable of predicting
delays impact on project finish dates so take appropriate control action
immediately.
Pl. does share if in your organisation, project
execution is driven by project plan or project plan is driven by project
execution as it happens.
