OU blog

Personal Blogs

Christopher Douce

TM470 Considering Careers

Visible to anyone in the world

I would argue that the project module provides four outputs:

  1. It enables you to consolidate and further develop your skills and knowledge that have been gained from your study of previous modules.
  2. It enables you to gain important and necessary academic credit that contributes to your degree.
  3. It enables you to complete a specific named degree that is recognised by an industrial body: the British Computer Society.
  4. It enables you to create an extensive and detailed project report that you can show to a potential employer.

This fourth point can be easily overlooked. When writing your report, imagine bringing it to a technical interview. Interviews are all about demonstrating your skills and abilities to someone who has a problem that needs to be solved. Your report should, of course, be written in such as way to showcase your skills, knowledge and what you have achieved.

If you have written your report with this in mind, there is no reason why you should not bring your end of project report to an interview. To efficiently share what you have done, one idea is to create an additional ‘presentation appendix’ that you can add to the end of your report. This could contain a very short series of PowerPoint slides, that have been designed so you are able to talk someone through your project.  Prepare for five minutes, no more. You can always go into more technical detail if you need to.

In addition to mentioning your project on your CV, if your project involves designing and building software, you might consider sharing your code through a GitHub repository. Not only can you include a link to the repository in your project work, perhaps as an appendix, but you could also share a link to your repository to your CV. The effect of this will be to highlight your professional skills.

When you are writing your project report, make sure you consider all your potential readers: your tutor, your examiner, and anyone else who might be interested in learning about your skills and abilities. Rather than thinking of the report as something that allow you to gain three of the academic outputs that come with studying a project module, think how you might present what you have done to a potential employer.

Careers support

The OU runs a career service. The service is funded through a portion of your student fees and is available for every student for up to three years after graduation.

As you work work on your project, begin to look at the different services that are offered by the university careers and employability service. Through the service, you can book in a one-to-one consultation with a careers advisor, access events about career planning, and internship and job vacancies.

Here is a short summary of some of the services offered by the careers service, taken directly from the opportunity hub website:

  • Explore career pathways.
  • Get help with qualification and career goals.
  • Build your work experience.
  • Develop skills for the workplace.
  • Get help with job seeking applications.
  • Explore further study.

A further resource that may be considered used is the Prospects website that provides information about further study, information about jobs, and further careers guidance.

Reflections

Very early on in my career, I found a vacancy through Prospects. I made and application, and was selected for interview. I made sure I took with my recently completed dissertation. I showed it to my interviewer.

I didn’t end up getting the job I had applied for, but I did end up getting a different opportunity (for which I am always grateful for). My dissertation showed what I was capable of doing, and it must have made an impression. Your project report has the potential to do the same.

A further reflection is that there is a lot of career related resources that are provided by the university. There is often a separation between the academic study, and the exploration of employability choices and options. It is really important that we find the time to explore the resources that are available. It is also useful to remember that we have access to the careers service for three years after graduation.

Permalink Add your comment
Share post
Christopher Douce

TM470 Project Report as a journey

Visible to anyone in the world
Edited by Christopher Douce, Tuesday 25 July 2023 at 08:55

The main output from the TM470 project module is a project report. 

The report shares what has been done and what has been learnt. The ‘things done’ bit relates to the planning, the reading (and any research that has been done), and the actual work that has been carried out. The ‘things learnt’ bit is shared in a section which is used to share reflections, or thoughts about all the work that has been carried out.

One of the bits of advice I offer students is: think of the TM470 project report as a “technical story”. When sharing this view with fellow tutors, another tutor, Kawal Banga, shared another metaphor: the TM470 project as a journey. 

Kawal shared a list of 13 really useful points which relate to actions that take place on the journey of completing TM470. The links to the module learning outcomes are, of course, associated with each of these points:

  1. You identified a real business/social problem that could be solved through an ICT solution (LO2), engaging with sponsors/users who needed a solution to the problem. 
  2. You project managed (keeping evidence of records, plans, outcomes) the delivery using a suitable project/process lifecycle (LO9). 
  3. You identified and managed risks (LO3) on the way and identified and utilised skills, resources and people you needed (LO3). 
  4. You made use of technical concepts and principles (LO1) from your Level 3 modules. 
  5. You analysed, designed and developed an ICT solution building on and extending skills from your Level 3 and other modules (or equivalent professional skills), and using any additional skills you needed (LO11). 
  6. You took into consideration any LSEPIs (Legal, Social, Ethical, Professional issues) and EDI (Equality, Diversity and Inclusion) issues and modified your project and your behaviour to deal with such issues (LO10).  
  7. You carried out a literature review using quality, credible and relevant sources in which to ground your work, and supporting your decisions (LO4, LO6). 
  8. You worked independently as much as possible and learned new skills and knowledge that you applied to your project (LO8). 
  9. You reflected on things (processes, tools, resources, studying, etc) that worked or things that didn’t work (LO5), and lessons and skills (technical, professional, academic, organisational, project management) that you learned through the project.  
  10. You replanned and rescheduled your work when things went wrong (LO9, LO3, LO5, LO8). 
  11. You communicated effectively through TMAs/EMA, reports, emails etc with your tutor and other project stakeholders (LO7).  
  12. You engaged the sponsors and/or users throughout the project journey, where appropriate, seeking feedback on interim deliverables and they evaluated your final artefact. 
  13. You can prove all of the above with solid evidence that you collected over the project journey, and can communicate this effectively to your tutor and other stakeholders.

It's really helpful to reflect on his list. 

Another thought is that the notion of stories and journeys are compatible with each other. In some respects, my advice for the TM470 Project Report Structure reflect both perspectives. This structure intends to take the EMA examiner on a journey from the start of the project to the final summary, which should clearly highlight the learning that has taken place.

Acknowledgements

Many thanks to Kawal for giving permission to share his list. Thanks also to fellow tutors who responded to my post about the notion of the project report being a story.

Permalink Add your comment
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 3289763