Claudia Eggers November 30, 2020 Project Management
Project Managers are all too familiar with the project triangle. We know we can shorten a schedule by either (a) reducing the scope of the project, or (b) adding more resources to it. Unfortunately, management either has not seen that triangle or, more likely than not, simply chooses to ignore it. Consequently, Project Manglers who are more interested in pleasing upper management than keeping honest have come up with their own universal algorithm for shortening project schedules. Take the number of days that need to be cut from the schedule, divide it by the number of major milestones, and then deduct that number from the duration of each milestone. In other words, if a project comprising of 4 major milestones is estimated to last 6 months, but you need to reduce it by one month, you`d take 20 days, and divide it by 4. Take the answer (5), and deduct it from the duration of each milestone. And voila! Works every time.
If you are a manager responsible for managing projects, you will eventually need to delegate tasks to individuals or teams. And so it is important that the tool yo are using to manage the project be able to keep track of who is performing what task, and also allow you to add new documents and notes with ease. Communication is important with any project. You should have the capability to have good communication with your team through email reminders and keep track of how the project is going at any moment. And a good project management tool will allow you to have online discussions with your project team no matter their location. A reliable tool for managing a project is essential and will serve you well.
A methodology guides an organization or an individual from start to finish. A project management methodology probes deep in the various steps of the project management life cycle. It is a checklist of tasks to be performed in the various steps of the plan. The project management methodology gives the manager a definite control over the scheme, allowing him or her to maneuver the team toward the destination called success. A project without a methodology would be a train running without tracks. It further allows the project manager to standardize the protocols of a plan, thereby providing a general structure of the steps, which can be followed in all other future projects.
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.
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.
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.