Assessment item 2Individual case study

Due date: 1:00pm AEST, Thursday, Week 11 All students are to submit electronically max file size is 2Mb. Weighting: Length: 35% No set length
ASSESSMENT

Introduction and Student Guide

This assessment item is to be completed individually. The case study simulates a project management scenario where the student takes on the role of project manager. The case information is not complete so where necessary students will have to make assumptions and argue the pros and cons for any recommendations they make. If necessary, students are expected to find relevant information in the academic literature to justify their answers. To assist students in their assessment solution development the following information is provided: Product development case description Specific assessment questions that must be answered Information regarding the submission of the assessment Marking guide

Product Development Case Description

Background
Xyzzy is a medium sized company that develops and manufactures mobile data collection devices. You are an employee of Xyzzy and work as project manager in the product development department. The people involved in this case are: You are Ms. Andersen, the project manager. Mr. OBrian is the Director of Product Development. Ms. Horsell is the Director of Marketing and Portfolio Management. Ms. Thomas is the Human Resource Manager. Functional line managers in the research and development department. Engineers and members of your project team.

You have been leading a small team of experienced engineers conducting a technical feasibility study to investigate if it is possible to modify one of its standard products to create a product variant to satisfy the needs of a local organisation involved in environmental management. You are planning to hold a M1 Milestone Concept Review on Friday 16th August 2013. (For the purposes of this assignment assume that this is next week.) The concept review is one of the milestones in the companys product development process. The need for the new product has been identified by the marketing department lead by Ms. Horsell, Director of Marketing and Portfolio Management. Ms. Horsell provided your small project team with a product brief,

outlining the special end user, sales and service requirements to supplement the requirements already established for the standard product. She also developed the business case for the product and believes that there is a market for this variant of the product beyond the customer with the original requirement/request for the modified product.

Schedule and Budget

Great Devices Milestones
The milestones your team will use are: A. M1 Concept review complete (At this point the feasibility study will be complete. A go/no-go decision for the project will be made at this milestone). B. M2 Designs Complete and Reviewed (At this point the overall design will be complete and reviewed. A go/no-go decision for procurement will be made at this milestone. For the purposes of this assignment assume that this go/no-go decision is made at the design review meeting, so you are not required to add any additional tasks for this decision making process). C. P1 proto build start (Everything is ready so that the product prototype 1 is able to be manufactured with the quality level expected). D. P2 proto build start (Everything is ready so that the product prototype 2 is able to be manufactured with the quality level expected). E. M3 Final Design review (At this point the product quality is verified based on the product validation testing carried out on the last prototype. A go/no-go decision for production of required number of units for customer is made). F. M4 Launch review (A go/no-go decision depending if all business areas are ready for market launch and required number of devices are in stock. For the purposes of this assignment this is the milestone marking the end of the project. You are not required to add a task to make the decision it will be made by senior management at this point. This milestone is the end of your schedule). At the M1 concept review it was decided to go ahead with the project. M1 milestone is to be the start of the project. Make the start of the project Monday 19/8/13. This is M1 the first milestone. On Monday 19/8/13 (after M1) you have a workshop led by Mr. Software, Mr. Mechanics, Mr. Electronics, Mr. Production and Mr. Validation to plan the product development activities. They are members of your project team and very experienced managers and engineers. From the team workshop you have obtained the following information: 1. A work break down structure (WBS), resource estimates and some dependencies provided in Table 1 below. 2. Mr. Production also did some preparations prior to the workshop and his input is summarized in the Activity-In-the-Box (AIB) network diagrams in Figure 1. Note that the following abbreviations are used: Electronic Engineer (EE) Software Engineer (SW) Mechanical Engineer (ME) Test Engineer (TE) Production Engineer (PE) Technical Writer (TW) Printed Wire Board (circuit board) (PWB) Electromagnetic Compliance (EMC) Planning Workshop (PW)

Table 1- Work Breakdown Structure

