Professional development

Skills matrix & action plan

A working document for tracking skills, evidence, and next steps throughout the MSc.

This is an initial planning framework, not a claim that every skill has already been demonstrated. Update each row with evidence from real coursework, feedback, and projects.

Initial skills review

Skill area	Current focus	Evidence to collect	Next action
Programming	Developing practical coding ability.	Completed code, README, tests, and a short explanation of design choices.	Build small, clearly scoped exercises and document what I learn.
Version control	Using Git and GitHub as part of my learning workflow.	Meaningful commits, repository history, branches where appropriate, and project documentation.	Practise a consistent commit message and review workflow.
Research and referencing	Learning to evaluate computing sources and reference them accurately.	Annotated source notes and coursework references checked against the university guidance.	For each assignment, distinguish evidence, author interpretation, and my own analysis.
Critical thinking	Moving beyond description to compare evidence and viewpoints.	Work that considers benefits, limitations, assumptions, and alternative perspectives.	Include a counterargument and explain why evidence supports my conclusion.
Communication	Improving clarity, structure, and concise academic writing.	Drafts revised after feedback; clear explanations of technical decisions.	Use shorter sentences, proofread punctuation, and check paragraph purpose.
Reflection and teamwork	Using feedback to identify strengths and development needs.	Actual peer/tutor feedback, meeting notes where applicable, and follow-up actions.	Record feedback and turn each useful point into a specific action.

Action plan

Goal	Action	Success measure	Review point
Strengthen academic writing	Plan paragraphs around one clear point, support claims with sources, and proofread.	Clearer drafts and fewer sentence/punctuation issues in feedback.	After each assessed task.
Build a reliable GitHub portfolio	Keep module pages current and add genuine artefacts with descriptions.	Each completed module has evidence, reflection, and relevant feedback.	At the end of each module.
Improve technical confidence	Complete small practical exercises and explain how they work.	Working examples with readable documentation and tests where appropriate.	Monthly.
Develop critical analysis	Compare at least two perspectives and identify limitations in evidence.	Assignments explain why evidence matters, not just what a source says.	Before submitting coursework.

Review log

Review date: Add date
What improved: Add specific evidence.
What remains difficult: Identify one or two honest development needs.
Next adjustment: Record the action and a realistic review date.