An intranet is a private communications network within a company. Developing an intranet project plan is a significant undertaking as the result of the project will affect the whole company. The project plan should focus on a long-term design with effective content management that utilises the technologies that make it a useful tool across multiple computer platforms. An intranet project plan should, at a minimum, cover the following planning topics: the discovery of what intranet needs are for your company, the implementation of the intranet, content management, security management, quality assurance, technology updates and intranet launch.
- Skill level:
Collect intranet requirements from end-users using a questionnaire. Set up meetings, facilitated with questionnaires, with individuals from different departments to gather requirements on the intranet project. The requirements will establish a baseline for the development of the project plan. A questionnaire, per gantthead.com, is an information-gathering tool to determine a client's business goals to establish an intranet, as well as the technical and organizational infrastructure needs to support it.
Determine the timing, resource needs and durations of each intranet requirement by discussing it with the individuals or groups that will work on them. Set up follow-up meetings after your requirement sessions with the individuals who will develop those requirements, as well as the individual who asked for the requirements. This will insure ensure that what is being requested can be done as part of the intranet project.
Categorise requirements by content, security, technology, quality assurance and implementation. These categories enable the project manager to delve into more detailed discussions with the end-users. The project details behind each requirement within the categories allow the project manager to better understand the overall project plan.
Enter the intranet project plan sections into your project plan application. The intranet project plan sections to be entered, with optional subcategories, are as follows: 1.) Design: content, technology and security; 2.) Development: intranet mapping, content, code and infrastructure; 3.) Quality Assurance: content, code, and technology; and 4.) Deployment: release and monitor. Enter these sections into your project plan application.
Enter the categories, with requirements, under each section of your intranet project plan timeline within the project plan application. By placing the categories into sections, your intranet project plan is formed with the details needed to manage your project. Remember to place a project end date, as a project has an end. According to viney.com, the difference between an intranet project and a steady state intranet model is the project-funded resources have an end date.
Review the project plan with other project managers to make sure it makes sense. Take the time needed to go over the project plan and challenge the project team on the content, timeline and delivery. Ask the following questions: Can we do this intranet project in the determined time period? Are the sections in proper order? If not, where can we make timeline changes? At the end of the project, will the implemented intranet be what our end-users requested?
Tips and warnings
- Begin with the end in mind.
- Stay off the cutting edge.
- Have policies and procedures in place.
- 20 of the funniest online reviews ever
- 14 Biggest lies people tell in online dating sites
- Hilarious things Google thinks you're trying to search for