Optimizing Project Resources: A Case Study of GreatToys SmartBear

This document provides a solution to a project management case study, "GreatToys SmartBear," focusing on optimizing project duration and resource allocation. It includes an analysis of project timelines, cost estimations, and the impact of resource changes. The solution covers aspects such as adjusting project duration by adding resources, resolving resource overallocation, and evaluating the earned value. The document also provides a status report, highlighting schedule and budget variances, along with explanations for task durations and cost impacts. The report further discusses potential risks and offers suggestions for reducing project duration, making it a comprehensive guide for understanding project management principles and practices.

☐ I/we understand and agree to the following:
1

Part A Question 3
a) Duration: 180 days End Date: 11-02-19
b) Duration after change: 150 days End Date after change: 27/12/18
c) It is identified that due to allocating one more software engineer there has been change in the
duration of the entire project. It is found that earlier the expected date of the project is 180 days
however after adding one more software engineer within the activity “software development, the
duration of the project changes to 150 days. This change is because the task is required to be
performed within the activity “Software development” is divided between the two software engineers
and as a result the entire duration of the project reduces.
d) The adding of resources always helps in reducing the duration of the task. It is identified that it not
only depends on the task nature however it is necessary that the duration will get reduced as the
workload get divided.
Part A Question 4
a) It is identified that that in order to resolve the problem of resource overallocation following
steps are generally followed:
i) Firstly, we click on the levelling option and after then resource levelling options
opened.
ii) Secondly, we uncheck split task option and adjust individual assignment on a task
which is reflected from the provided screenshot
iii) The problem of resource overallocation will get resolved.
2

b) The problem of resource allocation can be resolved by levelling the resources. This option is
considered advantageous as it generally does not enhance the entire budget of the project.
c) The comparison is provided below in the table:
PartAQ3.mp PartAQ4.mpp
150 days 210 days
It is identified that earlier the time that is needed for completing the project was around 150
days however after levelling the resources of the project in order to avoid resource overallocation, the
duration of the project increases to 210 days.
Part A Question 5
Memo
To: Mr. Nielson
From: << Student name >>, Project Manager
Date: 21/5/18
Sub: Suggestions for reducing the project duration by 2 weeks
Message
The project “GreatToys SmartBear” will be completed by 25-03-19 as it is assumed to be
commenced on 04-06-2018. It is identified that in order to reduce the duration of the project by 2
weeks, one need to involve more software engineers as well as mechanical engineer within the
project. By adding the resources within the project, the entire duration of the project can be easily
reduced. This is because by adding resources, the work load generally gets divided between the
new resources of the project and as a result the duration of the project gets reduces. The estimated
direct labour costs for each of the resource types are generally provided below in the table:
Resource Name Costs
Electronic engineer $ 90.00/hr
Software engineer_1 $ 80.00/hr
Mechanical engineer $ 70.00/hr
Test engineer $ 95.00/hr
Production engineer $ 100.00/hr
Software engineer_2 $ 80.00/hr
The mpp for part 4 is attached below
3

Impact of changes on overall project duration:
Change Impact
(longer, shorter
or no impact)
By how much Explanation
Change in person-weeks for
task 2.7
Before: 6wks
After:14wks
Impact: Longer
8 weeks It is identified that the duration of the activity
changes by 8 weeks due to increasing the duration
for completing the activity.
Change in person-weeks for
task 2.12
Before:2wks
After:3wks
Impact: Longer
1 week
The duration of the activity changes by 1 week
due to increasing the duration for completing the
activity.
Change in duration for 5.2 Before:4 week
After:2 week
Impact: Longer
2 weeks
The duration of the activity changes by 2 weeks
due to increasing the duration for completing the
activity.
Assignment of both MEs to
task 3.3
Before:2 weeks
After:1 week
Impact: Shorter
1 week
The duration of the activity changes by adding
one more mechanical engineer. This is because
workload get divided between two resources and
as result the time reduces.
Impact of changes on overall project cost
Change Impact on
direct labour
costs
(more, less or
no impact)
By how much Explanation
4

Change in person-weeks for
task 2.7
Before:
$38400
After: $89,600
Impact: More
$51,200
The cost of the activities enhances due to
increment in the duration of the activity.
Change in person-weeks for
task 2.12
Before: $6400
After: $9600
Impact: More
$3200 The cost of the activities enhances due to
increment in the duration of the activity.
Change in duration for 5.2 Before:0.0
After:0.0
Impact: No
impact
$0.0
As the activity does not include any resources
therefore change in duration does not create any
change on the project cost.
Assignment of both MEs to
task 3.3
Before: $5600
After: $2800
Impact: Less
$2800 The project cost reduces due to reduction in time
of the project by adding one more resources.
5

Project Name: GreatToys SmartBear Status Report <report # >
Project Manager: <please fill>
Status as of: 24th Aug 2018 End of Week: <week #>
Earned Value Figures
Planned Value
- PV (BCWS)
Earned
Value -
EV
(BCWP)
AC
(ACWP) SV CV EAC BAC VAC
$ 98,640.00 $
94,321.18
$
81,800.00
-$
4,318.82
$
12,521.18 $ 244,321.63 $
281,720.00 $ 37,398.37
Project Description
Great Toys is one of the medium sized company that generally aims to develop SmartBear
electronic toys.
Milestone Status
Milestone Description Date
schedule
d
(baseline)
Date
Reached
M1 M1 concept review 4-6-18 4-6-18
M2 M2 design review 13-11-18
P1 P1proto build start 16-01-19
M3 M3 final design review 01-04-19
M4 M4 launch review 29-05-18 29-05-18
6

