Makayla Maudsley October 26, 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.
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.
All the documents prepared all along the execution of the scheme must be lucid and articulate, so that everyone in the team and the stakeholders get to understand, each and every issue of it. This is an essential ingredient for a successful project. The final issue in project management is getting the user to check on the plan and see to that they are satisfied. A disgruntled user will not only reject the plan, but would also leave a bad reputation for the organization. So assuming that the requirements are met the customer is made to sign a customer satisfaction form and then the project is declared closed. The resources used on it are released and the project manager gets a day off!
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.
Regardless of terminology a company uses, the purpose of the WBS is to organize the project into various deliverables or summary reporting levels. Some of the traditional stage (or phase) levels in IS projects include project definition, analysis, design, development, testing, implementing, and project review. Whether a project has standard levels or not, the main purpose of these higher levels is to group the detail tasks, allowing project administrators to more easily track the project`s progress.
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.