Assessment item 2—Group case study
________________________________________
Due Dates: See Moodle for the exact date and time for the submissions listed below.
Individual submissions:
Sub-deliverable 1: End of week 6
Sub-deliverable 2: End of week 7 (plus first compulsory peer assessment due)
Sub-deliverable 3: End of week 8 (plus second compulsory peer assessment due)
Sub-deliverable 4: End of week 9
Sub-deliverable 5: End of week 10
Final Group Submission: End of week 11 (plus final compulsory peer assessment due)
________________________________________

Contents
________________________________________ 1
1 Overview 3
2 The Case Study 4
2.1 Background 4
2.2 Milestones 6
2.3 Initial Data 7
2 Assessment Tasks 10
3.1 Part A: Developing the schedule 10
3.2 Part B: Modifying the schedule 12
3.3 Part C: Tracking Progress 15
3.4 Assumptions 19
4 Assessment Submissions 20
4.1 Individual submission of sub-deliverables 20
4.2 Peer Assessment 20
4.3 Final Group Submission 21
5 Marking Guide – Group Final Submission 23
Appendix 1: Status Report Template 24

1 Overview
This case study simulates a project management scenario where the student takes on the role of project manager. Students are required to use Microsoft Project 2013 management software as part of this assessment task.
This is a group assignment with a maximum of four members per group. However, note that all members are also expected to attempt all parts of the assignment individually as assessment item sub-deliverables 1- 5. Members of the group are required to submit their own individual attempt for each of the sub-deliverables in Moodle before the group meets to consolidate answers to produce the -group solution-. There are separate submission areas and due dates for the individual submissions. On time submission of the 5 sub-deliverables is worth a total of 5 marks, but these submissions may also be used to assess individual contributions and may impact on a student’s final mark.
Groups must meet at least once a week to produce the “group solution” for the work scheduled for completion in that week. This solution should then be added to the developing final group solution.
It is also important to meet early in week 10 to produce the updated schedule to be used to complete the Part C questions and status report. Each group is responsible for providing their own status data. This means that the group members must collaborate on this and ensure that all members are working with the same PartC.mpp file when completing the Part C questions. This is explained further in part C.
There is one final group solution to be submitted at the end of the assignment. It is worth 35 marks and is to be submitted by only one member of the group. The names and student ids of all members of the group must appear clearly on the coversheet of the final assessment submission.
Peer assessment and your individual submissions will also be used to assess group member contributions. If any member of a team is not contributing satisfactorily to the group then he/she may have marks adjusted and/or be asked to leave the group and be required to complete the assignment as an individual.
If you are having difficulties within your group you must alert your tutor/lecturer as early as possible.
To assist students in their assessment solution development the following information is provided:
• A product development case description.
• Specific assessment questions that must be answered.
• Information regarding the submission of the assessment.
• Marking criteria.
Where necessary, students are expected to find relevant information in the academic literature to justify their answers. Students may have to make assumptions and argue the pros and cons for any recommendations that they make. Any assumptions made must be clearly documented in the answers.
2 The Case Study
2.1 Background
Dalmerdal Ltd is a small family business that provides ICT solutions to other small businesses and individuals. As part of their 2015-20 strategic planning process, it was identified that the business wanted to give back to the community by engaging in social innovation projects. The staff had many ideas about what type of project they wanted to run. To decide on the project, Ms Ellin Jannali, the CEO ran a competition. Staff could enter a concept document outlining their proposed projects and the board of Directors, which consisted of Ellin and her sister Ms Bindi Jannali, would choose the best proposal.
The successful project will be able to begin after 1 October 2016. This will be the official start date of the project and should be noted in the Project Information section in Microsoft Project.
You are an employee of Dalmerdal Ltd and have been working as a project manager in the product development and service unit. The people involved in this case study are:
• You (Ms. Colebee), the project manager.
• Ms Ellin Jannali, CEO
• Ms Bindi Jannali, Director
• If your proposal is successful - A project team where you will be able to draw from the following skill sets
o Software engineer/s
o Business analyst/s
o Test Engineer/s
o Marketing officer/s
o Project officer/s
You are not sure about the type of project you want to suggest so you start thinking about the last project you worked on. The project was the development and implementation of a class timetabling solution for the local high school. You start searching the internet about community concerns related to high school education.
After some time you find information about school retention rates on the Australian Bureau of Statistics website.
In 2011, the apparent retention rates for full-time Aboriginal and Torres Strait Islander students from Year 7/8 to Years 10 and 12 were 99% and 49% respectively.
Apparent retention rates to Year 10 and beyond for Aboriginal and Torres Strait Islander students have steadily increased since 2001. The apparent retention rate from the first year of secondary school to Year 10 rose from 86% in 2001 to 99% in 2011, while at the Year 12 level the increase was from 36% in 2001 to 49% in 2011 (see graphs).
APPARENT SCHOOL RETENTION RATES, full-time students by Indigenous status— 2001–2011

