Alexandra Faunce November 19, 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.
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!
Projects tend to slip for two reasons. Either Project Managers do not account for derivative activities such as vacation days when planning the overall project schedule, or they simply succumb to the pressure from management to compress the schedule. Now, present this schedule to the management team, and 8 times out of 10, the feedback you will get is "that`s too late". Eight times out of ten, you will be asked to revise the schedule and shorten it.
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 First and main benefit I think of is structure. These templates show you the best way and cycle to follow to tackle an important project. There are a lot of things people have to do along with planning their project. It often happens that managers have a many other things to deal with which often causes problems. These templates give you structure and clarity. They simplify the planning process which enables a smooth process. This simple yet professional way of presenting your project is bound to impress your boss. Confidence - These templates would help you create high quality documents. This would definitely boost your confidence while planning. They would help make your work look professional. This would help your employers trust and belief in you as well.
Most larger organisations have well developed and run IT departments. They usually have formal project offices with established plan templates and standards, with project office staff and automated plan analysis systems (for example seeking orphan tasks / missing dependencies and so on to measure overall `plan quality`). Smaller organisations - for example, `IT solutions houses` - may lack this level of sophistication but will certainly use detailed project plans.