Skye Clemes October 29, 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.
All projects have control points and required deadlines, where progress is monitored and measured. In the event that a deadline is missed then the overall impact on project completion time can be assessed, and if necessary new timetables drawn up, re-negotiated and agreed. Action Plans are lists of tasks/individual actions that are carried out to achieve a single and objective or outcome - in this case, the specific project. Action Plans focus on the achievement of a single goal, the action may then be translated in to a to-do list/diary cum calendar which cover many goals.
Project scheduling should be considered the central piece of any project management software. Without the possibility to easily schedule all the tasks of a project there would be little expectation regarding the efficiency of controlling complex projects. However a project scheduling software should simplify a project managers work and not complicate it.
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.
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.
The production and agreement of the business requirements is a substantial part of the overall project schedule and may take many iterations before it is finally approved. The project manager usually works with other departments or teams to put the document together. They will probably use Brainstorming and Interviewing techniques to help with this process and may even build a prototype