(a) Other series includes non-Indigenous students and those whose Indigenous status was 'not stated'.
Source: ABS, Schools, Australia, 2011 (cat. no. 4221.0).

Retrieved from:
http://www.abs.gov.au/AUSSTATS/abs@.nsf/lookup/4704.0Chapter350Oct+2010
The large gap between the retention rates of Aboriginal and Torres Strait Islander students and non-indigenous students motivates you to design a project around school retention. You have a look at websites providing translations of Aboriginal and Torres Strait Islander languages. The grandpapencil website which can be located at the following address http://www.grandpapencil.net/austral/abword/aba.htm states that the word ‘Auminthina’ means ‘to remain’ and you decide to call the project ‘The Auminthina Project’.
You decide to develop an app for mobile phones that link students to a number of resources they can use to assist them to stay in school. You think it would be good if students could post questions online and have teachers and experts in the different fields provide online advice and assistance to the students. You are not sure what students would really find helpful though and think that you should talk more with high school students who identify as Aboriginal and Torres Strait Islander to find out what they would find helpful and if they would utilise a mobile app of this nature.

2.2 Milestones
When creating your work breakdown structure you consider the points in the projects where you could identify the projects progress. You list these milestones for the project as:
Milestone Name
M1. Initiation Gate: Charter approved The project charter must be approved before any marketing or requirements analysis begin.
M2. Functional requirements approved After the functional requirements are complete.
M3. Design Gate - ARG detailed design approval This gate is a go/no go decision point where the Architectural Reference Group have reviewed the detailed design for the prototype and approved that the detailed design in sufficient to proceed with the development of the prototype.
M4. Prototype Development Complete This milestone occurs after the completion of all three modules of the prototype have been developed.
M5. Release 1 Development complete This milestone occurs after the completion of the two modules of Release 1 have been developed.
M6. Go-live Gate – Go-live approved by Project Board The project board will approve the Go-live after the errors and bugs identified in the system and user acceptance testing of release 1 have been fixed.
M7. Completion Gate - Project final report approved by Project Board The project board will approve the Project Final Report has been written which includes lessons learnt, confirmation that procurements have closed and all other documentation has been archived in compliance with the organisations document management procedures.
M8. Post Project Review Report Approval Approval of the Post Project Review Report can only be done after the report has been written.
2.3 Initial Data
As the project manager you have described a number of tasks that will need to be completed to achieve the desired outcomes of the project. You use these tasks as a basis to create the project schedule and allocate resources.
You have noted down the following information:
1. A work break down structure (WBS), resource estimates and some dependencies summarised in Table 1 below.
Note that the following resource abbreviations are used:
• Project Manager (PM)
• Business Analyst (BA)
• Software Engineer (SE)
• Test Engineer (TE)
• Project Officer (PO)
• Marketing Officer (MO)
Table 1- Work Breakdown Structure
Task Name Duration Predecessor
The Auminthina Project
1. System Concept & Planning
1.1Concept paper 1 person day of PM
1.2 Project kick off meeting 1 person day of PM, BA, PO and SE 1.1
1.3 Stakeholder identification 1 person day of PM and BA 1.1
1.4 Risk identification 1 person day of PM, BA and SE 1.1,1.3
M1. Initiation Gate: Charter approved
2. Requirements analysis
2.1 Marketing and awareness campaign Stage 1 10 person days of MO M1
2.2 Focus group - ideation 5 person days of PM M1
2.3 Options analysis 10 person days of PM 2.2
2.4 Business requirements 20 person days of BA M1
2.5 Story board design 10 person days of BA 2.2
2.6 Functional requirements 10 person days of BA and SE 2.1, 2.3, 2.4, 2.5
M2. Functional requirements approved
3. Prototype Design
3.1 Prototype basic design 35 person days of SE M2
3.2 Technical Feasibility Assessment 5 person days of SE M2
3.4 Architectural Reference Group presentation 5 person days of PM 3.1,3.2
3.5 Prototype detailed design 10 person days of SE 3.1
M3. Design Gate - ARG detailed design approval
4. Prototype development
4.1 Module 1 10 person days SE M3
4.2 Module 2 10 person days SE M3
4.3 Module 3 10 person days SE M3
M4. Prototype Development Complete
5. Prototype Test
5.1 Test case development 5 person days of TE M4
5.2 Prototype system testing 5 person days of TE 5.1
5.3 Prototype User Acceptance Testing 10 person days of TE 5.1
5.4 Prototype system & user interface bug fix 6 person days of SE 5.2,5.3
5.5 Prototype Lessons Learnt 1 person day of BA, MO, PM, PO, SE and TE 5.4
6. Release 1 Design
6.1 Marketing and awareness campaign Stage 2 5 person days of MO 5.2,5.3
6.2 Detailed design 10 person days of TE and SE 5.5
7. Release 1 Development
7.1 Module 4 10 person days of SE 6.2
7.2 Module 5 10 person days of SE 6.2
M5. Release 1 Development complete
8. Release 1 Test
8.1 Release 1 Systems Testing 10 person days of TE 7.2
8.2 Release 1 User Acceptance Testing 7 person days of TE 7.2
8.3 Release 1 bug fix 5 person days of SE 8.1,8.2
M6. Golive Gate - Golive approved by Project Board
9. Launch
9.1 Marketing and awareness Campaign - Stage 3 10 person days of MO M6
9.2 Deployment and GoLive 1 person day of SE 45 – note Deployment and GoLive can occur on the last day of the Marketing and Awareness campaign Stage 3
10. Closure
10.1 Lessons Learnt 1 person day of BA, MO, PM, PO, SE, TE 9.2
10.2 Close procurement 5 person days of PM 9.2
10.3 Release project team 1 person day of PM 10.1
10.4 Finalise and archive project documentation 5 person days of PM and PO 10.1
M7. Completion Gate - Project final report approved by Project Board
11. Maintenance
11.1Maintenance period 10 person days of SE (fixed duration) 9.2
12. Post Project Review
12.1 Post Project Review Report 3 person days of PO 11.1, M7
M8. Post Project Review Report Approval
Notes:
1. One “person-day” is a “unit of work” representing the work done by one person in one day. It means that the task will normally take one person one day to complete. You can assume that a week refers to a normal working week of 5 days (Mon-Fri) with people working 8 hours per day. This is the default in Microsoft Project. Unless otherwise stated you can also assume a linear relationship, i.e. 3 person-weeks will take one person 3 weeks or 3 people one week. Note that this is not necessarily the case in practice. Refer to the discussion of the “mythical man-month” in your text book (Brooks’ law, chapter 9). In addition, some tasks will be a fixed duration (e.g. delivery times).
2. For the purposes of this assignment (to reduce variability in solutions and complications for the markers) build your Part A1 schedule by assuming that you allocate one resource (i.e. one person with the required skills) to each task. In that case, if the task required 3 person-weeks of an SE you would assign one SE to the task and give it a duration of 3 weeks.
Table 2 - Dates staff will not be available to work on the project
Work exception Dates
Queens Birthday 3 October 2016
Melbourne Cup Staff Bonding Day 1 November 2016
Christmas Day 25 December 2016
Boxing Day 26 December 2016
New Years Day 1 January 2017
Australia Day 26 January 2017
Dalmerdal Ltd Staff Forum 6 and 7 February 2017

