<?xml version="1.0" encoding="UTF-8"?

>
<?xml-stylesheet type="text/xsl" href="PMP.xsl"?>
<pmp>
<info>
<title>Project Management Plan</title>
<author>Guardians of IT</author>
<identification>Repository/Assignment 2/TeamPMP</identification>
<status>Approved</status>
<changelog>
<change>
<version>0.1</version>
<date>28/08/14</date>
<reason>First version</reason>
</change>
<change>
<version>0.2</version>
<date>01/09/14</date>
<reason>Added more sections</reason>
</change>
<change>
<version>0.3</version>
<date>02/09/14</date>
<reason>Split managerial process into resource a
nd progress
monitoring
</reason>
</change>
<change>
<version>0.4</version>
<date>04/09/14</date>
<reason>Wrote up schedule, documentation policy<
/reason>
</change>
<change>
<version>0.5</version>
<date>05/09/14</date>
<reason>Wrote risk register</reason>
</change>
<change>
<version>0.6</version>
<date>05/09/14</date>
<reason>Finished project overview</reason>
</change>
<change>
<version>0.7</version>
<date>05/09/14</date>
<reason>Imported to Word, aesthetic changes</rea
son>
</change>
<change>
<version>1.0</version>
<date>05/09/14</date>
<reason>Final version - ready for submission to
team supervisor
</reason>
</change>
<change>
<version>1.1</version>
<date>11/09/14</date>
<reason>Marked up to XML</reason>

</change>
</changelog>
</info>
<content>
<section name="Project Introduction">
<subsection name="Project Overview">
<text>
<p>The Project Management Plan includes
all the information
we need
to deliver a high quality submis
sion for this project, on
time. The
plan will do this by making sure
everyone knows their
role and what
is expected of them. It also wil
l allow our
supervisor to keep an
eye on us, and what we plan to d
o.
</p>
<p>The XSLT stylesheets created in assig
nment 2 will be
used to
transform both an XML-encoded ve
rsion of this document,
and another
PMP provided by our team supervi
sor. We will also be
producing
specific XLST transformations as
directed by the team
supervisor.
</p>
<p>Assignment 3 will follow similarly to
the XLST
transformations
produced in assignment 2 but wil
l focus on
XML-encoded test cases
instead. As with the XML-encoded
PMPs,
general and specific
transformations will be created.
</p>
<p>Appropriate Task and Time recording l
ogs will be kept
for the
entire project. (That is, from t
he moment this document
was
created, until all deliverables
have been submitted.)
</p>
</text>
</subsection>
<subsection name="Project Deliverables">
<subsubsection name="Assignment 1">
<ul>

<li>Project Management Plan</li>

<li>Task recording log</li>
<li>Time recording logs</li>
</ul>
</subsubsection>
<subsubsection name="Assignment 2">
<ul>
<li>XML-Encoded version of our P
roject Management Plan</li>
<li>XML-Encoded version of sampl
e Project Management Plan
</li>
<li>XSLT stylesheet that transfo
rms entire Project Management
Plans to HTML
</li>
<li>XSLT stylesheet that transfo
rms the risk register of a
Project
Management Plan to HTML
</li>
<li>Task recording log</li>
<li>Time recording logs</li>
</ul>
</subsubsection>
<subsubsection name="Assignment 3">
<ul>
<li>XML-Encoded version of test
plan, including a full set of
test
cases
</li>
<li>XSLT stylesheet that transfo
rms entire test plans to HTML
</li>
<li>XSLT stylesheet that transfo
rms select parts of a test plan
to
HTML
</li>
<li>Task recording log</li>
<li>Time recording logs</li>
</ul>
</subsubsection>
</subsection>
<subsection name="Reference Materials">
<ul>
<li>IEEE Standard for Software Project M
anagement Plans:
http://ieeexplore.ieee.org/stamp
/stamp.jsp?tp=&arnumber=25325</li>
<li>Springrid Example Project Management
Plan:
http://wwwis.win.tue.nl/2M390/pr
ojects/spingrid/spmp.pdf
</li>
</ul>
</subsection>
</section>
<section name="Project Organisation">

<subsection name="The Team">

<subsubsection name="Group Leader: Mihidum Hetti
yahandi - 25117211">
<text>
<p>As group leader, Mihidum s role
is to coordinate the group s
activities. He will have
final say in any internal conflict and
be overall responsible f
or the group s work.
</p>
</text>
<email>vmhet1@student.monash.edu</email>
<phone>0488124402</phone>
</subsubsection>
<subsubsection name="Secretary: Hayden Razzell 25237667">
<text>
<p>As secretary, Hayden s role is
to oversee all documents and
ensure they remain organ
ised and up-to-date. He will also
organise the team reposi
tory and be responsible for maintaining
it.
</p>
</text>
<email>hraz5@student.monash.edu</email>
<phone>0424403318</phone>
</subsubsection>
<subsubsection name="Researcher: Katia Mercuri 25121669">
<text>
<p>As researcher, Katia s role is
to research and find any
required material and kn
owledge for the team. She will be
responsible for the accu
racy and relevance of all material and
knowledge she sources.
</p>
</text>
<email>kmmer5@student.monash.edu</email>
<phone>0431057311</phone>
</subsubsection>
<subsubsection name="Proof-Reader: Jordan Cook-I
rwin - 25132458">
<text>
<p>As group leader, Mihidum s role
is to coordinate the group s
activities. He will have
final say in any internal conflict and
be overall responsible f
or the group s work.
</p>
</text>
<email>jcoo18@student.monsah.edu</email>
<phone>0449952393</phone>
</subsubsection>
</subsection>

