Develop a Higher Education Website for Students - Project Charter Report

This project charter report outlines the development of a higher education website for students, including objectives, scope, MOV analysis, project management methodology, stakeholder analysis, leadership qualities, roles and responsibilities, WBS, and duration of activities.

Running head: PROJECT CHARTER REPORT
Project Charter Report
Develop a higher education website for students
Name of the Student:
Name of the University:
Author’s note:

1PROJECT CHARTER REPORT
Table of Contents
Introduction......................................................................................................................................2
1. Overview......................................................................................................................................2
1.1 Summary of Objectives.........................................................................................................2
1.2 Scope of the Project...............................................................................................................2
2. MOV analysis..............................................................................................................................3
3. Project Management Methodology..............................................................................................3
3.1 Selected Project Management Methodologies.......................................................................3
3.2 Identification of the Strengths and Weaknesses....................................................................4
4. Stakeholder Analysis and Communication Plan..........................................................................4
4.1 Analysis of Stakeholders.......................................................................................................4
4.2 Communication Plan.............................................................................................................5
5. Leadership Qualities and Roles & Responsibilities.....................................................................5
5.1 Leadership Qualities of Project Manager..............................................................................5
5.2 Roles and Responsibilities of team members........................................................................5
6. WBS.............................................................................................................................................6
6.1 Work Packages and WBS......................................................................................................6
6.2 Identified tasks list.................................................................................................................7
6.3 Duration of the Activities......................................................................................................9
6.4 Responsible Team Member.................................................................................................11
Conclusion.....................................................................................................................................12
Bibliography..................................................................................................................................13

2PROJECT CHARTER REPORT
Introduction
The following assignment had been developed for listing the elements of project in a
project charter document for the project of ‘Develop a higher education website for students’.
The project charter would serve the option for transferring the initial information to the project
team members and the aligning the utilization of the effective management and operations
(Ekrot, Kock & Gemünden, 2016). The charter document would help the project team for
understanding the basic information and initial requirements for the project. A WBS of project
plan is included this report for developing the understanding of the effective completion. The
complete charter document would align with the inclusion of the prospects of development and
understanding. The alignment would also be helpful for easing the simplification and
development.
1. Overview
1.1 Summary of Objectives
The objectives of the project of ‘Develop a higher education website for students’ are,
 To design and develop a website comprising of integrated database of higher
education
 To imply the use of project management principles and techniques for aligning
with the formation of operations
 To complete the project in the estimated time and budget exhaustion
1.2 Scope of the Project
The scope of the project of ‘Develop a higher education website for students’ is given
below,
In scope: The documentation of project progress, project plan development, design of
website, development of website, testing, and go live are the in scope items of the project.

3PROJECT CHARTER REPORT
Out of scope: The training and change management are out of scope items of the project
as they are not in need for the completion of the project.
2. MOV analysis
The MOV is the analysis of the project outcomes based on the factors of better, faster,
cheaper, and do more. The project deliverable of website for students has been analysed on these
factors as given below,
Better The development of the website would allow the integration of the information
and aligning the single database for the higher education information.
Faster The students would be able to access the information from a single platform and it
would align with the increasing the faster access to the information.
Cheaper Since no other resources would be required for accessing information, it would
consume less resources for the operations
Do More The students can provide feedback on the information and review it for improving
the operations
3. Project Management Methodology
3.1 Selected Project Management Methodologies
The waterfall methodology has been selected for the development of the website as it
would allow the utilization of the effective and improved operations. The activities would result
in listing the project for developing and designing the website using innovative tools and
operations. The following diagram would show the waterfall methodology model,

4PROJECT CHARTER REPORT
Figure 1: Waterfall Methodology
(Source: Mahadevan, Kettinger & Meservy, 2015)
Reason for selection of Waterfall Methodology: The waterfall methodology would allow
the use of sequential process and it would help in getting the following benefits for the project of
website development,
 Simple structure allowing the ease of project execution and development
 Supportive process as each of the prior step has been completed
 Ensuring the completion would allow the progress of the project
3.2 Identification of the Strengths and Weaknesses
Strengths Weakness
Steady process
All information is pre-assumed and analysed
All process would be completed
sequentially
Tracking is not possible
Inclusion of change management would be difficult
Time consuming
Strengths: The use of waterfall methodology would be helpful for defining the
completion of the project management operations. The waterfall methodology is helpful as it is a
steady process and involves the support and development of the effective operations. The