Activity Description Predecessor(s) Person days/weeks of effort 1(and type of resource required.) 2 days fixed duration. 1SE, 1TE, 1ME, 1 PE, 1EE, 1TW will be in attendance. 1 EE for 1 week. (fixed duration) 1 EE for 2 weeks (fixed duration) 1 EE for 2 weeks (fixed duration). To be completed at the following milestone

PW: Planning Workshop

Planning workshop

M1

1.

Electronics 1.1 PWB outline modifications 1.2 Component selection Selection of electronic components. Must be started together with 1.3. Creation of circuit diagram and PWB layout. Breadboard solution created. Must be started together with 1.2. Electronic verification tests with the use of the P1 prototypes. Electronic improvements to circuit diagram, component selection and layout. Electronic verification tests with the use of the P2 prototypes. Verification that electronic heat generation and heat transmission through covers is acceptable. Verification of compliance with electromagnetic compliance regulations. Specification of the software functionality based on user requirements. Detailed specifications of the user interface

Planning workshop(PW) 1.1

1.3 P1 circuit design and PWB layout

1.1

1.4 P1 electronics verification tests 1.5 P2 circuit design improvements 1.6 P2 electronics verification tests 1.7 Thermal verification tests

P1 build complete (5.5) 1.4

1 person-week of EE. 1 person-week of EE. 1 person-week of EE. 1 person-day of EE. M3

P2 build complete (6.5) P2 build complete

1.8 EMC verification tests

1.7

1 person day of EE.

M3

2. Software 2.1 Software specification

PW

1 person-week of SE. 1 person-week of SE. 1 person-week of SE. 2 person-weeks of SE 1 person-week of SE. 1 person-week of SE. 1 person-week of SE. 2 days fixed duration. 4SE, 1TE, 2ME, 1 PE, 3EE, 1TW will be in attendance. 12 person-week of SE. In your initial schedule assign 2 SEs to this task, so it should take 6 weeks.

2.2 User interface specification 2.3 Database specifications 2.4 Software test plans 2.5 Software design 2.6 User interface design 2.7 Database design 2.8 Review of designs and test plans

2.1 2.1 2.2,2.3 2.1 2.2 2.3 1.2,1.3, 2.4, 2.5,2.6,2.7, 4.1, 3.4

M2

2.9 Software development

You can assume that there are four modules of approximately similar effort and if there are 4 SEs available for this task it could be reduced to a duration of 3 weeks (this is still 12 personweeks of SE effort). For this assignment, you can also assume that individual

2.8 (i.e. M2)

2.10 User interface development 2.11 Database development 2.12 R1 release creation

modules will be tested during development Assume this includes interface development and testing Assume this includes development and testing Creation of the R1 software release used for testing with the P1 prototype (in 4.4)

2.8

3 person-weeks of SE. 4 person-weeks of SE. 2 person-days of SE

2.8 2.9,2.10,2.11

2.13 R1 error correction and user interface improvements 2.14 R2 release creation

4.4 Creation of the R2 software release to be used for testing with the P2 prototype Testing of the R2 release with the P2 prototype 2.13

1 person-week of SE. 2 days of SE.

2.15 R2 release tests

2.16 R2 error corrections 2.17 R2 interoperability tests

Correction of errors Testing of interoperability with 3rd party accessory devices. Correction of errors Creation of the software sales release Design of the industrial design for the device. Must be started in parallel with 1.1 and 2.1 Modifications of the PWB to fit the industrial design, new components and usability requirements. Must be done in parallel with 1.1 CAD design of mechanical plastic parts and metal parts for the device. Analysis of the mechanical tolerance stacks compared to part tooling and moulding capabilities. Physical analysis of moulded plastic parts and sheet metal parts used in the first prototype Modification of moulding and sheet metal tools used for P2 parts. Evaluation of P2 mechanical parts and approval of moulding and sheet metal tools used in part manufacture. Creation of a plan documenting what is to be tested. Test of key hardware component reliability to various standard tests like drop and humidity. Test of module functionality after assembly. Test of integration of modules

