Isabel Leverrier November 10, 2020 Project Management
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!
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.
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
The next phase is the execution phase. Here the project must be monitored and managed. A schedule is derived which includes work breakdown, followed by allocation of tasks to people, allocation of resources and finally setting up deadlines for tasks. It is very important to have both a short-term goal and a long-term goal. While the long term goal is to get the product done, the short goals must be imposed by the project manager, who helps in guiding and motivating the members of the team working on the plan. Two important documents namely the issue log and the risk log which are both maintained by the project manager. The issue log keeps track of issues raised by the stakeholders and the risk log considers the vulnerabilities of a system.
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.
Complex projects require sophisticated software and scheduling tools, however simpler and more straightforward projects involving only a few people over a relatively short period of time require a much simpler approach. Usually, a simple project will have a few steps which are dependent on other steps taking place first, and will be relatively straightforward to coordinate. An example might be creating and implementing a marketing plan for a one person business, painting a single room, baking a cake, planning a weekend away for two, building a garden shed etc.