Table 3 - Available Resources
Resource $/hour Number Available
Software Engineer $80.00 2
Business Analyst $65.00 1
Test Engineer $60.00 1
Project Officer $45.00 1
Project Manager $100.00 1
Marketing Officer $80.00 1
The software engineers work a 40 hour week from Monday to Friday (i.e. a 5 day week with 8 hour days). There are no differences between the abilities of the two software engineers).
You know that there are items that you may not have sufficient information about yet and that you may need to make some assumptions to complete your schedule and budget. Make sure that you list any assumptions you make at the beginning of your assignment submission.
2 Assessment Tasks
3.1 Part A: Developing the schedule
For part A of the assessment you must complete the following tasks and questions. Read all the questions before you commence the tasks. The schedule is to be developed in an appropriately named Microsoft Project 2013 file (see the name specified below) and the questions are to be answered in a Word document. As stated above, any assumptions must also be listed at the beginning of the Word document (after the coversheet).
1) Use Microsoft Project 2013 to develop the project schedule. Note that Ms Ellin Jannali has also asked you to include the following in your schedule:
a) The project title as the overall project summary (as task 0 and WBS number 0). All other tasks should be “indented” according to the WBS structure described in the case study.
b) The project name and start date be noted in the Project Information section in Microsoft Project.
c) The Microsoft Project workbook columns are set up as shown below:
(task number – no column title) Task
Mode Task Name Predecessors Duration Start Finish Resource Names
d) The task names are to include the WBS identifiers prior to the name in the ‘Task Name’ column (1.2 Project kick off meeting) and the milestones are to be placed throughout the schedule, with the milestone identifier included at the start of the milestone name in the ‘Task Name’ column (M1. Initiation Gate: Charter approved). All milestones are to be highlighted yellow.
e) Resource allocation details are included.
f) Holidays are entered.
g) The critical path(s) automatically displayed in red on the bars of the Gantt chart view of your schedule
At this point there may be resource over allocation issues. Do not attempt to resolve these before answering question 2. Save this version of your schedule as Auminthina_A1.mpp. You will be required to submit this file as part of your assignment submission.
2) At this point ignore any resource over allocations. For the purposes of this question only you can assume that there would be no resource constraints so do not attempt to resolve any resource over allocation (if any exists). Based on your Auminthina_A1.mpp schedule:
a) Use the “view tab” filter to display only the critical tasks. Provide a screenshot showing the task names and the Gantt chart of all the tasks on the critical path(s).
b) Did the annual holidays make any difference to the end date of your project? If so note the previous and changed end date. Explain why/why not there was/was not a change in end date.
c) If you were asked to complete the project 10 days earlier by reducing the duration of some of the tasks in the project. Fill in the table below stating what tasks you will reduce the duration of, by how much and how you will reduce the duration of each task.
Table 4 – Tasks with proposed duration reductions
Task WBS identifier and name Original task duration (prior to reducing) New task duration (after reducing) Suggestion of how to shorten the task
.

