Claudia Eggers November 9, 2020 Project Management
Can Project Managers prevent projects from slipping? Ask a techie to come up with a schedule for a specific list of activities, and more often than not, he/she will present a fairly accurate estimate. Some activities might be underestimated, others overestimated, but overall, the plan will be fairly accurate. However, something happens to these estimates between the time the techie writes them down and the time the Project Manager publishes a baseline project schedule. That "something" is why projects slip.
A detailed schedule is one of the best tools that a project manager can have. By scheduling yourself in advance to do all of the necessary management tasks, you stay much more organized throughout your project. You know exactly what you need to do to get started, what you need to do for the planning stage, and so on. Plus, before you commence work on your project, you can ask yourself: how often do I want to meet with my team? how often do I want to conduct project reviews? and schedule yourself to do these periodic tasks.
When it comes to choosing tools for managing a project, there are several options that are available to you. In the past several years, many tools that were in use were general purpose tools. Nowadays, software tools have been created specifically for managing projects in specific industries. In addition, these tools are available in different types such as automated tools that could be installed on local computers or on a network server where different users can access them. There are also Web-based tools and paper-based tools, which include forms, templates and checklists.
The business requirements document should accurately, and in detail, describe the purpose of the project. It states what is needed to achieve that goal i.e. what is in-scope, what is out-of-scope, any assumptions that have been made, any constraints that have been imposed and expected timescales. The document will form the definitive description of the aims of the project and, as such, can be used to manage the expectations of the stakeholders. It will also include acceptance criteria that will ultimately be used to judge whether the project was a success.
Many of these products assume a knowledge of project management that many technical managers do not have. Without an understanding of the basic concepts of project management, managers may often find the software is confusing and hard to use. The first step in project management is to break the project down into measurable tasks and organize them into a hierarchy called the work breakdown structure (WBS). Different companies have different terms for the various levels in a work breakdown structure. Some levels include stages, steps, and tasks, or phases, activities, and tasks.
The next step in project management involves determining inter-task dependencies. Once the tasks have been listed and organized into a WBS, inter-task relationships need to be established. These relationships, also called dependencies or links, exist when the start or completion of one task is somehow related to the start or completion of another task. There are three types of inter-task dependencies: finish-start, start-start, and finish-finish. The tasks that must be performed first are called the predecessor tasks and those that follow are successor tasks.