Status summary (schedule and budget)
Schedule
Planned finish date (from Gantt chart): 01-04-19
Current estimated finish date (from tracking Gantt chart): 20/5/19
The planned cost to date: $98,640
The earned value to date: 9,.321. 18
The actual cost to date: $ 81,800.00
Schedule Variance: -$ 4,318.82
Summary of schedule status:
1. As per the finish dates, it is identified that the project is ahead of the current estimated finish
date by 49 days.
2. It is identified that less work has been completed as per the schedule variance of the project
Budget
The actual cost to date: $281,720
The earned value to date: $265,280
Cost Variance: $ 12,521.18
CPI: 1.15
Summary of budget status:
1. The project is over budget as the cost of the project enhances which is generally reflected from
the difference between actual cost and earned value.
2. The project is expected to be over budget by $ 12,521.18
Explanations
WBS Task Name Duration Start Finish % Complete
0 GreatToys SmartBear 50 wks. Tue 29-
05-18
Mon 20-
05-19 32%
1 Electronics 41.2 wks. Mon 04-
06-18
Mon 25-
03-19 78%
1.1 PWB outline 2 wks. Mon 04-
06-18
Fri 15-06-
18 100%
1.2 Component selection 3 wks. Mon 18-
06-18
Fri 06-07-
18 100%
1.3 Circuit design 2 wks. Mon 09-
07-18
Fri 20-07-
18 100%
1.4 Electronic verification test 1 wk. Tue 12-
03-19
Mon 18-
03-19 0%
1.5 Thermal verification tests 3 days Tue 19-
03-19
Thu 21-03-
19 0%
1.6 EMS Verification tests 2 days Fri 22-03-
19
Mon 25-
03-19 0%
2 Software 39.6 wks. Tue 29-
05-18
Thu 07-
03-19 26%
2.1 Detailed software analysis 2.8 wks. Tue 29-
05-18
Fri 15-06-
18 100%
7

2.2 User interface specification 2 wks. Tue 10-
07-18
Mon 23-
07-18 0%
2.3 Database analysis 2 wks. Wed 07-
11-18
Tue 20-11-
18 0%
2.4 Software design 3 wks. Tue 19-
06-18
Mon 09-
07-18 100%
2.5 User interface design 2 wks. Wed 21-
11-18
Tue 04-12-
18 0%
2.6 Database design 3 wks. Wed 05-
12-18
Thu 27-12-
18 0%
2.7 Software development 14 wks. Tue 31-
07-18
Tue 06-11-
18 26%
2.8 User-interface development 2 wks. Fri 28-12-
18
Fri 11-01-
19 0%
2.9 Database development 1 wk. Mon 14-
01-19
Fri 18-01-
19 0%
2.10 R1 release creation 3 days Mon 21-
01-19
Wed 23-
01-19 0%
2.11 R1 release tests 2 wks. Thu 24-
01-19
Thu 07-02-
19 0%
2.12 R1 error correction and
interface improvements 2 wks. Fri 22-02-
19
Thu 07-03-
19 0%
3 Mechanics 5 wks. Tue 29-
05-18
Mon 02-
07-18 95%
3.1 Industrial design 1.2 wks. Tue 29-
05-18
Tue 05-06-
18 83%
3.2 PWB outline modifications'P1
mechanical CAD design 1 wk. Tue 12-
06-18
Mon 18-
06-18 100%
3.3 P1 mechanical CAD design 1 wk. Tue 19-
06-18
Mon 25-
06-18 100%
3.4 Tolerance stack analysis 1 wk. Tue 26-
06-18
Mon 02-
07-18 100%
4 Verification 50 wks. Tue 29-
05-18
Mon 20-
05-19 8%
4.1 Test plan creation 1.8 wks. Tue 29-
05-18
Fri 08-06-
18 56%
4.2 Component tests 1 wk. Mon 14-
01-19
Fri 18-01-
19 0%
4.3 Module tests 2 wks. Tue 12-
03-19
Mon 25-
03-19 0%
4.4 System integration tests 2 wks. Tue 26-
03-19
Mon 08-
04-19 0%
4.5 Product validation tests 1 wk. Tue 09-
04-19
Mon 15-
04-19 0%
4.6 Technical construction file
compilation 1 wk. Tue 16-
04-19
Mon 22-
04-19 0%
4.7 Regulatory approval tests 4 wks. Tue 23-
04-19
Mon 20-
05-19 0%
5 Production 10 wks. Fri 28-
12-18
Mon 11-
03-19 0%
5.1 P1 component lead time 2 wks. Fri 28-12- Fri 11-01- 0%
8

18 19
5.2 P1 PWB manufacture and
delivery 2 wks. Fri 28-12-
18
Fri 11-01-
19 0%
5.3 P1 mechanical part lead time 2 wks. Fri 28-12-
18
Fri 11-01-
19 0%
5.4 P1 assembly and production
test preparation 3 wks. Fri 28-12-
18
Fri 18-01-
19 0%
5.5 P1 prototype build 2 days Fri 08-03-
19
Mon 11-
03-19 0%
6 Production of 1000 devices 2 wks. Tue 29-
05-18
Mon 11-
06-18 100%
M1 M1 concept review 0 days Tue 29-
05-18
Tue 29-05-
18 100%
M2 M2 design review 0 days Thu 27-
12-18
Thu 27-12-
18 0%
P1 P1proto build start 0 days Thu 07-
03-19
Thu 07-03-
19 0%
M3 M3 final design review 0 days Mon 20-
05-19
Mon 20-
05-19 0%
M4 M4 launch review 0 days Tue 29-
05-18
Tue 29-05-
18 100%
Major changes or issues since last report
No changes or issues are identified since the last report.
Risk watch: No change
9