5PROJECT CHARTER REPORT
involvement of the processes would be aligned with the formation of the information access and
development. The utilization of the successive management process would involve the utilization
of the sequence completion of the project. The implication of waterfall methodology is helpful
for ensuring the effective completion of the project.
Weaknesses: The lack of possibility of progress tracking would be helpful for making
the major drawback for the use of the methodology. The management of the processes would
involve the utilization of the proper and effective management processing. The change
management would provide the major role for project of website development. However, using
waterfall methodology, the project would not get the opportunity of developing change
management process.
4. Stakeholder Analysis and Communication Plan
4.1 Analysis of Stakeholders
Stakeholder
s Power Influenc
e Role
Client High High Providing initial requirements for the project
Sponsors High Low Providing the resources required for the project
End Users Low Low Using the end product of the project
Project team Low High Executing the project activities
Contractor High Low Inspection the functionality of the website and making it Go
live
4.2 Communication Plan
Sender Information Method of Communication Frequency Receiver
Client Project Requirements Board Meeting Once Project
Manager
Project
Manager Project Requirements Reports Once Project team

6PROJECT CHARTER REPORT
Project
Manager Project Progress Meetings Weekly Client
Project team Project Progress Emails Monthly Project
Manager
5. Leadership Qualities and Roles & Responsibilities
5.1 Leadership Qualities of Project Manager
The leadership qualities of the project manager are,
Excellent Communication: the project manager must be able to communicate with the
project team members and the client about the requirements and progress of project.
Positive Attitude: the project manager must bring positivity in the operations for
motivating the project team members.
Competence and Integrity: The project manager must possess the qualities of
competence and integrity of the operations.
Team Builder: The project manager would have to make sure that project team would be
managed and executed by the use of the effective operations.
Cool, Calm, and Problem Solver: The project manager must have cool mind and he/she
would be responsible for solving the problems of the project calmly.
5.2 Roles and Responsibilities of team members
Resource Name Roles and Responsibilities
Analyst Analyzing the requirements of the project
Documenter Developing the project documents
Project Manager Management of the project activities
Planner Forming the project plan
Risk Analyst Mitigation the risk factors identified

7PROJECT CHARTER REPORT
HR manager Managing the resources of the project and communication process
Designer Developing the design of the website
Tester Testing the functionality of the website developed
Developer Developing the website supporting the inclusion of the information of the
higher studies
Consulting
Engineer Inspecting the final operations of the website
6. WBS
6.1 Work Packages and WBS
The work breakdown structure for the project of Develop a higher education website for
students would comprise of developing an understanding of the progress of the project and align
it with the formation of the smart and effective management process. The implication of the
effective and smart project completion would be aligned for developing the smart identification
of the project completions. The work packages of the project include the phases of initial phase,
planning phase, execution phase (includes work packages of website designing and website
developing), and closure. The initial phase is the first work package required for developing the
effective and improved operation development for initialization of the project operations and it
includes the activities of requirement analysis, charter documentation, resource accumulation,
submission of documents, review and signs off, and kick off. The second work package is the
planning phase that would result in identification of the activities required for the completion of
the project and forming the schedule for the activities. The activities of this work package are
activities are listed, scheduling of the project activities, risk management planning,
communication planning, and plan approvals. The execution phase is the work package
comprising of sub work packages of website designing and developing. It is the main work
package as the website development and designing is the most crucial aspect of modifying the
influence of managing the configuration of the operations. The activities of the website designing
include interface of website developed, review of functions, design development, simulation of

8PROJECT CHARTER REPORT
design, and design approval. The activities of website development include functions are
programmed, website features are developed, structure of website is developed, all functions are
integrated, alpha testing, beta testing, and system developed. The final work package of the
project is closure that results in termination of the project. Final documents are made, inspection,
submission of documents, review and sign off, and closed are the inclusive work of the work
package. The following is the work breakdown structure for the project,
Develop a higher
education website for
students
Initial Phase
Requirement
Analysis
Charter
Documentation
Resource
Accumulation
Submission of
documents
Review and Sign off
Kick off
Planning Phase
Activities are listed
Scheduling of the
project activities
Risk management
planning
Communication
Planning
Plan Approvals
Execution Phase
website Designing
Interface of website
developed
Review of Functions
Design
Development
Simulation of design
Design Approval
Website Development
Functions are
programmed
Website Features
are developed
Structure of website
is developed
All functions are
integrated
Alpha testing
Beta testing
System Developed
Closure
Final Documents are
made
Inspection
Submission of
documents
Review and Sign off
Closed
Figure 1: Work Breakdown Structure of Project
(Source: Created by the author)
6.2 Identified tasks list
The project of ‘Develop a higher education website for students’ has been developed for
designing and developing the website for the students so that they can access information and
develop an identification of the aspects of development. The identified activities would be
inclusive of documentation and planning process along with the website development and
designing. The task list is given below,
WBS Task Name
0 Develop a higher education website for students
1 Initial Phase

