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:
- 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.
- You project managed (keeping evidence of records, plans, outcomes) the delivery using a suitable project/process lifecycle (LO9).
- You identified and managed risks (LO3) on the way and identified and utilised skills, resources and people you needed (LO3).
- You made use of technical concepts and principles (LO1) from your Level 3 modules.
- 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).
- 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).
- You carried out a literature review using quality, credible and relevant sources in which to ground your work, and supporting your decisions (LO4, LO6).
- You worked independently as much as possible and learned new skills and knowledge that you applied to your project (LO8).
- 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.
- You replanned and rescheduled your work when things went wrong (LO9, LO3, LO5, LO8).
- You communicated effectively through TMAs/EMA, reports, emails etc with your tutor and other project stakeholders (LO7).
- You engaged the sponsors and/or users throughout the project journey, where appropriate, seeking feedback on interim deliverables and they evaluated your final artefact.
- 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.
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.