d) Create a new version of the schedule with the changes you outlined in part (c) highlighted blue using the “background colour” icon on the task ribbon. Make sure that your changes have reduced the project duration by 10 days. Call this file Auminthina_A2.mpp. You will be required to submit this file as part of your assignment submission. This file is not to be modified/developed further.
3) Create another copy of your original question 1, Auminthina_A1.mpp in another file called Auminthina A3.mpp. In this question, unlike question 2, assume that you will not have any additional resources assigned to the project even if there are resource over allocation issues. If your schedule had any resource over-allocation issues resolve these in the PartAQ3_resources.mpp file without adding any additional resources. For this assignment, do not “split tasks”. Save this “modified” version of Auminthina_A3.mpp file. You will be required to submit the Auminthina_A3.mpp file as part of your assignment submission.
a) Describe how you used (or how you would have used Microsoft Project) to resolve any resource over-allocation issues.
b) Does the fact that you cannot have any additional resources for this project have any impact on your project duration and end date? Explain.
c)
4) Continue working with Auminthina_A3.mpp. In this file, include two additional milestone “markers” to show the following notifications:
a) The Architectural Reference Group needs notification and papers to be sent out five business days prior to being able to approve the detailed design (M3). Continue working with Auminthina_A3.mpp. In this file, include an additional milestone “marker” called ‘N1 ARG Design Gate Notification’ to highlight the latest date that the project manager should contact the Architectural Reference Group to provide notification and papers. The papers will consider of the Prototype detailed design documents that are created in task 3.5 Prototype detailed design.
i) According to Auminthina_A3.mpp what is the latest date that notification and papers can be sent to the Architectural Reference Group?
ii) Is there an issue between the dates for notification and finalising the Prototype Detailed Design (3.5).
b) The Project Board needs notification and papers to be sent out ten business days prior to being able to approve GoLive (M6). Continue working with Auminthina_A3.mpp. In this file, include an additional milestone “marker” named ‘N2 Project Board GoLive Gate Notification’ to highlight the latest date that the project manager should contact the Project Board to provide notification and papers.
i) According to Auminthina_A3.mpp what is the latest date that notification and papers can be sent to the Project Board?
Make sure that these new milestones have the appropriate predecessor relationships so that the dates will be automatically adjusted if there is any change to the schedule. On your schedule, highlight the rows that include these milestones in blue. This change is to be saved in your Auminthina_A3.mpp file.
5) Write a memo to the CEO, Ms Ellin Jannali, providing your project proposal and include following information:
a) an explanation of the project need and what it is trying to achieve.
b) the expected completion date of the project, assuming it commences on 1/10/16;
c) the total duration of the project;
d) an explanation of the main factors that cause the project to require that length of time and any recommendations that you might make if time was a priority for the project;
e) the estimated labour costs for each of the resource types working on the project. Present the costs in a table similar to the following:
Table 5 – Labour Costs
Resource Name Cost ($)
Business Analyst
Software Engineer
Test Engineer
Project Manager
Marketing Manager
Project Officer
Total labour costs:
Assume that you will send the project schedule (Auminthina_A3.mpp) as an attachment to the memo. The information in the memo should correspond to the attached schedule. Some notes regarding memos can be found on the course website in the same area as this specification.
3.2 Part B: Modifying the schedule
Ms Ellin Jannali reviews your project proposal including the attached schedule and advices you you’re your project has been chosen however requires some changes.
• She states only one Software Engineer will be available for the project.
• The task ‘3.1 Prototype basic design’ needs to be reduced to 30 days.
• The task ‘10.2 Close procurement’ needs to be reduced to 1 day.
Based on the information given above complete the following tasks:
1. Copy your AuminthinaA3.mpp file into a file called Auminthina_B.mpp file. Amend the project schedule in your new Auminthina_B.mpp file incorporating the change requests from Ms Ellin Jannali. If this has created any resource over allocation issues resolve these before progressing to the next question. Save the changes. The Auminthina_B.mpp file is also to be included as part of your final assignment submission.
Have the changes impacted on the duration or costs of your project and if so in what way? Be very precise in your answering of questions 2 and 3 below. If the project is longer or shorter state the previous finish date the new end date and by how much the project has been shortened or lengthened. If the changes had an impact on the cost, mention what the previous cost was and what the cost was after the change and explain why there was or was not an impact.
2. Describe the impact of each of these changes on the project duration in a table similar to the following:
Table 6 – Impacts of Changes to Project Duration
Change Impact on project duration
(longer, shorter or no impact) By how much Explanation
Reduction to one Software Engineer
Change to the duration of ‘3.1 Prototype basic design’
Change to the duration of ‘10.2 Close procurement’
Note that if a combination of the changes have had an additional impact that would not have occurred if the change was made in isolation clarify this in your explanation.
3. Describe the impact of each of these changes on the labour costs for the project in a table similar to the following:
Table 6 – Impacts of Changes to Labour Costs
Change Impact on labour costs
(more, less or no impact) By how much Explanation
Reduction to one Software Engineer
Change to the duration of ‘3.1 Prototype basic design’
Change to the duration of ‘10.2 Close procurement’
3.3 Part C: Tracking Progress
In this part of the assignment you are to imagine that your project is underway and that it is time to produce one of a project performance report.
1. Copy Auminthina_B.mpp to Auminthina_C.mpp. Save the baseline for this version of your project.
2. You are back at work after the Christmas and New Years holidays. You are writing the project performance report for the period from the start of the project to the end of December 2016. You review the information provided to you by your project staff on the progress of the project and need to update your schedule accordingly. In your Auminthina_C.mpp file
a. Set the current date to 3 January 2017, the status date to 31 December 2016 and include a solid, purple status date gridline in your project to ensure the status date is clearly visible in your Gantt Charts.
3. Most of the tasks up to the 31 December 2017, were completed as per the schedule. However the following data represents information on tasks where the performance was different to what was planned.
Table 7 – Actuals differing from planned estimates (as at 31 December 2016)
Task WBS identifier and name Actual start date Actual Duration to date % Complete Notes
1.1 Concept paper 4 October 2016 10 person days 100% Completed five days earlier than planned.
1.4 Risk identification 25 October 2016 2 person days 100% This was completed during the project kickoff meeting and the stakeholder identification workshop. As all staff were present, the resources cost for this task is duplicated. Remove the resources for this task.
2.5 Story Board 17 November 2016 10 days 100% This was able to be done by the Business Analyst during the collection of business requirements. Therefore labour costs for this task are not needed. Remove the resources for this task.
2.6 Functional Requirements 1 December 2016 10 days 100% The functional requirements were endorsed the following day. Thereby meeting M2 on the 15 December 2016.
3.1 Prototype Basic Design 19 December 2016 5 days ?? You are not sure of the %Complete for this task. However the Software Engineer went on leave from Saturday 24 December and has started working on the prototype basic design today (3 January 2017). She states that as at the 31 December 2016 (the status date for the report) there were 25 days of work left on the task.
a. Update your schedule with the information from the Include a screenshot of the top of your tracking Gantt chart showing the tracking table and the Tracking Gantt Chart for some of your tasks. For example, if asked to do this for the Microsoft Project practical 4 schedule, you would have included a screenshot similar to the following:

