2.  Planning helps us understand what we want to do, why we are doing it, when, how and where we are going to do it, and who is involved.  Planning also helps us achieve the desired outcome – a good thing if your job depends upon it!

3. ClassificationDescription Size of contents 1TitleProject title. 2IntroductionHighlight what the project is about, what will be done and a brief summary. Max 500 words 3Clear AimOverall aim of the project summarised in two sentences Max two sentences 4Target objectivesSpecify the deliverables of the research as bullet points. Max five points 5TasksThe tasks that need to be done in the project including writing up. Not more than 300- 500 words 6MilestonesThe dates of your completion of each measurable task, for example completion of building a prototype or software code. Max 100 words 7Time chartGraphical display of the tasks and milestone indicating period of activity and times. Max one full page. 8Resource requirements Hardware and software sources that will be involved in the project. Max 100 words. 9ReferencesIdentified the significant references for the study, listed as in Sec. 1.9 Typical 4 References

4.  Not possible to write a work plan without knowing what you are going to do.  To know what you are going to, one has to think, discuss and study.  Work plans are not the copying of material from the web, or from reports – that is called plagiarism.

5.  Meet with your supervisor  Arrange formal weekly meetings with your supervisor.  Buy a hardcover A4 notebook to write down what you are doing on the project everyday.  Buy a pen to use to write down what you are doing.

6.  Clear Aim  Target objectives  Tasks  Milestones  Time chart  Resource requirements  References

7.  Your work plan is not just a report but is a structured way of thinking.  In other words, if you do not spend time thinking it is unlikely you can do a work plan that is reasonable.  We will concentrate on the thinking process in this talk.

8.  Think about what you know about successfully completed projects;  Think in terms of what you want to / have to achieve - aims, objectives, targets and milestones;  Don’t worry about the detail of the project work - individual activities will sort themselves out as the project gets going;  Write it down in a ‘Project Workplan’.

9.  Think about:  the desired outcome  what you want to do,  why you want to do it,  when, how and where you are going to do it,  and who is going to be involved.

10.  A brief description, or "strategic overview“, of your project;  A list of the major activities you expect to have to do;  A clear statement of aims, objectives and deliverables.

11.  WHAT you want to achieve?  Clearly state your objectives.  WHY you want to do it?  Give an explanation.  What facilities, equipment, knowledge, you think you will need?  What resources do you think you will need?  How much do you think it will cost?  Who will you need help from?  Where will you do it?

12. Study of lower leg injuries in car frontal collisions Introduction The importance of the interaction between the pedal box and the lower limbs on the risk of injury of the lower limbs in frontal collision is not currently fully understood, though there has been much research in this area. Both the driver and passenger sustain lower leg and foot injuries, but the seriousness and frequency of these injuries are higher in the driver. Current research has concluded that the sources of these injuries are either the pedals or intrusion into the footwell.

13. The aim of this project is to identify if the pedal box interaction with the lower limbs does increase the risk of injury. If this is found to be the case, the results will be used to try and identify which injuries received by casualties during this type of accident are resultant from the interactions of the pedals. The main objective of the project is to find conclusive evidence to support the hypothesis that the brake, clutch and accelerator pedal do increase the risk of injury to the lower limbs of the driver in a frontal collision.

14. The approach taken includes examining research that has already been carried out in this area and also by conducting analysis of the human body in frontal collisions and the interactions of the brake pedal. The analysis will be computational, using the modelling and simulation technique of multi-body dynamics. The software used will be ‘ADAMS’ with the ‘ADAMS Human Figure’. The model will concentrate on the relative displacements of the footwell, brake pedal and seat during a collision and what effect these displacements have on the driver, in particular the lower leg, ankle and foot.

16.  the desired outcome  what she wanted to do,  why she wanted to do it,  when, how and where she was going to do it,  and who was going to be involved.

17.  Make a time plan;  Base the plan on what you know about what you have to do;  Think in terms of what you want to achieve - aims & objectives;  Identify the major activities.

19. DateDeliverable 15 th November 2008Project Workplan March 2009Poster Presentation 1 st September 2009MSc Project Report  Deliverables are what you have agreed to be the tangible outcomes – i.e. the results – of your project;  e.g. the Project report.  Targets are those results which you aim for at a particular time during the project;  e.g. a working example by a specified time.  Milestones are markers by which you recognize that targets have been achieved.  e.g. a Work Plan on a specified date

20.  Complete the second semester successfully  Sit the examinations  Revise for the examinations  Complete and submit coursework  Attend lectures, tutorials and labs  Check module notes on Blackboard  Make a time plan for the semester  Find out when and where the lectures are  Get a timetable  Check the course modules  Say ‘Hello’ to the MSc staff!

24.  Do your project planning and prepare the time plan using a pencil and paper;  Then if you must, make it presentable using the computer!  Use a simple Word table, or Excel chart;  Advanced planners use specialist software e.g. Microsoft Project.

25.  Cost is important;  Most projects have to work to a fixed budget;  Take into account any time and resource limitations.

26.  “A Plan is nothing, Planning is everything” - Eisenhower,  At the start think about precisely where you want to be and how and when you want to get there.  If you have been through the planning process, you will have a plan which you can refer to for guidance, measuring progress, and as the basis for reviewing progress and direction,  All plans can be changed, but changes should be conscious decisions.