This section presents an overview of project tasks and the output of a project scheduling tool.
- Project task list: The tasks that have been selected for the project are presented in this section.
- Task network: Project tasks and their dependencies are noted in this diagrammatic form.
- Timeline chart: A project timeline chart (Gantt chart) is presented. Please embed the Gantt chart in the document, as this is the way end users would see it.
Project task list
The first task will be to conduct an analysis of the current business situation. This will provide insight about a number of things such as organizational needs, software capabilities, and requirements. The organizational needs depend on the business goals as well as performance requirements. The second step is to develop a detailed plan of the steps to be followed during the implementation. In this, the IT and development staff will first be trained. The key vision of the intranet site will be established and also the information architecture. Tasks to consider under information architecture include aspects such as URL structure, metadata policy, and information storage design. The third step is development of the intranet web site. Key aspects to consider include application lifecycle management, developing proof of concept, and the general layout. The fourth task will be deployment. In this task, a pilot solution will be run. Server preparation will also take place in this step. The last task is to commence operations. This will involve installing software updates, maintaining services, and other tasks.
|(i)Assess organizational needs.
||(i)Training IT and other development staff||(i)Application lifecycle management||(i)Test a pilot system||(i) Enhance administrator operations
|(ii)Analysis of software capabilities
||(ii)Establishing the key vision of the site||(ii)Customization to global layout
||(ii)Web ownership operations
||(iii)Planning information architecture
||(iiii)Proof of concept||(iii)Deploy the intranet solution
|(iv)Develop custom navigation||(iv)Create metadata|
|(v)Training for content developers and approvers|
The following Gantt chart shows the timeline for the intranet web site project
2.1 Training IT and other development staff
2.2 Establishing the key vision of the site
2.3 Planning information architecture
3.1 Application lifecycle management
3.2 Customization to global layout
3.3 Proof of concept
4.2 Server preparation
4.3 Intranet solution deployment
4.4 Metadata creation
4.5 Training for content developers and approvers
The structure of the project team determines its productivity and efficiency in conducting various operations (Schwalbe, 2015). Development of an intranet web site requires a variety of skills due to the diverse range or responsibilities that must be taken into consideration. At the top is the project manager whose role is to ensure the smooth running of the entire project. The project manager will motivate workers, keep track of jobs, and ensure that deadlines are met. Below this level is the web designer. The web designer will be responsible for developing the web pages for the intranet. A graphic artist will be required to develop relevant graphics on a full-time basis. A developer will be responsible for creating applications and features on the intranet. A technical writer will be required to develop high-quality content for the intranet. Lastly, a communication specialist will be responsible for developing a communication plan and dissemination information via the intranet.
Reporting lines will follow the hierarchical structure identified in the organization. Progress reporting will be conducted via emails. File sending will be conducted through emails to save time and resources. Test logs will be used for error tracking. Inter-team communication will take place through emails and teleconferencing options where need arises. Intra-team communication will occur through weekly meetings.
Schwalbe, K. (2015). Information Technology Project Management. Boston, MA: Cengage Learning.