b. Include a screenshot of the top of the earned value table for your Auminthina_C.mpp file. You will probably have to add the additional CPI and SPI columns. For example, if asked to do this for the Microsoft Project practical 4 schedule, you would have included a screenshot similar to the following:

c. Based on the current status of your project, you are to produce a status report with a similar format to “exhibit 13.1” in the textbook (the actual template you are to use for the status report is provided as Appendix 1). Detailed explanations for why tasks are not tracking according to their original estimates are not required for this assignment as the data you entered is “fictitious”. However, you can suggest reasons for tasks to be tracking better or worse to make your report more realistic if you wish. Even if you do not give specific reasons, you must still flag which tasks are responsible for your project status being better or worse than planned.
4. From past projects you have worked on one of the lessons learnt was that not enough emphasis was placed on closure activities. To avoid this during this project you have included closure activities within the schedule.
You have included the following tasks in the project closure
i. 10.1 Lessons Learnt,
ii. 10.2 Close Procurement
iii. 10.3 Release Project Team
iv. 10.4 Finalise and archive project documentation
Considering the activities that should be carried out in the closure stage of a project are there any activities that you have failed to include in the schedule? If so what are they? In your answer explain the purpose of any missing closure activities
5. It is a week out from when you will be released from the project. You have been offered a role as the Scrum Master of a project that will be run using agile project management methodology.
Your project officer has been asked to work with you on the agile project as well. They have never worked on an agile project and ask you what the main differences between agile and traditional project methodologies are. To help the project officer understand the differences between the methodologies and which types of projects are suited to each you fill out the following table:
Table 8 – Traditional vs Agile Project Management
Attribute Traditional Project Management Methodology Agile Project Management Methodology
When does the design usually occur? Upfront / Continuous?
Is the scope fixed or flexible?
Should change be avoided or embraced?
Which project methodology has the higher / lower customer interaction?
Which project teams are conventional and which are self-organised?
Which methodology deals better with projects where the requirements are certain / uncertain?
3.4 Assumptions
You are free to make any assumptions necessary to complete the assignment. However each assumption must be justified and stated clearly in your assessment word document. Marks will be deducted for any unreasonable assumption or for stating an assumption and then ignoring it in your assignment.
4 Assessment Submissions
This assignment requires 5 individual submissions of the sub-deliverables online by all members of the group and one final group submission of the complete assignment by one member of the group only plus three peer group assessments. The individual sub-deliverables are to be submitted in weeks 6, 7, 8, 9 and 10. The final group submission is due in week 11. The exact due dates and times are given on the Moodle course website. The details of what is to be submitted for each sub-deliverable and for the final group submission are given below.
4.1 Individual submission of sub-deliverables
These are to be submitted by all members of the group as zip files in their own submission area on the Moodle course website. Each individual submission has a different due date. The table below provides a summary of what is to be submitted in the zip files.
Sub-deliverable Week due Description of zip file contents
1 6 A zip file containing:
1. .mpp files for MS practical 1
2. .mpp files for MS practical 2
3. .mpp files for MS practical 3
4. .mpp files for MS practical 4
2 7 A zip file containing:
1. Auminthina_A1.mpp
2. Your completed peer assessment form(s)
3 8 A zip file containing:
1. Word document with answers for Part A
2. Auminthina_A2.mpp
3. Auminthina_A3.mpp
4. Your completed peer assessment form(s)
4 9 A zip file containing
1. A Word document with the answers to Part B
2. Auminthina_B.mpp
5 10 A zip file containing:
1. A Word document with answers for Part C
2. Auminthina_C.mpp
4.2 Peer Assessment
The aims of this peer assessment are twofold:
1. to provide information to the markers to help with their assessment of student work
2. to give students feedback to help students to improve their skills when working as part of a team.
In terms of point 2, it is important that the feedback be used in a positive way. It should only include “constructive criticism”, i.e. it should:
1. Provide positive feedback so that the team member understands what they are doing that works well.
2. Provide constructive criticism, i.e. advice about how a team member could improve their team work.
3. Be polite and positive.
In terms of point 1, although there are three peer assessments scheduled as part of this assessment item (one in week 7, one in week 8 and one with the final submission in week 11). It is also important that you alert your tutor as early as possible if you are experiencing problems within your group (for example, if a team member is not attending meetings or is coming to meetings unprepared).
The first peer assessment is to be submitted with your individual sub-deliverable in week 7. Similarly the second peer assessment is to be submitted with your individual sub-deliverable in week 8.You will be advised later in the term about how/where to submit your final week 11 peer assessment.
The Peer Assessment Forms to be completed and submitted in weeks 7 and 8 are available on the course website in the same area as this assignment specification.
4.3 Final Group Submission
The final group solution with the mpp files and assignment answers must be submitted in the electronic submission system on Moodle by one member of the group. It is important that only one member of the group submits the work or Turnitin will produce a very high similarity score for your work.
The final group submission is due at the end of week 11 (exact date and time shown in Moodle). Unlike the individual sub-deliverable submissions, this submission area will not accept zip files. The final group submission is to consist of six individual files as follows:
1. A Word document with the coversheet/title page (shown below) and the group answers to all the questions in Part A, Part B and Part C.
2. The following group .mpp files:
a. Auminthina_A1.mpp
b. Auminthina_A2.mpp
c. Auminthina_A3.mpp
d. Auminthina_B.mpp
e. Auminthina_C.mpp
Content of the Word Document in the final submission
To avoid problems with Turnitin, do not copy the questions from this assignment specification into your Word document.
However, do make it as easy as possible for your marker to identify the question you are answering by labelling each question clearly. For example:
Part A
Question 1
Your answer
Question 2
Your answer
The Word document (with your group answers to the questions) must also include a coversheet/title page at the start of the document that clearly shows all members of the group. A template for the coversheet/title page follows.
PPMP20007 / MGMT22166
Assessment Item 2 Coversheet
Tutor:
Group Members:
Student Name: Student Id:
Student Name: Student Id:
Student Name: Student Id:
Student Name: Student Id:
Remember that it is your responsibility to keep backups of your work and of your current version of the final group assignment.
Although there is to be only one submission of the final group assignment by one member of a group, it is the responsibility of all members of the group to make sure that the correct files are submitted by the due date.

