Christin Maur November 7, 2020 Project Management
Then you bring in your techies to ask them to prepare a project scope document along with a report, in which the specific technologies and the steps to carry out the plan are decided. The scope and the feasibility of it are studied and a decision on whether to take it up or to pass on the offer is made. This official document contains everything from primary goals of the scheme to the deliverables expected of it. Once the document is perused and the upper management gives it a green signal, the project is considered as taken!
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.
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.
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.
With simple projects, a tool such as a Gantt chart may make over complicate the project scheduling. Unless all team members are trained in the tool then the use of the tool may itself lead to poor communication and an unsatisfactory result. A simple project such as those identified above may only require a timetable and/or an action plan. All those in the project team should be communicated with as to their tasks content and timing. Timetables can then be negotiated and agreed, actions lists or diaries/calendars can be used for recording and planning purposes.
Most team members often feel overwhelmed with the prospect of having to worry about timelines and tasks they need to accomplish over the duration of the work effort. Helping them to stay focused and organized is a key skill that a PM must bring to the table when running a project.