This action might not be possible to undo. Are you sure you want to continue?
Type of assignment: Group assignment (group of 4 to 5) (60%) To be submitted to: Dr A Lung at the RV reception by 20/5/10 (Wednesday)
Description of the assignment : Based on a given case study (starting from page3), prepare a Project Planning Document (PPD) to persuade your company boss that the whole project is worthy of the necessary investment. Goal : The goal of this assignment is to enable the project team to plan its work ahead and overcome any potential difficulties. By establishing a solid project management plan, the team will have identified the problem it is solving, the strategies and tactics it will use to address the problem, the resources it needs to complete its work. Additionally, the team will have developed a mechanism for controlling the project and measuring its outcomes to reach its goal. You must provide some evidence how the measurement of success is to be judged. It is also advisable to split the project into tasks and different tasks can then be undertaken by different team member. You have some flexibility to break the problem down and create appropriate solutions.
Costs: Each resource you use should have a commercial cost associated with it, so that the total
cost of your project plan can be calculated. Unless instructed otherwise, you should use £40-£70 per hour for a team member, £70-£100 for managers and £20-£40 for support/administrative staff. Other resources may be required and should be costed, but bear in mind that this is only one small element of your assignment and doesn’t have to be too detailed.
1. Project Evaluation and Estimation Strategy 30%
Consider the characteristics of this project and write a brief report (maximum three sides A4 typed) describing the implications to the project manager (resource limitations, risks, quality requirements etc.), your proposed life-cycle model and your justification for the estimation approach you have taken. 2. PPD (Project Planning Document) 70%
Produce a Project Planning Document showing how your project will be initiated. This should comprise a Gantt Chart (including Work Breakdown Structure code, a deliverable, resource allocation, effort estimate and cost for each task) and daily, weekly or monthly effort by resource. By all means include other sections suggested in the PPD guide if you think they are appropriate. Either MS Project or Pert
2 . Aim for about 10 tasks .your project view will dictate whether these are high-level or low-level tasks.Master can be used to produce the necessary task schedule and Gantt Chart.
training etc). A project mission statement 3. Project work objectives (a list of all deliverables such as reports. This identifies all of the tasks that must be performed in order to achieve the objectives of the project. 6. Exit criteria. Schedules (milestones and working schedules)** 9.) 7. Risk areas with contingencies if possible ** Important Note: 7 & 8 can be completed by using either Microsoft Project or Pert Master 3 . Control systems (a description of how the progress on the project will be monitored) 11. equipment. software. The plan must include the following components: 1. materials and facilities needed to complete the project). 10. 5. End-item specifications (This is a list of the items that will accompany finished project. These criteria are used to determine when each milestone in the project has been reached. the end specifications would be the documentation that will be left with the trainer describing how the course materials were put together and how changes can be made if needed be. A problem statement 2. Project objectives 4. Contributors (a list of what each team member will be responsible for) 12. For example if a training course is to be created.** 8. Work Breakdown Structure. Required resources (people. user guide.The Project Management Plan is a team assignment.
Last Updated: 01st March.Project Plan Shopkeeper Inventory & Asset Management Project for a manufacturing company Marwin Machine Tools Ltd NOTE: This is a fictitious case study. 2007 4 . You should use this case study to prepare a PPD (Project Plan Document) to your line manager about the details of the project and to seek for their approval.
etc.1 Inclusions 1. 4. 3. 2. 0. drills and CNC milling machines.2 Exclusions 1.e. To provide a networked solution that can be accessed outside of the Shopkeeper’s office. The Shopkeeper is using a simple Access Inventory Database that provides him/her with the ability to track inventory. 2. there is a requirement to provide inventory reports for the City of Raleigh’s internal auditors. The tracking of assets or inventory outside of the Shopkeeper’s i. Interface between the Employee Database and the Shopkeeper’s application. this number “follows” them from service reports into court. Objectives of the proposed project The objectives of this project are as follows: 1. The company operates in two shifts per day. Interface between the barcode printer software and the Shopkeeper’s application. The formal creation of a Purchase Order. To provide an application that provides flexible reporting capabilities. 5. vehicles etc. 3. To provide the Shopkeeper with an automated tool to aid in the tracking of inventory. Currently Shopkeeper tasks in Marwin Ltd are very manually intensive. The employee receives their equipment/clothing. In addition to reports and forms used by the Shopkeeper. and require constant tool changes and safety clothing. 3. 5 . Periodically they do spot check inventories (count the clothing and supplies) to ensure their numbers in the database are correct. It has many machining centres such as CNC lathes. The tracking of Shopkeeper inventory including both equipment and clothing. In addition to being used internally for things like equipment requests. The employee enters a request sheet (like a sign in sheet) 2. employs around 120 people. 3.1 Current Process Our current process for personnel to obtain equipment and clothing is as follows: 1. The company’s main business is to produce small hand tools for a wide range of customers. 4. An interface between the Shopkeeper’s application and FIS (internal Purchasing system). 1. 1 Scope 1.Background Marwin Machine Tools Ltd is a SME company. The Shopkeeper enters the information into the Access DB. Each employee has a unique code number they use to identify themselves. When the Shopkeeper needs to order new inventory he/she submits a Purchase Request to Finance where a Purchase Order is generated by FIS (our Purchasing System). 2.
4 Development o o The development work will be performed at the vendor’s location. 1.5 Installation o o o o o The vendor will send install disks for the application. including Hardware and Software. The Shopkeeper and company management are responsible for approving the application after the final application delivery. CoR IT is responsible for leasing and installing the server. CoR IT is responsible for installing the application on our server and local PC’s CoR IT is responsible for installing all the hardware. 1.7 Training o o o The vendor will be on-site for 2 days of training. 1.3 Analysis o o You should get some quotes from possible vendors. CoR IT is responsible for setting up the training environment Server PC’s Network 1.8 User Acceptance o o The Shopkeeper is responsible for conducting user acceptance testing. Inc. The vendor is responsible for providing training documentation. The vendor will send all the hardware.6 Testing o o The Shopkeeper is responsible for testing all the incremental releases and providing vendor with feedback on problems or issues. Inventory Specialists. 6 . Each tester will be able to download the latest version for testing. CoR IT is responsible for installing the software on the barcode printer.Other useful information 1. 1. The vendor will import the data from the barcode software to the application. The vendor will deliver incremental releases to the City to test on windows PC’s.
Any issues deemed to be outside of the scope of CoR IT will be elevated to Inventory Specialists. Inc. Process o o All issues and problems will be filtered to the Production Manager. 7 .3 Issues & Problem Management Issues and Problem types may include: o Software: Bugs in the test application o Hardware: Issues procuring or setting up hardware. All issues and problems will be discussed in the weekly status meeting. by the Production Manager.1 Deliverable Acceptance Management The team will be creating a user acceptance document listing all the functions that are required to be tested prior to the team approving and signing off on the application. 2. 2.2 Management Approach 2. 3 Progress Reporting and Communications o You have to suggest how the project team should communicate and how the progress can be monitored.2 Risk Management We will be reviewing and documenting the possible risks to the project during our weekly status meetings.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.