You are on page 1of 9

ENGG 951 Assignment 1 Technical Report

Project Objective:

Design a building according to the requirements of the client using the available resources and within the project deadline.

Project Preliminary Schedule:

ID

Task name

Duration(days)

Precedence

Resources

1

Start

0

   

2

Initial Planning

  • 10 1

 

Principal Architect

3

Sketching Mock-ups

  • 20 1

 

Principal Architect & Draft person

4

Prepare Documentation

  • 30 2

 

Principal Architect

5

Prepare Detail Drawings

  • 20 3

 

2 X Draft person

6

Check Project Scope & Costs

  • 20 5

 

Principal Architect

7

Plan Building Schedule

  • 30 6

 

Principal Architect & Draft person

8

End

0

 

4,7

 
 

Table 1 Preliminary Project Schedule

 

Available Resources and Costs:

 
 

Resource

 

Availability

 

Rate/day

 
 

Principal

 

1

 

$1500.00

 

Draft person

 

2

 

$900.00

Table 2 Resources and associated costs

Project Environment:

  • 1. Start Date: 13/02/1989

  • 2. No. of working hours/week: 40 Hours

  • 3. No. of working days/week: 5 Days

  • 4. Beginning of Day: 9:00 AM

Project Title: ENGG951

Project Client: Peter Gibson

Date:

20/0/2012

Project Manager: Aneesh Kolla

Student No.: 4231120

Page: 1 of 9

Project Tasks:

The tasks of the project are divided into two phases.

  • 1. Preliminary Design tasks

    • a. Initial Planning

    • b. Sketching Mock-ups

    • c. Prepare Documentation

  • 2. Final Design Tasks

    • a. Prepare Detail Drawings

    • b. Check Project Scope & Costs

    • c. Plan Building Schedule

  • Project Execution:

    The execution of the project is done in the following order.

    • A new project file is started with the required environment.

    • A start date and a schedule is then assigned to the project file.

    • The resources (with associated costs) are commissioned to the project.

    A Gantt

    chart

    is

    then

    presented below.

    produced for the

    project. The generated Gantt Chart is

    Project Title: ENGG951 Project Manager: Aneesh Kolla Project Client: Peter Gibson Student No.: 4231120 Date: 20/0/2012
    Project Title: ENGG951
    Project Manager: Aneesh Kolla
    Project Client: Peter Gibson
    Student No.: 4231120
    Date:
    20/0/2012
    Page: 2 of 9

    Fig. 1 Gantt Chart

    Issues with the original project plan:

    Resource Histograms for both the resources Principal Architect and Draftsperson are produced and is shown below. Fig. 2 shows the graph of the Principal Architect and the Fig. 3 shows the graph of the Draftsperson.

    Fig. 1 Gantt Chart Issues with the original project plan: Resource Histograms for both the resources

    Fig. 2 Histogram showing overallocation of Principal Architect

    Project Title: ENGG951 Project Manager: Aneesh Kolla Project Client: Peter Gibson Student No.: 4231120 Date: 20/0/2012
    Project Title: ENGG951
    Project Manager: Aneesh Kolla
    Project Client: Peter Gibson
    Student No.: 4231120
    Date:
    20/0/2012
    Page: 3 of 9

    Fig. 3 Histogram showing allocation of Draftsperson

    From the above obtained Resource Histograms we can observe that Principal Architect has been over-allocated, which is indicated by the red bars. So, in order to level the allocations, the re-allocation of the resource has to be done using the levelling options in MS Project. The following are the levelling options obtained and

    it’s shown below.

    Fig. 3 Histogram showing allocation of Draftsperson From the above obtained Resource Histograms we can observe

    Fig. 4 Levelling Options

    The levelling options observed are as follows:

    • Level only within available slack

    • Levelling can adjust individual assignments on a task

    • Levelling can create splits in remaining work

    • Level resources with the proposed booking type

    • Level manually scheduled tasks

    So, the levelling options are selected in such a way that the levelling is done manually and the entire project is levelled instead of a certain period of time. Then with the rest of the five options, only the first option is selected and the rest are not selected. Then the process is continued by selecting one single option and not selecting all the other options. So the following results are obtained by applying the above procedure.

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 4 of 9

    Levelling option 1: “Level only within available slack”

    When this levelling option is applied we can observe that the over-allocation still persists but not in the same tasks but in other tasks, Documentation and Integration testing instead of in Screen design, Interface design and Documentation. We can observe a change in the Gantt chart which means that the order in which the works are done is changing by applying this levelling option. The task sheet after applying this option is given below.

    Levelling option 1: “Level only within available slack” When this levelling option is applied we can

    Fig. 5 Levelling option 1

    Levelling Option 2: “Levelling can adjust individual assignments on task”

    When this levelling option is applied we can observe there are no over allocations observed. But we can observe that the number of working days have increased when compared to the number days that were allocated in the beginning of the project. The task sheet after applying this option is given below.

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 5 of 9

    Fig. 6 Levelling option 2 Levelling Option3: “Levelling can create splits in remaining work” When this

    Fig. 6 Levelling option 2

    Levelling Option3: “Levelling can create splits in remaining work”

    When this levelling option is applied we can observe that the over allocation still persists in the project during the tasks, screen design and interface design. We can observe that the tasks will split up according to the availability of the resource. Even the number of days allocated will change. The task sheet for this option is given below.

    Fig. 6 Levelling option 2 Levelling Option3: “Levelling can create splits in remaining work” When this

    Fig. 7 Levelling option 3

    Levelling Option4: “Level resources with the proposed booking type”

    When this levelling option is applied we can observe that there is no over allocation of resources. But, the number of days allocated for the tasks are increasing and the tasks are splitting up. The task sheet for this option is given below.

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 6 of 9

    Fig. 8 Levelling option 4 Levelling Option5: “Level manually scheduled tasks” With this levelling option we

    Fig. 8 Levelling option 4

    Levelling Option5: “Level manually scheduled tasks”

    With this levelling option we can manually resolve the over allocations by either increasing the number of days that were actually allocated or by increasing the number of resources that were actually available. So by increasing the number of Analyst available from 1 to 2 we can resolve the over allocation. The task sheet obtained is shown below.

    Fig. 8 Levelling option 4 Levelling Option5: “Level manually scheduled tasks” With this levelling option we

    Fig. 9 Levelling option 5

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 7 of 9

    Final Solution:

    When the project statistics are observed we can conclude with the following results:

    • Final Planned Cost: $246,000.00

    • Duration of the Project: 90 Days

    Final Solution: When the project statistics are observed we can conclude with the following results: 

    Project Statistics:

    Final Solution: When the project statistics are observed we can conclude with the following results: 

    Assumptions:

    While resolving the issues that have been encountered while executing this project, we have made some assumptions in order to overcome the issues. Some of them are given below:

    • It is assumed that we can increase the available resources, particularly the Principal Architect. We have increased the maximum resources to 2 in order to decrease the project duration to 90 days.

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 8 of 9

    • We have assumed that in the project completion time is a priority. So, we have tried to decrease the number of days rather than try to decrease the cost of the project.

    • We have even assumed that splitting of the tasks is not practical. So, we did not use the levelling option which splits the given tasks.

    Project Title: ENGG951

    Project Client: Peter Gibson

    Date:

    20/0/2012

    Project Manager: Aneesh Kolla

    Student No.: 4231120

    Page: 9 of 9