Kristin Fink October 25, 2020 Project Management
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.
In addition, the schedule provides project teams with a map for project execution and offers a baseline for tracking progress and managing changes. It can be used as a checklist to make sure that all necessary tasks are performed. If a task is on the schedule, the team is committed to doing it. In other words, the project schedule gives the means by which the project manager brings the team and the project under control. The visual representation of a schedule is a timeline chart. It is created such that it depicts the tasks of the projects, the duration and the sequencing of them, and the major milestones of the project. The Gantt chart is the most popular timeline chart.
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.
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.
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.
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.