This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
initial_plan [2011/10/02 15:17] – created scmfcl | initial_plan [2017/12/19 09:45] – scmfcl | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Initial Project Plan ====== | ====== Initial Project Plan ====== | ||
- | The final year project is a substantial part of your degree. It can have a | + | The final year project is a substantial part of your degree. It can have a major effect on the degree class you are awarded and even whether or not you pass the degree. The initial project plan is to make sure you understand what your project requires you to do and how you are going to finish it successfully. You must submit an initial project plan at the beginning of your project. |
- | major effect on the degree class you are awarded and even whether or not | + | |
- | you pass the degree. The initial project plan is to make sure you understand | + | |
- | what your project requires you to do and how you are going to finish it successfully. | + | |
- | You must submit an initial project plan at the beginning of the first semester of | + | |
- | your project | + | |
- | description). | + | |
- | The initial | + | The initial plan is marked |
- | you should discuss the plan with your supervisor | + | |
- | make sure both of you agree on what your project entails. You should further check the | + | |
- | project plan with your moderator, but the first person to talk about it is usually your | + | |
- | supervisor. | + | |
- | We suggest that you write an initial version of your project plan and arrange meetings | + | We suggest that you write an initial version of your project plan and arrange meetings with your supervisor to discuss it and revise the plan. If you are not sure what to write in the plan, please discuss this with your supervisor |
- | with your supervisor | + | |
- | what to write in the plan, please | + | |
- | supervisor and moderator are happy with your plan, submit it to PATS and they can | + | |
- | officially approve it there. As you can resubmit | + | |
- | also submit a draft and your supervisor and moderator can look at it there and even leave | + | |
- | comments. However, unless there are exceptional circumstances (e..g supervisor or moderator | + | |
- | may be away), we highly recommend to discuss the plan in person and not just in PATS or by | + | |
- | e-mail. | + | |
- | Finally, note that this is an initial plan, and you can, and most likely should, adjust | + | You can find the deadline for submitting your initial |
- | plan as you progress. Note, however, | + | |
- | intend to deliver at the various stages of the project (in particular for the final and, if | + | |
- | applicable, interim report). | + | |
- | For information about how to submit your initial plan via pats please see the [[Submission Guide]]. | + | Finally, note that this is an initial plan, and you can, and most likely should, adjust the plan as you progress. Note, however, that with the initial plan you are prescribing what you intend to deliver at the various stages of the project as explained below. |
+ | ===== Ethics ===== | ||
+ | |||
+ | For the initial plan you should consider, after discussion with your supervisor, whether the project will require research that needs ethical approval. See [[http:// | ||
===== Structure and Contents ===== | ===== Structure and Contents ===== | ||
- | For the initial plan one to at most two pages text are sufficient. It should contain | + | Your initial plan should be at most 2,000 words, excluding any figures and tales. It should contain the following information: |
- | the following information: | + | |
==== Project Title ==== | ==== Project Title ==== | ||
- | The title of the initial plan document should be " | + | The title of the initial plan document should be " |
- | title of your project. List yourself as author and also say who your supervisor | + | |
- | and moderator is. | + | |
==== Project Description ==== | ==== Project Description ==== | ||
- | The first section of the document should be a brief description of your project | + | The first section of the document should be a brief description of your project outlining |
- | outlining its context and what it is overall | + | |
- | project description | + | |
- | a lot of detail there and this would usually not be longer than half a page. | + | |
==== Project Aims and Objectives ==== | ==== Project Aims and Objectives ==== | ||
- | The second section of the document should be a list of top-level | + | The second section of the document should be a list of more detailed |
- | for your project. These are statements of what you set out to achieve with your project. | + | |
- | Try to be as specific as possible | + | |
- | details that may change later. | + | |
- | level of sub-points is usually sufficient. | + | |
- | === For Projects with Final Report Only === | + | ==== Work Plan ==== |
- | If you are taking module CM0300, CM0333 or CM0400 your aims and objectives are what | + | The last section of your initial plan should consist of a time plan stating what you are working on when. This should include clear milestones of what you expect to achieve by which date and also show how you intent to achieve these milestones. |
- | you expect to have at the end of the module for your final report. | + | |
- | === For Projects with Interim | + | Make sure you clearly describe what you intend to include in the deliverables required for your project type, i.e. state what you will produce for the interim |
- | If you are taking module CM0343 you should | + | Your time plan should |
- | in the interim report and the final report. Note that the contents of the interim report | + | |
- | should | + | |
- | and the final report as volume II of your overall project report. Your final deliverables | + | |
- | (e.g. any final versions | + | |
- | + | ||
- | What to include | + | |
- | should | + | |
- | the total project work. This would usually be the results of the background study and a | + | |
- | detailed analysis of the problem | + | |
- | problem. For some projects, e.g., it may also contain an initial version of a final | + | |
- | deliverable | + | |
- | + | ||
- | The final report then contains the overall project findings | + | |
- | complete set of deliverables developed | + | |
- | project. The report should not repeat | + | |
- | it and expand on it. | + | |
- | + | ||
- | Your project plan effectively defines what should go into which report. Hence, you should | + | |
- | carefully discuss this with your supervisor to make sure there is enough for 25% in the | + | |
- | interim report and you neither try to do too much or too little for the interim report. | + | |
- | + | ||
- | ==== Work Plan ==== | + | |
- | The last section of your plan should consist of a time plan stating what you are working | + | You are free to choose the work plan format that you think is best suited for your project and working |
- | on when. This should include clear milestones of what you expect to achieve by which date | + | description |
- | and also show how you intent to achieve these milestones. | + | |
- | the final (and interim) report clearly link with your time plan, such that you can actually | + | |
- | deliver them when they are due. | + | |
- | You are free to choose the work plan format that you think is best suited | + | ==== Planning |
- | This //may// be in a GANTT chart format, but sometimes it may also be fine to simply list | + | |
- | in sequence what you are working on. Usually a weekly scale for the plan is a good choice. | + | |
- | Take note of the deadlines for the deliverables as listed in your PATS project description | + | |
- | when you develop the work plan. | + | |
- | ===== Approval Procedure ===== | + | This section is only relevant if you have to produce an interim and a final report for your project. Note that the final report should not repeat content of the interim report. They should rather be two reports that overall make up your project report. |
- | Once you have discussed | + | What to include in the two reports depends on the nature of your project. Your interim report should provide the results of the first stage of the project, representing about 25% of the total project work. This would usually be the results of the background study and a detailed analysis of the problem with a description of an approach of how to address the problem. For some projects, e.g., it may also |
- | submitted it on PATS, both, your supervisor | + | contain an initial version of a final deliverable or some other building block of the overall project. It is not necessarily everything you have done by its due date (this depends on your time plan and other commitments), |
- | as well. They can also choose to leave any comments with your plan. You will see the comments | + | |
- | and the approval as soon as they have done this. | + | |
- | You can resubmit your plan at any time until the deadline listed. Should you resubmit a plan | + | The final report contains |
- | that has already been approved, | + | |
- | approved again. | + | |
- | After the submission deadline | + | Your project plan effectively defines what should go into which report. Hence, you should carefully discuss this with your supervisor |
- | edit their comments, etc. and in very special cases even remove approval (they should | + | |
- | get in contact with you to discuss if they choose | + | |
- | one week after the plan submission deadline. After this approval deadline they cannot | + | |
- | undo any approval (but still approve your plan in case there is any delay, just that | + | |
- | approval will then be final). | + | |
- | In case you fail to submit your plan by deadline or wish to resubmit a plan after the | + | ===== Marking Criteria ===== |
- | submission deadline, please get in contact with the project coordinator to discuss this. | + | |
+ | Your supervisor and moderator will mark your plan according to the following criteria: | ||
+ | * Title and project description accurately represent the project and are suitable for the module you are are taking; | ||
+ | * Aims and objectives are clear, sufficiently detailed and provide a suitable challenge for your project; | ||
+ | * Time plan is feasible, sufficiently specific to the project, and has a clear timeline and milestones; | ||
+ | * Deliverables for the reports required for your project are suitable and clearly specified; | ||
+ | * Approximate dates for at least two review meetings are given; | ||
+ | * The amount of work is suitable for the credits and level of the module; | ||
+ | * The report is well written and clearly structured; | ||
+ | on the following scale: | ||
+ | * 0 marks: No suitable plan has been submitted. | ||
+ | * 1 mark: Only a partial plan with major deficiencies/ | ||
+ | * 2 marks: A plan with a project description, | ||
+ | * 3 marks: ...which is feasible to execute within the constraints of the project... | ||
+ | * 4 marks: ...and has sufficient project-specific details and clear milestones... | ||
+ | * 5 marks: ...and shows originality and professionalism and/or scholarship. | ||
+ | Supervisor and moderator will leave comments about your plan explaining any concerns they may have and their expectations regarding the aims and objectives and deliverables. Make sure you consider these when executing the project. |