5 Marking Guide – Group Final Submission
Assignment Question Criteria Marks available Marks awarded
Individual Sub-deliverables Marked separately on Moodle
Part A
Assumptions Listed, justified and stated clearly at the start of the Word document (if any )
Q1 The adequacy of the Project Schedule 7
Q2 a) CPs; b) impact of hols; c) & d) shorten project 3
Q3 Dealing with resource issues 2
Q4 Dates for bookings 2
Q5 Appropriateness of the written memo with all the information included and corresponding to the schedule. 3
Sub Total Part A 17
Part B
Q1 The adequacy of the amended Project Plan 1
Q2 End date and duration – any difference and if so what is it? 1
Q3 Description of impacts of each of the changes on duration 2
Q4 Description of impacts of each of the changes on cost 2
Sub Total Part B 6
Part C
Q1 Save baseline 0.5
Q2 a) Status date set + gridline
b) Screenshot of Tracking Gantt with updated status information
c) Screenshot of earned value table + CPI & SPI 2.5
d) Completed status report 4
Q3 Project Closure 2
Q4 Traditional vs Agile 3
Sub Total Part C 12
TOTAL 35
Notes:
1. This assessment item 2 also includes 5 individual sub-deliverables and peer assessment. The marks for the 5 sub-deliverables are recorded separately in Moodle.
2. All marks for this assessment item depend on students making satisfactory contribution to the group. If students are not contributing to they may be asked to work on the assignment as an individual and/or have marks adjusted. Both peer assessment and individual submissions will be taken into account.
3. Sub-deliverables must be submitted on time to be awarded marks and both peer assessments must be completed.