9PROJECT CHARTER REPORT
1.1 Requirement Analysis
1.2 Charter Documentation
1.3 Resource Accumulation
1.4 Submission of documents
1.5 Review and Sign off
1.6 Kick off
2 Planning Phase
2.1 Activities are listed
2.2 Scheduling of the project activities
2.3 Risk management planning
2.4 Communication Planning
2.5 Plan Approvals
3 Execution Phase
3.1 website Designing
3.1.1 Interface of website developed
3.1.2 Review of Functions
3.1.3 Design Development
3.1.4 Simulation of design
3.1.5 Design Approval
3.2 Website Development
3.2.1 Functions are programmed
3.2.2 Website Features are developed
3.2.3 Structure of website is developed
3.2.4 All functions are integrated

10PROJECT CHARTER REPORT
3.2.5 Alpha testing
3.2.6 Beta testing
3.2.7 System Developed
4 Closure
4.1 Final Documents are made
4.2 Inspection
4.3 Submission of documents
4.4 Review and Sign off
4.5 Closed
6.3 Duration of the Activities
The project is divided into phases and the completion of the activities would be summed
for getting the duration of the phase. The addition of the time taken for the completion of the
each of the phases would result in developing the final project deliverable. The following is the
time taken for the project activities,
WB
S Task Name Duration Start Finish
0 Develop a higher education website for students 66 days Mon 10/1/18 Mon 12/31/18
1 Initial Phase 10 days Mon 10/1/18 Fri 10/12/18
1.1 Requirement Analysis 2 days Mon 10/1/18 Tue 10/2/18
1.2 Charter Documentation 2 days Wed 10/3/18 Thu 10/4/18
1.3 Resource Accumulation 4 days Fri 10/5/18 Wed 10/10/18
1.4 Submission of documents 1 day Thu 10/11/18 Thu 10/11/18
1.5 Review and Sign off 1 day Fri 10/12/18 Fri 10/12/18
1.6 Kick off 0 days Fri 10/12/18 Fri 10/12/18

11PROJECT CHARTER REPORT
2 Planning Phase 12 days Mon 10/15/18 Tue 10/30/18
2.1 Activities are listed 2 days Mon 10/15/18 Tue 10/16/18
2.2 Scheduling of the project activities 3 days Wed 10/17/18 Fri 10/19/18
2.3 Risk management planning 4 days Mon 10/22/18 Thu 10/25/18
2.4 Communication Planning 3 days Fri 10/26/18 Tue 10/30/18
2.5 Plan Approvals 0 days Tue 10/30/18 Tue 10/30/18
3 Execution Phase 58 days Mon 10/1/18 Wed 12/19/18
3.1 website Designing 12 days Wed 10/31/18 Thu 11/15/18
3.1.1 Interface of website developed 3 days Wed 10/31/18 Fri 11/2/18
3.1.2 Review of Functions 2 days Mon 11/5/18 Tue 11/6/18
3.1.3 Design Development 5 days Wed 11/7/18 Tue 11/13/18
3.1.4 Simulation of design 2 days Wed 11/14/18 Thu 11/15/18
3.1.5 Design Approval 0 days Thu 11/15/18 Thu 11/15/18
3.2 Website Development 58 days Mon 10/1/18 Wed 12/19/18
3.2.1 Functions are programmed 4 days Fri 11/16/18 Wed 11/21/18
3.2.2 Website Features are developed 3 days Thu 11/22/18 Mon 11/26/18
3.2.3 Structure of website is developed 5 days Tue 11/27/18 Mon 12/3/18
3.2.4 All functions are integrated 6 days Tue 12/4/18 Tue 12/11/18
3.2.5 Alpha testing 3 days Wed 12/12/18 Fri 12/14/18
3.2.6 Beta testing 3 days Mon 12/17/18 Wed 12/19/18
3.2.7 System Developed 0 days Mon 10/1/18 Mon 10/1/18
4 Closure 8 days Thu 12/20/18 Mon 12/31/18
4.1 Final Documents are made 2 days Thu 12/20/18 Fri 12/21/18
4.2 Inspection 4 days Mon 12/24/18 Thu 12/27/18
4.3 Submission of documents 1 day Fri 12/28/18 Fri 12/28/18

