Project Plan
Introduction
Writing the project plan provides a structured framework for thinking about how the project will be conducted. A significant value of writing a project plan is the process rather than the outcome. It forces the players to think through their approach and make decisions about how to proceed. A project plan can be formal, as stakeholders and supporters approve documents and procedures used to guide both project execution and project control. Overall, project plans create a system of document forecast assumptions and decisions, push communication amongst stakeholders, substantiate approved scope, cost and schedule baselines.
In this paper, we will observe a project plan in its entirety. Of how each structure is dependent on the other to keep activities on path. A marketing project manager takes an in-depth look into processes and methods commonly used among project management to meet successful outcomes in this case the launch of an intranet.
Intranet project management differs slightly from traditional management tasks in that it contains both technical and non-technical users, managers, information technologists, and sometimes, users of the project. Traditional, hierarchical command structures and permanent staffing patterns are not found in project teams. Instead, the team members are given responsibility and assigned to the project. Team members are often juggling their regular duties with multiple projects.
In this scenario, the CVO Marketing department is heading the CVO Intranet Project. As most projects only exist for an arranged duration of the project, coming into commencement as described in the closure plan, this project differs. The CVO Intranet Project is a launch phase of an informational portal. From here, it is most likely that the Marketing team will continue with phases and forever changing the make-up, information and tools.
Basis for CVO Intranet One of the most modern and most potent tools used by fortune 500
Writing the project plan provides a structured framework for thinking about how the project will be conducted. A significant value of writing a project plan is the process rather than the outcome. It forces the players to think through their approach and make decisions about how to proceed. A project plan can be formal, as stakeholders and supporters approve documents and procedures used to guide both project execution and project control. Overall, project plans create a system of document forecast assumptions and decisions, push communication amongst stakeholders, substantiate approved scope, cost and schedule baselines.
In this paper, we will observe a project plan in its entirety. Of how each structure is dependent on the other to keep activities on path. A marketing project manager takes an in-depth look into processes and methods commonly used among project management to meet successful outcomes in this case the launch of an intranet.
Intranet project management differs slightly from traditional management tasks in that it contains both technical and non-technical users, managers, information technologists, and sometimes, users of the project. Traditional, hierarchical command structures and permanent staffing patterns are not found in project teams. Instead, the team members are given responsibility and assigned to the project. Team members are often juggling their regular duties with multiple projects.
In this scenario, the CVO Marketing department is heading the CVO Intranet Project. As most projects only exist for an arranged duration of the project, coming into commencement as described in the closure plan, this project differs. The CVO Intranet Project is a launch phase of an informational portal. From here, it is most likely that the Marketing team will continue with phases and forever changing the make-up, information and tools.
Basis for CVO Intranet One of the most modern and most potent tools used by fortune 500
References: (2004). Success Project Communications Plan. A Project of the Medical College of Georgia. Version 1.0. Retrieved June 13, 2006 from www.mcg.edu/success/pdf/Communications.pdf. Fichter, D., Cervone, L. (2001). Intranet Project Management. Intranets Enterprise Strategies and Solutions. Retrieved June 16, 2006 from http://www.intranetstoday.com/Articles/?ArticleID=5452. Finne, T. (2005). Casting a Wide Net. Internal Auditor; Vol. 62 Issue 4, p29-33. Retrieved June 4, 2006 EBSCOhost database, University of Phoenix Online Library Collection. Guengerich, S. (1997). Building the Corporate Intranet. New York: John Wiley & Sons, Inc., p1. Hills, M. (1997). Intranet Business Strategies. New York: John Wiley & Sons, Inc., p8. Labrosse, M. (2005). Build the Business with Powerful Project Management. Industrial Management. Vol. 47 Issue 1, p22-26. Retrieved May 20, 2006 from EBSCOhost database, University of Phoenix Online Library Collection. Lovett, G. (2004). Project Audit Support: Know Where You Stand. Source Experts; Vol. 2 Issue 4, p56-67. Retrieved June 16, 2006 from www.evoknow.com/doc.php?id=project_audit_support.pdf. Loewe, L (2002). Global computing for bioinformatics. Briefings in Bioinformatics; Vol. 3 Issue 4, p377. Retrieved June 3, 2006 from EBSCOhost database, University of Phoenix Online Library Collection. Rafamanickam, D. (2005). Successful Project Management Using Agile Methodology. Journal of the Quality Assurance Institute. Vol. 19 Issue 3, p15-18. Retrieved June 2, 2006 from EBSCOhost database, University of Phoenix Online Library Collection. Shafikova, G. (2004). Managing Web Development Projects. Journal of Educational Technology Systems; Vol. 33 Issue 2, p67-101. Retrieved June 3, 2006 EBSCOhost database, University of Phoenix Online Library Collection Wagner, R., L