Appendix 1: Status Report Template
This is the status report template that is to be used for Part C, question 2 part (e).
The information to be entered in the status report is shown in italics.
Project Name: enter project name Status Report #
Project Manager: enter the name of the project manager (for this assessment item, enter the names of all members of the group
Status as of: enter status date End of Week: #
Earned Value Figures
PV EV AC SV SPI CV CPI BAC EAC VAC

Enter the earned value figures in the table above. The data in this table must correspond to the data in your Auminthina_C.mpp file
Project Description
A brief description of what this project is about.
Milestone Status
Milestone Description Date scheduled
(baseline) Date
Reached
M1
M2
M3
M4
M5
M6
M7
M8
N1
N2
For each milestone, enter the milestone description and week scheduled for completion according to your baseline. If a milestone has been reached enter that information in the last column.
Status summary (schedule and budget)
Schedule
Planned finish date: enter date
Current estimated finish date: enter date
Summary:
Based on the finish dates, explain whether the project is currently ahead or behind and by how much.
Based on the schedule variance (SV) explain in dollar terms whether more or less work has been completed compared to what was planned and by how much.
Budget
The actual cost to date: enter the actual cost to date here
The planned cost to date: enter the planned cost to date here
Summary:
Explain whether the project is currently over or under budget and by how much
Based on the current data (and assuming the project continues at the same rate of efficiency), report the estimated cost at completion. Explain whether this means the project is expected to be over or under budget and by how much.
Explanations
Explanation of current status. Identify the tasks responsible for the results and explain the reasons. For this assignment you must at least highlight which tasks are not tracking according to their original estimates and explain whether they are performing better or worse and by how much.
Major changes or issues since last report
Describe any major changes or issues since the last report
Risk watch:
Review the risk plan and project risks. Document any changes here