Project Charter Documents for 365performance.com.au Website Test Plan

This project charter proposal is for forming the test plan for the website of 365performance.com.au. The project overview, objectives, stakeholders, constraints, scope, and risks are discussed in detail. The stakeholders' interests and risks are prioritized according to their importance for the website. The project constraints include budget, information, teams, team size, schedule, access to developers, and infrastructure. The project scope includes project plan, design, website page, and testing. The project risks include team members' unfamiliarity, poor time distribution, inefficient communication, continuous changing requirements, and testing not complying due to changes in industrial rules.

Running head: PROJECT CHARTER DOCUMENTS
Project Charter Documents
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1PROJECT CHARTER DOCUMENTS
1. Introduction
The following project charter proposal has been made for forming the test plan for the
website of 365performance.com.au is helpful for forming the utilization of the documentation
and progressive analysis of the improved functional development. According Pedersen (2017),
the implication would be helpful for supporting the deployment of the test plan for the website
development.
1.1 Document Purpose
The alignment of the documentation would be helpful for easing the flow of the activities
and forming the significant information transfer process. The documentation for the processes
would be supportive for the forming the utilization of the operations (Doppelt 2017). The test
results are documented for ensuring that the website functionality would be easily checked and
evaluated. The draft plan for the testing of the website would also be done for ensuring that the
project for testing the website is completed successfully.
1.2 Project Overview
The project is developed for easing the test process and ensuring that the website review
of 365performance.com.au would be done easily. The website of 365performance.com.au is an
online health and fitness training services (365performance.com 2018). The website review
would be based on the study of the improved functional and development operations. The
features of the website would be reviewed for the alignment of the successive deployment of the
activities.
1.3 Project Objectives

2PROJECT CHARTER DOCUMENTS
The project is executed for the testing of the website with the help of test functions like
alpha testing, black box testing, prototype testing the functions, and final implication testing. The
project would meet the following objectives,
 To test the website for any errors with the help of alpha testing functions
so that the improved functional testing can be employed
 To deploy the test plan successfully for easing the alignment of the test
plan supporting the utilization of the improved communication
 To deploy black box testing for easing the using the go live testing
functions of the website for easing the utilization of the operations
 To improvise the development process for easing the utilization of the
operations of test functions
2. Stakeholders
2.1 Identifying Stakeholders
The stakeholders play a crucial role for the execution of the activities project activities for
the website testing the development of the comparative extension model. The alignment would
be helpful for forming the utilization of the improved functional and professional development.
The implication would be implied for allowing the deployment of the improved functional
development model (Mazzei 2014). The stakeholder analysis would be deployed for easing the
flow of operations and aligning the utilization of the successive integration model. The
stakeholders of the project would be responsible for the execution of the activities and following
the utilization of the activities. Recognition of various stakeholders is the first step, the outcome
has been listed below

3PROJECT CHARTER DOCUMENTS
Stakeholder Key Representative Description
Website
developer
Josh Lewis
lewis.josh@___mail.com
+61-XXXX-XXXX
Website developers ensure that the website is
developed very often. It is updated whenever
required.
Investor
Amanda Jones
amandajones@___mail.com
+61-XXXX-XXXX
Investors form a team and invest in the funds
required by the website for various purposes.
Employees
Yousef Chan
yousefchan@___mail.com
+61-XXXX-XXXX
Employees are officials who work for the website.
End user
Jonathan Kin
jonathankin@___mail.com
+61-XXXX-XXXX
End users are customers for websites. End users
use the website for their desired purposes.
Suppliers
Jim Lee
jimlee@___mail.com
+61-XXXX-XXXX
Suppliers are sources for information available on
the website. They ensure that the website contains
genuine data.

4PROJECT CHARTER DOCUMENTS
Management
Jim Chan
jimchan@___mail.com
+61-XXXX-XXXX
Management team takes care of the management
of the website. They maintain the entire
whereabouts of the website.
Tester
Katherine Jones
katherinejones@___mail.com
+61-XXXX-XXXX
Testers are officials that ensure that there are no
loopholes in the website’s functioning. They test
the management loopholes as well as technical
loophole in the website.
Stakeholder Design Development Maintenance Investment Testing Supply
Website
developer * *
Investor * *
Employees
End user
Suppliers *
Management *
Tester *

