This page was automatically translated from Swedish using Qwen3.5-27B-IQ4_XS. The Swedish version is considered authoritative.

TDDD83 Computer Engineering - Bachelor Project

Summary of Experience

In addition to the bachelor's thesis, each student must also submit an individual reflection summary in the form of an academic essay, reflecting on a course experience such as a project. Reflection entails critically examining your experience and explicitly articulating what you have learned.

Why write a reflection summary?

Reflecting on and writing a reflection summary offers many benefits. By reflecting and documenting your experience, you gain the opportunity to process your course experience and consider how it has contributed to your learning. Without reflecting on the course experience, what you have learned may be forgotten or its learning potential may be lost. Reflective writing requires you to connect your experience to the course content, which helps you hone your analytical skills. Through the reflection document, you demonstrate to what extent the experience has helped you achieve the course learning objectives.

How to write an experience summary?

The individual experience summary should be 3-5 A4 pages (1500-2500 words).
The experience summary is read by your supervisor and must be written in English if your supervisor cannot read Swedish (some supervisors are proficient enough in Swedish to read the experience summary but not the full report).
Each student should focus on their own experiences from the project work, covering both process-related and technical aspects, and reflect on them, for example:
- If you divided the work among yourselves during the project, you might, for instance, discuss experiences related to the areas you focused on more heavily: such as the Scrum Master role or experiences with Ajax or Python.
- Reflect on how your individual skills developed during the work, addressing both technical and process-related experiences.
- Reflect on the execution of the project from your perspective. Did you achieve the individual goals you set for yourself at the beginning of the work? Why or why not?

Gibbs' Reflective Cycle should be used to analyze a specific situation or event regarding both process-related and technical experiences. Gibbs' Reflective Cycle consists of six steps, and your analysis is expected to address all steps in a continuous text:

1. Description	The first step is to briefly describe the situation, event, or experience without making judgments, interpretations, or attempting to draw conclusions. For process-related experiences: What happened? Who was involved? In what context did it occur? What did the involved parties do? How did you act? For technical experiences: What happened? Which technologies were involved? In what context did it occur? (Note: Git/version control counts as a process-related experience).
2. Feelings, thoughts, and reactions	The second step involves clarifying feelings and thoughts without yet analyzing them. For process-related experiences: Concretely formulate thoughts, feelings, and reactions regarding what was described in step 1. What do you think the other involved parties felt and thought? For technical experiences: Concretely formulate the consequences of the event for the project. Again, do not analyze these consequences yet.
3. Evaluation	The third step helps you understand feelings, thoughts, and reactions by asking questions: - What was good and what was bad about the experience/event? - What was positive/negative? Evaluate.
4. Analysis	How can you make sense of the situation, event, or experience? Draw on external thoughts and ideas. For process-related experiences: What actually happened? Were different people's experiences similar or significantly different in any way? If things went well or poorly, how did you and others contribute to this? Which learning objectives relate to the situation, event, or experience? How does this experience improve your understanding of the course material? Does it reinforce or challenge your previous understanding? A constructive critical perspective should be applied here. You may use relevant scientific sources here. For technical experiences: How can positive experiences be utilized in future projects? How could negative experiences have been avoided, and how should things be done differently? Which learning objectives relate to the situation, event, or experience? How does this experience improve your understanding of the course material? Does it reinforce or challenge your previous understanding? A constructive critical perspective should be applied here. You may use relevant scientific sources.
5. General conclusions	Here you should formulate your learning: What did you learn? Explain how your reflection on the experience led to an improved understanding. How did you learn it? What general takeaways can be drawn from these experiences and the analysis you have performed? Why does this learning matter? Consider how your learning helped you achieve a relevant learning objective. Here you can support your conclusions with related scientific publications.
6. Personal action plans	How can you apply what you have learned in the future? What will you do differently in this type of situation in the future? What potential actions will you take as a result of what you have learned, both process-wise and technically? For example, which other techniques, approaches, or solutions can you use?

The model is taken from Gibbs G (1988) Learning by doing: a guide to teaching and learning methods. Cheltenham: The Geography Discipline Network.

The reflection must be supported by at least two relevant scientific articles published in a conference and/or a journal, as well as doctoral dissertations.

Do not include course evaluations here, such as "The course worked well and the labs provided a good start in learning about Flask and JS." Such comments belong in the course evaluation and should not be highlighted in the experience summary.

Tips

Keep a diary throughout the project and use it both as a tool to track progress and as a resource when documenting your experiences.
The technical reflection should describe insights that others could benefit from (i.e., the insight must have objective value), and you should use scientific references to support and elevate the quality and level of the described insight. To illustrate:
Poor insights: “I have learned the important difference between UX design and GUI design.” or "I have learned Scrum, Flask, JavaScript" or "I was not familiar with the concept of Scrum and agile methods before the project started, but thought it would be interesting to test the concept. When I read about the methodology, it seemed suitable for the type of project we were undertaking."
Good insight: “Our initial difficulties in maintaining a runnable codebase in the project have highlighted the importance of continuous integration (Fowler, xx). In practice, this means that every developer …”.

Submission of Individual Experience Summary

The Individual Experience Summary is submitted via Lisam under Submissions/Individual Experience Summary.
The file must be saved in PDF format.

Page responsible: Martin Sjölund
Last updated: 2026-03-12