<subsection name="Structure">
<!--INSERT PHOTO HERE SOMEHOW-->
</subsection>
</section>
<section name="Managerial Process">
<subsection name="Monitoring and Controlling Mechanisms"
>
<subsection name="Progress Monitoring">
<text>
<p>The monitoring of progress wi
ll be done by the group leader using
the following means:
</p>
</text>
</subsection>
<subsection name="Tasks Spreadsheet">
<text>
<p>Tasks will be tracked on a sp
readsheet located at
Google Drive\FIT2043\Task
s . This allows the group leader
to check at a glance whi
ch tasks are completed and which
are not. The spreadsheet
also has the remaining amount of
days before due date. Ea
ch group member has access to this
to mark their own progre
ss and to see what tasks they have
been assigned.
</p>
</text>
</subsection>
<subsection name="Team Meetings"
<text>
<p>Every week, the group will fi
nd a suitable time to meet up and
discuss the project. Any
issues can be raised at these meetings
and tasks can be shuffle
d around to meet individual group
member s needs.
</p>
</text>
</subsection>
<subsection name="Resource Monitoring">
<text>
<p>The monitoring of resources w
ill be done by the group leader using
the following means:
</p>
</text>
</subsection>
<subsection name="Project Metrics">
<text>
<p>All work done by the team mem
bers needs to be administered. Each
team member has to fill
in their hours on a personalised excel
file in the team google

drives folder. This log needs to be

filled in each time the
team member finishes working on the
project. Every entry in
the log needs to have a description
of what they worked on,
and any other notable comments.
</p>
<p>These logs will be shared wit
h the Team Supervisor, and team
members must make the ef
fort to meet the amount of work other
team members are putting
in, and not slack off.
</p>
</text>
</subsection>
<subsection name="Schedule">
<subsection name="Assignment 2">
<text>Milestone
Descript
ion
Planned Date</text>
<text>
XML lang
uage designed
10th September</text>
<text>M1
XML lang
uage checked by tutor
11th September</text>
<text>
Own PMP
Endoded
17th September</text>
<text>
Provided
PMP Encoded
17th September</text>
<text>M2
Own PMP
checked by tutor
18th September</text>
<text>M3
Provided
PMP checked by tutor
18th September</text>
<text>
XSLT sty
lesheet for full PMP written
24th September</text>
<text>
XSLT sty
lesheet for selected sections of PMP written
24th September</text>
<text>M4
XSLT sty
lesheet for full P<P checked by tutor
25th September</text>
<text>M5
XSLT sty
lesheet for selected sections of PMP checked by tutor 25th September</text>
<text>M6
Submissi
on of assignment: complete
26th September</text>
</subsection>
<subsection name="Assignment 3">
<text>Milestone
Descript
ion
<text>
Test pla
ns written
3rd of October</
text>
<text>
Test cas
es written
5th of October</
text>
<text>
Test pla
n and cases XML encoded
8th of October</
text>
<text>M1
Test pla
n and cases checked by tutor
9th of October</
text>
<text>
XSLT sty

lesheet for complete test plans written

/text>

15th of October<
<text>M2

XSLT sty
16th of October<

<text>

XSLT sty
20th of October<

lesheet for complete test plans checked by tutor

/text>
lesheet for selected parts of test plans written
/text>

<text>M3
XSLT sty
lesheet for selected parts of test plans checked by tutor
23rd of October<
/text>
<text>M4
Submissi
on of assignment: complete
24th of October<
/text>
</subsection>
</subsection>
</subsection>
<subsection name="Ensuring High Standards/Quality Manage
ment">
<subsection name="Verification and Validation"
<text>A task will be checked against the
specifications listed on the assignment
sheet by each team member after
it has been finished. We will then ask
our tutor for feedback during ea
ch weekly tutorial. Any modifications
will be reviewed by every team m
ember.
</text>
</subsection>
<subsection name="Quality Assurance">
<text>Using lecture notes on writing XML
/XSLT as a guide, a detailed plan will
be completed for each assignment
. The plan will contain a specification
for all files to be created. Thi
s will include design and style decisions
ect.
</text>
<text>All relevant files will be checked
against a schema. Other files will be
checked by each team member for
syntax errors and to make sure they meet
their specification. The final v
ersion PDFs will then be checked against
the style specifications by all
team members.
</text>
</subsection>
</subsection>
</subsection>
</content>
</pmp>