12PROJECT CHARTER REPORT
4.4 Review and Sign off 1 day Mon 12/31/18 Mon 12/31/18
4.5 Closed 0 days Mon 12/31/18 Mon 12/31/18
6.4 Responsible Team Member
The project comprises of a number of resources for taking care of the activities and
aligning with the completion of the effective project completion. The project team would
comprise of Analyst, Documenter, Project Manager, Planner, Risk Analyst, HR manager,
Designer, Tester, Developer, and Consulting Engineer. The following is the responsible activities
of the project human resources for the completion of the activities,
Resource Name Responsibilities Work
Analyst Requirement Analysis 16 hrs
Documenter
Charter Documentation
Submission of documents
Final Documents are made
Submission of documents
48 hrs
Project Manager
Resource Accumulation
Review and Sign off
Review and Sign off
48 hrs
Planner
Activities are listed
Scheduling of the project
activities
40 hrs
Risk Analyst Risk management planning 32 hrs
HR manager Communication Planning 24 hrs
Designer Interface of website developed
Review of Functions
Design Development
192 hrs

13PROJECT CHARTER REPORT
Website Features are developed
Structure of website is developed
All functions are integrated
Tester
Simulation of design
Alpha testing
Beta testing
64 hrs
Developer Functions are programmed 32 hrs
Consulting Engineer Inspection 32 hrs
Conclusion
It can be concluded from the assignment that the development had been effectively
implied for easing the utilization of the formation development. The alignment had been
involved for improving the management of the successive inclusion management. The
involvement had been implied for easing the successful development model. The completion of
the project of ‘Develop a higher education website for students’ had been done for developing a
website for the students for accessing information of higher studies. A WBS of project plan was
included this report for developing the understanding of the effective completion. The complete
charter document had aligned with the inclusion of the prospects of development and
understanding. The alignment had also helped for easing the simplification and development.

14PROJECT CHARTER REPORT
Bibliography
Amrollahi, A., Ghapanchi, A. H., & Talaei-Khoei, A. (2014). Three decades of research on
strategic information system plan development.Communications of the Association for
Information Systems, 34(1), 84.
Bentahar, O., & Cameron, R. (2015). Design and Implementation of a Mixed Method Research
Study in Project Management. Electronic Journal of Business Research Methods, 13(1).
Braglia, M., & Frosolini, M. (2014). An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), 18-29.
Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management
techniques. A theoretical framework. Journal of Risk Research, 18(2), 232-248.
Cs.bilkent.edu.tr. (2018). A Guide To Project Management Body Of Knowledge. Retrieved 28
August 2018, from http://www.cs.bilkent.edu.tr/~cagatay/cs413/PMBOK.pdf
Drury-Grogan, M.L., 2014. Performance on agile teams: Relating iteration objectives and critical
decisions to project management success factors. Information and Software
Technology, 56(5), pp.506-515.
Ekrot, B., Kock, A. & Gemünden, H.G., (2016). Retaining project management competence—
Antecedents and consequences. International Journal of Project Management, 34(2),
pp.145-157.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Ghosal, S., Chaturvedi, S., Taywade, A., & Jaisankar, N. (2015). Android application for ticket
booking and ticket checking in suburban railways. Indian Journal of Science and
Technology, 8(S2), 171-178.

15PROJECT CHARTER REPORT
Giorgadze, L., Alibiev, D., Chirico, G. D., & Kazhikenova, A. S. (2017). Minimization of
product defects by the means of implementing correct test pyramid in the software
development process.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational excellence.
pearson.
Mahadevan, L., Kettinger, W. J., & Meservy, T. O. (2015). Running on Hybrid: Control Changes
when Introducing an Agile Methodology in a Traditional" Waterfall" System
Development Environment. CAIS, 36, 5.
Pmi.org. (2013). A Guide To Project Management Body Of Knowledge. Retrieved 28 August
2018, from https://www.pmi.org/-/media/pmi/documents/public/pdf/pmbok-standards/
pmbok-guide-5th-errata.pdf
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Works.gov.bh. (2018). A Guide To Project Management Body Of Knowledge. Retrieved 28
August 2018, from https://www.works.gov.bh/English/ourstrategy/Project
%20Management/Documents/Other%20PM%20Resources/
PMBOKGuideFourthEdition_protected.pdf
Www2.fiit.stuba.sk. (2018). A GUIDE TO PROJECT MANAGEMENT BODY OF
KNOWLEDGE. Retrieved 28 August 2018, from
http://www2.fiit.stuba.sk/~bielik/courses/msi-slov/reporty/pmbok.pdf