Heike Moeller December 2, 2020 Project Management
Now, you will notice that some of these tasks will be ongoing throughout the project, like managing team performance, assuring quality, and schedule control. Before each project, you should make a checklist and a list of deliverables that will keep you on track throughout your project. There will be a lot of similarities from project to project, so after the first time this will be very easy to do. You may want to schedule yourself to do some tasks weekly or monthly, depending on the task and the length of your project. Maybe you want to add in some of your own tasks, or maybe there are some that you can live without, but this is a great start to managing any project.
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.
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.
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.
Among all the tools at our disposal for managing projects, checklists are perhaps the simplest and most productive means of building consistency in work practices. Checklists are useful in almost every field of human endeavor, and in particular where repeatability and systematic action drive performance. Yet they are still much under-used in the planning and managing of projects.