2.14,6.5 (prototype 2 build completed) 2.15 2.16

1 person-week of SE.

1 person-week of SE. 1 person-week of SE. 1 person-week of SE. 2 days of SE.

2.18 R2 interoperability error correction 2.19 R3 sales release creation 3. Mechanics 3.1 Industrial design

2.17 2.18

M3

PW

2 weeks of a ME/industrial designer. 1 person-week of ME.

3.2 PWB outline modifications

3.1

3.3 P1 mechanical CAD design

3.2

2 person-weeks of ME. 1 person-week of ME.

3.4 Tolerance stack analysis

3.3

3.5 P1 mechanical part analysis

P1 build complete

1 person-week of ME.

3.6 P2 mechanical part modifications 3.7 Mechanical tool approval

3.5

2 person-weeks of ME. 2 weeks of ME. M3

P2 build complete

4. Verification 4.1 Test plan creation

PW

2 person-week of TE 1 person-week of TE

M2

4.2 Component tests

4.3 Module tests 4.4 System integration tests

After delivery of components for P1 i.e. 5.1,5.2,5.3 and also 4.1) P1 build complete, 4.2 4.3 ,2.12

P1

1 person-week of TE. 1 person-week of

P2

4.5 Product validation tests

4.6 Technical Construction File compilation 4.7 Type approval and regulatory approval tests 5. prototype 1 build 6. prototype 2 build 7. Documentation 7.1 documentation plan

and R1 software i.e. testing of P1 prototype Test of product against reliability to various standard tests like drop and humidity and end user requirements. Creation of documentation for regulatory approvals. Approvals from regulatory authorities. see figure 1 for details see figure 1 for details

4.4, P2 build complete (6.5)

TE and 1 personweek of SE 1 person-week of TE

4.5 4.6

See fig 1 for details see figure 1 for details 2.8

1 person-week of TE. 4 weeks by regulatory authorities. See fig 1 for details see figure 1 for details 1 person-week of TW and 1 personweek of SE 2 person-weeks of TW 1 person-week of TW and 1 personweek of SE

M3

Table of contents etc.

7.2 development of documentation 7.3 review of documentation

TW writes documentation Review by SE and corrections by TW

7.1 7.2

M3

8. Production of devices for customers/market 8.1 assembly and production preparation 8.2 Production of devices

M3 Bulk production of required number of devices for customers and market launch 8.1

2 person-weeks of PE 3 weeks fixed duration. Requires 1 PE.

M4

Note: To achieve the WBS numbering shown in the table, you will have to manually enter the WBS numbers in a WBS column. Automatic generation will not produce the above WBS numbers because you should have an outer level summary task for the whole project (and also have milestones at the top of the task). It is very useful to include the correct WBS numbers as this will allow you to check your predecessor relationships by making a comparison with the table above.

Figure 1 - Activity in Box Network Diagrams for Production

Assume that all durations shown are fixed duration. Abbreviations: w is weeks and d is days. Prototype 1
P1 component lead-time P1 prototype build

M2 1

5.1

Suppliers

4w

P1

5.5

P Engineer

2d

P1 PWB manufacture and delivery 5.2 Supplier 4w

P1 mechanical part lead-time 5.3 Supplier 3w

P1 assembly and production test preparation 5.4 1 Production Engineer 2w

Prototype 2
P2 component lead-time P2 prototype build

1.5

6.1

Suppliers

4w

P2

6.5

