1. The Project Proposal

2. Main Headings Summary Project Background Project Description
Project Aim
Project Objectives
Evaluation Criteria
Deliverables
Timeframes and Project Plan
Technical and Non-Technical Resources Required
References

3. Summary of Project

4. Summary of Project No more that 350 words
To create the first draft, just answer the questions on the following slide.

5. Questions What is the area of study?
What is the problem being tackled?
What does the literature say?
How did you tackle the problem?
How did you implement the solution?
What results have you gotten?

6. Sample Answers
“This research investigates the area of knowledge capture in the domain of knowledge management.”
“By introducing a new technology into my work place the staff will be able to record their ideas.”
“Existing research indicates that their may be benefits to capturing the organisational knowledge.”
“In this work a Wiki server was be introduced into the workplace, and logins provided to staff.”
“The Wiki has a range of templates to support the range of approaches to ideas generation.”
“Results suggest that the use of this Wiki has aided in capturing key organisational knowledge.”

7. Merge into abstract
This research investigates the area of knowledge capture in the domain of knowledge management. By introducing a new technology into my work place the staff will be able to record their ideas. Existing research indicates that their may be benefits to capturing the organizational knowledge. In this work a Wiki server was be introduced into the workplace, and logins provided to staff. The Wiki has a range of templates to support the range of approaches to ideas generation. Results suggest that the use of this Wiki has aided in capturing key organisational knowledge.

8. Project Background

9. Project Background At least three pages long.
This is NOT to explain how you came up with the idea of the project, but rather to discuss some of the literature associated with your project area, without mentioning the specific research project that you are undertaking.

10. Project Background
So it’s about setting the scene for the project and explaining background to this research
How does it fit into the overall context of your discipline (e.g. Knowledge management / Engineering)

11. Project Background
Provide a couple of definitions of AT/IT/DA/KM that support this research
Provide several references in this section (between at least).
Don’t talk about your specific research in this section

12. Project Background
Include a few mentions of what people have done in the past,
And add in diagrams from their work...

13. Project Background

14. Project Description

15. Project Description
At least a page and a half to two pages
The description needs to tell us two things, this is WHAT I’m going to do, and this is WHY I’m doing it.

16. YOU Project Description Results Literature Review Survey Artefact
All discussed
in the context
of the literature
Thesis
Results
Evaluation

17. Project Description
Include a few diagrams to show the architecture of:
The experiment
The artefact
The models

18. Project Description

19. Project Description

20. Project Description

21. Project Description

22. Project Aim

23. Project Aim This is the “thesis” of the project
Consider using Bloom’s Taxonomy Verbs in stating your aim.
e.g. “This research will measure how Web 2.0 tools can improve collaboration and knowledge sharing”

24. Bloom’s Taxonomy
Bloom, B.S. (Ed.) (1956) Taxonomy of educational objectives

25. Bloom, B.S. (Ed.) (1956) Taxonomy of educational objectives

26. Bloom’s Taxonomy
Evaluation: appraise, argue, assess, attach, choose compare, defend estimate, judge, predict, rate, core, select, support, value
Synthesis: arrange, assemble, collect, compose, construct, create, design, develop, formulate, manage, organize, plan, prepare
Analysis: analyze, appraise, calculate, categorize, compare, contrast, criticize, differentiate, discriminate, distinguish, examine
Application: apply, choose, demonstrate, dramatize, employ, illustrate, interpret, operate, practice, schedule, sketch, solve, use
Comprehension: classify, describe, discuss, explain, express, identify, indicate, locate, recognize, report, restate, review
Knowledge: arrange, define, duplicate, label, list, memorize, name, order, recognize, relate, recall, repeat, reproduce state

27. Project Objectives

28. Project Objectives Typically between 4 and 7 objectives
The objectives are the milestones in reaching your project aim.

29. Project Objectives Suggested objectives Review appropriate research
Identify interesting approaches
Identify a range of opinions
Design the experiment
Execute the experiment
Analyze the results

30. Evaluation Criteria

31. Evaluation Criteria About half a page for this section
How you intend to implement and evaluate your research?
What methods are you going to use, both quantitative and qualitative?

32. Evaluation Criteria
Can you find a formal framework for assessing the outcome the a previous project has already used?
Use standards?
IEEE 829 Standard for Software Test Documentation.
ISO 9126 and ISO (which are standards on software evaluation)

33. Evaluation Criteria Suggested criteria The suitability of the design
The suitability of the experiment
The suitability of the evaluation

34. Evaluation Criteria How do you evaluate the project?
How effective were the tools you used?
Did the tools prove to be suitable?
How effective were they at measuring your research question?
Did the tools accurately model the research question?

35. Evaluation Criteria
How have other researchers who have done similar projects in the past evaluated their projects?
Is there a standard model, framework, or instrument to be used?

36. Deliverables

37. Deliverables Literature Review Dissertation Document Software
Survey results on CD
Etc.

38. Timeframes and Project Plan

39. Timeframes and Project Plan

40. Timeframes and Project Plan
You need create a Risk Mitigation, Monitoring and Management matrix.
An effective strategy must consider three issues:
risk avoidance,
risk monitoring, and
risk management and contingency planning.

41. Risk Mitigation, Monitoring and Management
Example:
Assume that high staff turnover is noted as a project risk

42. Risk Management Contingency Planning
Assumes that mitigation efforts have failed and that the risk has become a reality
Continuing the example, the project is well underway and a number of people announce that they will be leaving
If the mitigation strategy has been followed, backup is available, information is documented and knowledge has been dispersed across the team

43. Risk Mitigation
A proactive approach to risk avoidance is the best strategy. Develop a plan for risk mitigation. For example: assume that high staff turnover is noted as a project risk r1, some of the possible steps to be taken are these:
Meet with current staff to determine causes for turnover
Assume turnover will occur and develop techniques to ensure continuity when people leave.
Define a backup staff member for every critical technologies.
Double everyone’s salary

44. Risk Monitoring
As the project proceeds, the following factors can be monitored:
general attitude of team members based on project pressures,
the degree to which the team has jelled,
interpersonal relationship among team members,
availability of jobs within the company and outside it
As the project proceeds, risk monitoring activities commence.
In addition of these factors, the project manager should monitor the effectiveness of risk mitigation steps.
Project manager monitors factors that may provide an indication of whether the risk is becoming more or less likely

45. Types of Risks Discuss project-based risks only These are NOT risks;
I might get sick in the middle of my project
I might get a promotion and be too busy in my job
My girlfriend/boyfriend might run off with my best friend
My dog might run away
My supervisor might now give me a lot of feedback

46. Types of Risks These are risks; My test audience might not help me
The tool I use might not fully match the requirements
I might not get the technology/software I need
I might not get a lot of responses from my survey
Problems might take longer to solve than I predicted

47. RMMM Matrix Risk Level of Risk Management Monitor Mitigation 1
Loss of any/all part or project
Moderate
Develop a comprehensive back up strategy at the start of the project.
Ensure backups are being completed. Check files dates and sizes.
Keep daily, weekly and monthly backups on multiple devices. 2
Insufficient responses to questionnaire
Critical
Keep log of answered questionnaires
Reference questionnaires completed against timeframe
Ensure questionnaire available to enough people 3
Lack of time for project due to settling in time in new work position
Low
Follow plan for completion of dissertation
Continuously track dissertation progress
Allow an occasional annual leave day if behind

48. Technical and Non-Technical Resources Required

49. Technical and Non-Technical Resources Required
Access to people
PC / Laptop / PDA / etc.
Software Libraries

50. References

51. References
At least 20+
Up-to-date references
In Harvard format