5PROJECT CHARTER DOCUMENTS
2.2 Analysing Stakeholders
Based on the stakeholders’ roles they are identified in the previous steps. Each
stakeholder’s interest on projects of 365performance.com.au can be determined. The results are
explained in the table below.
Stakeholder Interest
Website developer
Website developers find innovative ways in order to develop the
website. They try to make the website attractive by adding some
unique and genuine features to the website.
Investor Investors invest in the funds required by the website for its
development, designing or management.
Employees Employees work for a common goal that has to be achieved by the
website.
End user End users are common people who use the website for various
purposes.
Suppliers Suppliers are the one ones who provide data for the website of an
organization. The data supplied by suppliers should be genuine.
Management
Management officials take care of the management of the website.
They ensure that website is well managed, weather it is the contents
or the design of the website.
Tester Website testers are the ones who test for any faults in the functioning
of the website.
After determining the stakeholders’ interests, they are prioritized according to their
importance for the website 365performance.com.au. Through this method each stakeholder’s
interest, power or influence is mapped on a quadrant.

6PROJECT CHARTER DOCUMENTS
Meet the needs of the
stakeholders
Key importance
Least important Consideration
Interest of the stakeholders
P
O
W
E
R
Designing Management
Tester
Stakeholder Design Development Maintenance Investment Testing Supply
Website
developer * *
Investor * *
Employees
End user
Suppliers *
Management *
Tester *

7PROJECT CHARTER DOCUMENTS
3. Project Constraints
1. Budget: A definite budget has been decided for the designing, development, testing
and management of the website.
2. Information: The information provided in the website is made sure to be genuine and
relevant to the organization to which it belongs. The information collectors are required to
research properly regarding the organization and then update it in the website (Pedersen 2017).
The website is for public use so it should be ensured that the information in the website should
be appropriate. The information should be well conveyed to the common people who would refer
to the website for information regarding the organization.
3. Teams: employees are categorized into various teams according to their specialization.
A leader guides every team. The leader decides the works to be performed by each employee for
the website 365performance.com.au.
4. Team size: The divided teams have specific a specific team size. Each team may
consist of 9-10 employees. If the members exceeded the minimum count sub teams are formed.
These sub-teams might have their respective team leaders.
5. Schedule: Schedule is decided according to the deadline. If a deadline is approaching
then the schedule is decided accordingly. Employees might have to work extra.
6. Access to developers: The access to the developers of a website is limited to some
extent.
7. Infrastructure: A definite infrastructure has been designed for the functioning of the
website. The infrastructure contains details of how the teams would perform.

8PROJECT CHARTER DOCUMENTS
4. Project Scope
4.1 In Scope Items
Considering the project constraints, the features that needs to be tested, quality and
specification of the important stakeholders are mentioned below.
1. Project plan: In project plan the functioning of the website is planned. The further
works of the employees is also mentioned in the project plan.
2. Design: The designing of the website is very important. The infrastructure of the
website is designed for the functioning of the website.
3. Website page: A website page should be attractive enough for the customers to refer
to it. Website page needs to be updated regularly. It should also contain genuine data regarding
an organization.
4. Testing: Testing is important for the functioning of a website, testers check for
loopholes in the website.
4.2 Out of Scope Items
1. Transportation: In designing a website, transportation factor is not involved as there
is no requirement for transportation
2. Training: Training is not required for maintaining a website as the website use would
not require any specific training
3. Change management: Website management does not need a change management
planning as the changes would not be required in the project.