1 P Production Engineer Engineer (fixed

2d

P2 PWB manufacture and delivery 6.2 Supplier 4w

P2 assembly and production test preparation 6.3 1 Production Engineer (fixed 2w

P2 mechanical part lead-time

3.6

6.4

Supplier

3w

As the project manager you have accepted the tasks of creating the compiled project schedule and allocating resources.

Available Resources
The maximum full time resources available for your project are:

Resource Electronics Engineer Software Engineer Mechanical Engineer Test Engineer Production Engineer Technical Writer

$/hour $95.00 $90.00 $80.00 $90.00 $100.00 $65.00

Number Available 3 4 2 1 1 1

Your team is committed to producing only two prototype iterations to develop and validate the design You know that there are items you did not address at the project workshop 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.

General Information
In addition to the work breakdown structure and AIB network diagram you have collected the following information. The project booking of the proto builds (task 5.5 and 6.5) will have to be done at the latest four (4) weeks in advance of the build. This is the lead time required to include builds in the manufacturings master production schedule. The company will have a general holiday period between 23/12/13 to 3/1/14. You should also include a public holiday on 7/10/13. You are not required to enter any other holidays for the purposes of this assignment. The booking of the Type Approval (TA) test house (task 4.7) has to be done 8 weeks prior to type approval (task 4.7). The engineers work a 40 hour week from Monday to Friday (i.e. a 5 day week with 8 hour days).

Assessment Part A
For part A of the assessment you must complete the following tasks and questions. Read all the questions before you commence the tasks. 1. Ms Horsell has asked you to use Microsoft Project to develop the project schedule. Note that Ms. Horsell has also asked you to include the milestones at the top of the task list in your schedule. Develop the schedule and make sure that you a) Include the milestones at the top of the task list (underneath the project summary task at the top of the task list). b) Include the resource allocation details on the schedule. c) Resolve any resource allocation issues. Assume that the project is constrained to the resources listed in the case study description above. d) Have an appropriate project name as the top of the task list and have all other tasks indented below this heading. Note that by having the overall project summary task and the milestones at the top of the task list the automatically generated outline numbers / WBS numbers will not correspond to the WBS numbering in the specification. However, you should introduce a WBS column and manually enter the numbering required to keep the work breakdown

numbering specified in the assignment. The WBS column should be placed before the task column. e) Make sure that the holidays described in the general information are not included in the available working days for your project.

2. In this question you must identify the critical path in your schedule. a) The bars of the tasks on the critical path must be automatically highlighted in the Gantt chart view of your project schedule (in the .mpp file). The marker should be able to view all tasks in the project when they open the .mpp file. b) List the tasks on the critical path in your answer to this question in the Word document.

3. Include additional milestones (tasks with 0 duration) in your schedule to show the latest date you need to contact: a) the production manager to ensure that the facilities are booked for the prototype builds (i.e. two milestones one for each prototype build). b) the type approval test house to ensure that the facilities are booked for the type approval. c) According to your schedule when is the latest date that you need to contact: The production manager to book the facilities for the first prototype build? The production manager to book the facilities for the second prototype build? The type approval house to book the facilities for the type approval? Note that these additional milestones should be listed at the end of the milestones list at the start of the project and should be highlighted in the task list in yellow using the background colour icon on the task ribbon. This is to allow your marker to locate them easily. 4. Write a memo to the director of product development, Ms. Horsell outlining: a) the expected completion date of the project, assuming it commences at M1; b) the total duration of the project; c) an explanation of the main factors that cause the project to require that length of time d) the estimated labour cost of the project after the M1 concept review. Present the costs in a table showing the costs for the following: Planning workshop Electronics Software Mechanics Verification Prototype 1 build Prototype 2 build Documentation Production of devices for customers Total for the Project Assume that you will send the project schedule as an attachment to the memo. 5. Generate a who does what report using the Microsoft Project reporting facilities. The start of a who does what report for a different project is shown below. Include a screenshot of your who does what report as the answer to this question in your Word document.

