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...

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. Any assumptions must also be listed at the beginning of the Word document (after the coversheet).
1. Use Microsoft Project to develop the project schedule according to the instructions below.
For this assignment, unless the specification states otherwise, you must initially allocate only one of each required resource to a task. To clarify, some examples are given below. For example, based on the information in table 2, you should initially allocate:
• One Analyst to work on task “5.1 Detailed Requirements Analysis” for 12 weeks.
• One Operations staff member and one Software Engineer to work together on task “4.6 Installation” for 1 week.
• All three of the installation team to work together on each of the installation tasks (6.1-6.3). With this “team”, each task should have a duration of 2 days.
• Two members of the installation team to work together on each of the training tasks (7.1-7.3). With this “team”, each training task should have a duration of 3 weeks.
All tasks must be automatically scheduled tasks for this assignment. Remember to make this the default setting before you begin adding tasks to your schedule.
You are required to report directly to the owner, Chris Parsons. Chris has asked that the following be included in the schedule:
a) The following holiday/non-working times:
b) A project title of “Family Friendly Financial Control System”. This is also to appear as the overall project summary at the top of your “WBS” in the mpp file. It must appear as task 0 with WBS number 0. All tasks should be “indented” according to the WBS structure described in the case study (see table 2). See the Microsoft Project practicals for details about how to add the project title and how to make it the overall project summary.
c) A WBS column before the “Task Name” column and a WBS Predecessors column after the “Task Name” column as shown below:
d) The milestones are to appear at the end of the task list in your schedule. See the notes after table 2 for more details about the project milestones. (Note that this is not
Page 8
always a requirement in a project schedule. Milestones can be embedded in the schedule or listed at the start. In this assignment you are required to add them at the end).
e) Chris Parsons has also asked you to use a “customised WBS code” for the milestones. For example, if you double click on the first milestone, you can change the WBS code to M1 as illustrated in the screenshot below.
f) Resource allocation details.
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 in PartAQ1.mpp. You will be required to submit this file as part of your assignment submission.
2. At this point ignore any resource over allocations. Copy your PartAQ1.mpp schedule to PartAQ2.mpp.
Chris Parsons asks you to allocate all three analysts to task “1.1 Analysis of original system functionality”. Assume that with the additional resources the task still requires “6 person-weeks” (i.e. that there will be a reduction in duration as the work can be divided equally among the three resources).
a) What is the new duration of task 1.1 and has this change impacted on the overall duration of the project? Explain.
b) What is the additional cost in adding these extra resources to the project? Explain.
Save PartAQ2.mpp. You will be required to submit this file as part of your assignment submission.