Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 1 of 7
Due Date: Week 5 – Monday 5:00 pm
Weight: 10%
This is an individual assignment. There is an expectation that no two submissions will be the same.
Objectives
This assessment task relates to the following course objectives:
 Observe real world information technology problems and apply project
management principles and techniques to solve these problems;
 Employ a systems thinking approach to identify critical roles and
stakeholders in information technology projects;
 Demonstrate decision-making processes to solve a range of information
technology project issues;
 Utilise a range of organisational and self-management skills, emulating real
world practice of information technology project managers.
 value the importance of effective communication to solve problems on
information technology projects
Task
During the Project Initiation phase, an important artefact is the Project Charter. This artefact clearly
indicates for the project team and all stakeholders the project objectives, scope and vision. In this
assignment, you are provided with a case study project description below. You will create a Project
Charter for this project that will be managed following the adaptive methodology of Agile Scrum.
In a project managed using traditional project management methodologies, the Charter would be a
document of just a few pages (around 4) formally outlining the key objectives, schedule and
stakeholders. In an Agile project, this artefact would be displayed in the project team room.
Background
After top management determines which projects to pursue, then it becomes important to notify the
organisation about the projects. The Project Charter is used to authorise the project and nominate the
project manager. The Project Charter formally recognises the project and provides a summary of the
details of the project.
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 2 of 7
Requirements
For this assessment task, students are required to create a Project Charter for the case study provided:
The WOWS Project. The Project will be managed using the Agile SCRUM PM methodology. You
(project manager – PM) have made a presentation about your proposed approach for developing the
research report to the senior leadership committee meeting in order to get approval for the project. You
presented a Business Case to the committee to secure their approval for this project. The Business
Case includes many of the details that will form the Project Charter.
At the conclusion of the presentation, the committee authorised you to implement the project. To get the
project started, you need to draw up a Project Charter as the formal authority for the project. The project
sponsor has appointed you as the project manager. While preparing the Project Charter report, you
need to express clearly the vision (why do this project), the mission (what is to be done), and the success
criteria for this project.
You will also need to:

You may need to make other necessary assumptions in preparing the Charter but make sure these are
clearly stated. (You may be creative with your assumptions to ensure that your submission is unique.)
The Project Charter will be displayed on the wall in the project team room for the duration of the project
and includes information such as:

o Milestones/objectives for each sprint

o Governance

An initial template example for the Project Charter document is provided.
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 3 of 7
Submission
Please submit an electronic copy of the Project Charter based on the example Project Charter
template provided in Moodle. Submit only via Moodle. Partner students please refer to your course
lecturer for submission instructions. Please refer to the Course Description for information regarding
late assignments, extensions, special consideration, and plagiarism. A reminder all academic regulations
can be accessed via the university’s website, see: http://www.federation.edu.au/students/essentialinfo/publications/handbook
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 4 of 7
CASE STUDY—THE WOWS PROJECT
The WOWS (Web-based Oncological Working System) Project is a collaboration between the Centre
for Multimedia Computing, Communications, and Artificial Intelligence Research (MCCAIR) at
Federation University Australia and the Oncology division of the Western Gippsland Cancer Institute
(WGCI) at the Western Gippsland Hospital (WGH). The director of the WGCI is Phil Smart and the
director of the MCCAIR is Bill Bright. They have been appointed as the co-CEOs of WOWS. The
project involves the migration of the division’s current predominantly paper-based clinical
documentation system to an advanced digital solution that is better aligned with their goals of
improving quality of care with increased efficiency and accuracy.
Currently, a WGCI patient’s medical history of cancer (including a series of past and current
diagnoses, treatments, and responses) is reviewed by WGCI doctors upon the acceptance of a new
patient. The doctors then dictate their findings with a possible new diagnosis and suggested treatment
for the patient. References to the electronic versions of these dictations, intake notes as well as patient
demographic information are stored in the WGCI database. Paper copies of the intake notes,
supporting documents and together with the patient’s demographic information from WGCI are
consolidated in a ‘Patient File’. The Patient File is then used for analyses and discussions, and is
updated as changes occur to the patient’s clinical information. Such a system has the following
limitations:
• Paper-based system makes discussion and communication about patient care difficult:
Retrieval of patient’s information becomes difficult since a paper file cannot be accessed
remotely. Understanding a patient’s condition involves shuffling through the various, and
sometime voluminous, sheets of paper in the file and hence it is difficult to get a clear
overview of the patient’s condition.
• Inefficient process for synthesis and analysis of patient information: A system that stores
information in a single, inaccessible paper file has inherent inefficiencies which can be
addressed by making the system paperless. Electronic systems are easier to maintain, update
and access and hence more efficient than paper-based systems.
• Lack of centralized data repository: Since the patient’s information is not stored in a central
location and accessible remotely it introduces the danger of inconsistencies and inaccuracies
between multiple records.
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 5 of 7
The WOWS Project intends to introduce a high level of efficiency into the current process of treating
patients. Through this new process a patient’s clinical information and demographics will be entered
into WOWS (by the physicians or their assistants). Softcopies of documents supporting the patient’s
history can also be uploaded.
All subsequent changes to the patient record will be made on the system which will be able to track
changes to sensitive patient data. Through its web interface, the system will facilitate remote viewing,
updating reporting and will facilitate analysis and discussions through an enhanced presentation of
patient information.
The benefits of these improvements will be as follows:
• Visual Representation: Facilitates comprehension and discussion through an intuitive and
dynamic graphical representation.
• Accessible and updatable: Update and maintenance of accurate and integrated patient
information. Easy access to multiple sources and types of patient information.
• Centralized data: A centralized data repository allows for patient information to be retrieved
from one location, limiting the need to consult other repositories. In addition, a centralized
database allows for a one-step correction process in correcting data as needed.
As a result, WOWS facilitates the easy retrieval of accurate information which can be used to perform
detailed analysis and make faster and more accurate decisions that ultimately lead to enhanced service
to WGH’s patients.
WOWS strides to achieve these goals by providing a Web-based, database driven prototype system
designed to meet the stated needs of the division’s specialists to document, summarize, and view a
patient’s clinical history that is relevant to their treatment for cancer. This history takes the form of a
chronologically ordered list of episodes that include diagnosis (es), the treatment(s) he or she has
undergone, and the corresponding response(s). Each episode (event) is represented by a unique shape
and color scheme for quick visual recognition of the event type. This primary functionality of WOWS
is included in a module called View/Edit Patient Record. Other known modules include:
 Interface — An appealing interface with efficient navigation. The interface will also serve as
a portal to provide all cancer related information to doctors from both within the hospital and
external source.
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 6 of 7
 Login – Authenticates WOWS Users
 Search for Patient Record – Robust Search with Wildcard Ability for Patient Records
 Create Patient Record – Allows for the Input of New Patients into WOWS

 Log Out
 User Administration
 Reporting
 Online Help
It is hoped that the WOWS prototype developed in 6 months provides WGCI with the basic
functionality they require so that it can be deployed within the department soon after delivery of the
source code. The budget for the project is $700,000.
During the project management, you may make assumptions if it’s necessary, e.g., tasks may be
required but not explicitly listed; to breakdown certain relatively larger tasks into a number of smaller
subtasks for better management etc.
Reference: The GOLDS Project, http://www.heinz.cmu.edu
Assignment 1
ITECH 2250
IT Project Management Techniques
CRICOS Provider No. 00103D ITECH 2250 Assignment 1 Semester 2 2017– Project Charter Page 7 of 7
Assessment Criteria
Students work will be assessed as outlined below:

Assessment Feedback

Project Charter

Comments: