Heike Moeller November 10, 2020 Project Management
Most larger organisations have well developed and run IT departments. They usually have formal project offices with established plan templates and standards, with project office staff and automated plan analysis systems (for example seeking orphan tasks / missing dependencies and so on to measure overall `plan quality`). Smaller organisations - for example, `IT solutions houses` - may lack this level of sophistication but will certainly use detailed project plans.
The business requirements state what is required but do not specify how the deliverable will actually work. So in many projects with a tangible and technically sophisticated deliverable, it is very common to produce additional documentation about the look and feel of the end product. The functional specification describes not only how the end product will look but also how an end-user will actually use it and what the user-experience will be like. This document should contain sections that specifically relate to each of the requirements in the business requirements document so that every functional item can be tracked back to an original business need.
They are a fundamental tool in a project manager`s toolkit. However, an unseasoned project manager can find that they can take over the project and result in reduced control. How so? In this article we will look at their potential pitfalls and provide some tips and strategies for ensuring successful project management. Gantt charts are, after all, just one of many ways of presenting the project planning and actual data that has been input.
Prior to creating the project schedule the project manager must have a work breakdown structure (WBS), an effort estimate for each task, and a list of resources with availability for each resource. Once these data are established a project scheduling tool can automatically do much of the tedious work of calculating the schedule. However, before a project manager can use such tools, he should have an understanding over concepts like WBS, dependencies, resource allocation, critical paths etc. These are the real keys to planning a successful project.