6. Is there any way that the overall duration of the project can be shortened without removing any tasks? (Justify your answer. Be specific and describe any tasks that you would target and what you might do that could reduce the length of the project.) 7. Describe what the project manager needs to do to ensure that the project runs smoothly and completes on time. Give a detailed answer describing procedures, processes and anything else that you believe is important both in general terms and specifically for this project 8. Is there any way that the cost of this project could be reduced? (Justify your answer. Be specific and describe any implications (apart from the reduction in cost) that could result from you suggestion(s). You are only required to discuss one suggestion to answer this question.) 9. Are there any project related supporting activities, plans, events or tasks that you might have overlooked? If they were overlooked describe how this could impact on the project. .

Assessment Part B
Mr. Production reviews your project schedule and requests that both the prototype builds also include the participation of one engineer from electronics and one from mechanics. You will have to update your schedule as you agree with this proposal. You are now 1 week after the M1 milestone and the display supplier has been revised the delivery time. This is one of the components required for the prototype 1 build (not the prototype 2 build). The delivery time is now expected to take 5 weeks. (This will impact on the duration for task 5.1.) In addition, you are advised that the type approval and regulatory approval tests are now expected to take only 2 weeks. Based on the additional information given above complete the following tasks: 1. Amend the project schedule incorporating the request from Mr. Production, the change to the delivery time for the display and the new estimated times for the regulatory approval task. 2. Describe the impact of each of the changes, i.e. what is the impact of: a. the requirement for the additional resources on the prototype build on both the duration and the cost of the project? b. the change in delivery time for the display component on both the duration and the cost of the project? c. the change in the time for the regulatory approval tests on both the duration and the cost of the project. 3. Are there any options that you would consider instead of making any of these changes? Explain. 4. What is the new duration for the project? What is the new expected completion date for the project?

Assessment Part C
You have been advised that there will only be two software engineers available for the project. 1. Modify your resource details so that there are now only 2 software engineers available. 2. a) Does this result in a resource over-allocation issue in your schedule? b) If so, resolve the resource over-allocation issue. If you had to resolve a resource over-allocation issue explain how you resolved the problem(s). If you did not have to resolve a resource overallocation issue, explain how you would have resolved the resource over-allocation issue. a resource over-allocation issue using Microsoft Project. 3. Has this change impacted on the duration of your project? Explain why/why not. 4. Has this change impacted on the sensitivity of the network? Explain why/why not.

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.

Submission of Assessment
The assignment is to be submitted as four separate files using the electronic assignment submission system that can be accessed from the assessment item 2 link on the course website. The four files to be submitted are: 1. The Word document with the assumptions and solutions to the questions for Part A, Part B and Part C. 2. The Microsoft project files created for Part A, Part B and Part C. Please ensure that the names of these files clearly indicate their purpose, e.g. Xyzzy_Part_A.mpp, Xyzzy_Part_B.mpp and Xyzzy_Part_C.mpp.

Marking Guide for Assessment item 2 Individual Case Study

Assignment Question Part A Q1 The adequacy of the Project Schedule Tasks; correct WBS; overall summary task; auto scheduling Durations/effort Resources allocated (+ no over-allocation) Milestones Predecessor relationships holidays Critical path highlighted and tasks listed Dates of bookings Appropriateness of the Written Memo and all information correct according to the schedule Who does what report Details on shortening the Project Ensuring finished on time Reducing cost. Overlooked activities 7 Criteria Marks available Marks awarded

Q2 Q3 Q4 Q5 Q6 Q7 Q8 Q9 Sub Total Part A Part B Q1 Q2 Q3 Q4 Sub Total Part B Part C Q1 Q2 Q3 Q4 Sub Total Part C TOTAL Comments:

1 1 4 1 2 3 2 3 24 2 3 1 1 7 1 1 1 1 4 35

The adequacy of the amended Project Plan (+ ensure no resource over-allocation) Discussion of the impact of each of the changes (for each discuss impact on budget and duration) Discussion of options Overall duration change

Change to 2 SEs Resolution of resource issues Impact on duration + explanation Impact on network sensitivity + explanation

Lecturer: _______________________________ Lecturers signature: _______________________ Date: / /