9PROJECT CHARTER DOCUMENTS
5. Project Risks
Along with stakeholder analysis, risk analysis is also important. It is a part of software
testing which reduces uncertain and undesirable events that may take place. By accessing the
risks in projects, effective solutions can be decided (Pritchard and PMP 2014). Risk management
consists of various steps. These steps are identifying the risks that could possibly take place,
accessing and prioritizing, the risks that are identified. The last step includes finding out ways to
overcome those risks.
Risk Category Risk Likelihood Impact Mitigation
Organizational
The team members are not
familiar with the
requirements in conducting
software testing in a
specific industry.
High High Provide necessary training to
the participants.
T echnical
Team members of the
testing team are unfamiliar
with the concepts and
operation of the website.
Medium High
Preparing a well-organized
kick-off by introducing the
project to help the team
understand the project
background of the website.
Schedule Poor time distribution High Medium
Use of better project
management tools. Leave
sufficient buffer when
planning.
Operational
Inefficient communication
within the team may
reduce the quality of the
work.
Medium High
Establish efficient
communication channel and
plan.

10PROJECT CHARTER DOCUMENTS
Technical
Continuous changing
requirements may bring
hardness to the execution
of the testing project of the
website.
Medium High Carefully review the test
strategy documentation.
Programmatic
Testing not complying due
to changes in industrial
rules. Low Medium
Keeping close eye on policy
and compliance rules updates
and act accordingly.

11PROJECT CHARTER DOCUMENTS
References
365performance.com 2018. CrossFit, Personal Training, Gym | 365 Performance. [online]
Available at: http://365performance.com.au/ [Accessed 3 Jun. 2018].
Coombs, C. R. 2015. When planned IS/IT project benefits are not realized: a study of inhibitors
and facilitators to benefits realization. International Journal of Project Management, 33(2), 363-
379.
Doppelt, B. 2017. Leading change toward sustainability: A change-management guide for
business, government and civil society. Routledge.
Falkheimer, J. 2014. The power of strategic communication in organizational development.
International Journal of Quality and Service Sciences, 6(2/3), 124-133.
Goetsch, D. L., and Davis, S. B. 2014. Quality management for organizational excellence. Upper
Saddle River, NJ: pearson.
Hopkin, P. 2017. Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Hornstein, H. A. 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2), 291-298.
Kuipers, B. S., Higgs, M., Kickert, W., Tummers, L., Grandia, J., and Van der Voet, J. 2014. The
management of change in public organizations: A literature review. Public administration, 92(1),
1-20.

12PROJECT CHARTER DOCUMENTS
Langley, B., Langley, L., Martin, J. B., and Hasselbacher, S. 2018. The Koasati Language
Project: A collaborative, community-based language documentation and revitalization model.
Insights from Practices in Community-Based Research: From Theory To Practice Around The
Globe, 319.
Mazzei, A. 2014. A multidisciplinary approach for a new understanding of corporate
communication. Corporate communications: an international journal, 19(2), 216-230.
McNeil, A. J., Frey, R., and Embrechts, P. 2015. Quantitative risk management: Concepts,
techniques and tools. Princeton university press.
Olson, D. L., and Wu, D. D. 2017. Data Mining Models and Enterprise Risk Management. In
Enterprise Risk Management Models (pp. 119-132). Springer, Berlin, Heidelberg.
Pedersen, P. (Ed.). 2017. Routledge handbook of sport communication. Routledge.
Pritchard, C. L., and PMP, P. R. 2014. Risk management: concepts and guidance. CRC Press.
Pritchard, D., Sperner, J., Hoepner, S., and Tenschert, R. 2017. Terrestrial laser scanning for
heritage conservation: the Cologne Cathedral documentation project. ISPRS Annals of the
Photogrammetry, Remote Sensing and Spatial Information Sciences, 4, 213.
Rajbhandari, P., Auron, M., Worley, S., and Marks, M. 2018. Improving Documentation of
Inpatient Problem List in Electronic Health Record: A Quality Improvement Project. Journal of
patient safety.
Sadgrove, K. 2016. The complete guide to business risk management. Routledge.
Schwalbe, K. 2015. Information technology project management. Cengage Learning.

13PROJECT CHARTER DOCUMENTS
Trittin, H., and Schoeneborn, D. 2017. Diversity as polyphony: Reconceptualizing diversity
Management from a communication-centered perspective. Journal of Business Ethics, 144(2),
305-322.
Van der Voet, J. 2014. The effectiveness and specificity of change management in a public
organization: Transformational leadership and a bureaucratic organizational structure. European
Management Journal, 32(3), 373-382.