Example of a prosed outline for a Project plan.

The project I am proposing is a companywide update of all internal computer systems. In a large company this could take a year or more as computers are gradually replaced office by office. The necessity of a company-wide reboot would most likely be caused by a fundamental deficiency in the company’s current network. Likely reasons would include that the current network was built with some inherent flaw such as an incorrect assumption about company functions, that the current network was built piecemeal over time and is less efficient that a purposely designed network, or that the current network relies on legacy hardware that is no longer practical to keep.

The network update would affect every aspect of the company and thus would have to be approved by the top managers of the company. Because of the length of time involved the project would need its own manager separate from the normal head of IT affairs. Planning would probably take a third or more of the project’s total time as plans for the new network are submitted and reviewed by all of the parties involved. Priority would most likely be placed on updating the company’s internal database and network, with individual office’s computers and terminals being updated afterwards. Major changes would have to be timed to cause the minimum interruption in business operations, implying that the project would involve a lot of work outside of normal business hours.

Important Stakeholders:

Company Upper Management: Highest level of control. As the stakeholders in charge of determining the overall direction and stability of the company, they would have final say on the spending and functionality changes brought about by a companywide network update.

Head/Director of IT: High level of control. While ultimately answering to the upper management, would be expected to collect the information regarding the costs and benefits of the project and present them to the upper management, and would be considered responsible for the final results of the project.

Project Leader/Manager: High level of control. Would make the individual decisions concerning the project and manages the other employees working on the project, allowing the head of IT to focus on the general management of the IT department. Reports to the head of IT and occasionally communicates with the upper management.

Project Workers: Members of the project team who are managed by the project leader and perform most of the hands-on work. They will usually have a low level of control over the project, being able to make suggestions to the management but not having final say on most decisions.

Product Vendors: Most companies will not be making the new computer systems in-house and instead make a contract with one or more vendors for new systems. Vendors have a large financial stake in the project’s completion but will generally have little control beyond what products and services they can offer the project.

Company Employees: Employees not working on the project, who rely upon the company’s computer network to do their jobs. They have the lowest level of control, usually confined to providing input through surveys or random interview. In very small companies’ individual employees are more likely to have greater input into such a project because they are more likely to be in personal contact with the IT department and the company management.

Reference:

Watt, A. (2014). Project Management. Retrieved from https://opentextbc.ca/projectmanagement/chapter/chapter-5-project-stakeholders-project-management/