Information on What to put into your Internship Reports
The list of deliverables is for me. If it makes sense, give
two lists: deliverables for me, deliverables for your sponsor.
One reason that you may want to give two lists is if what you
are doing is proprietary. You may give your sponsor material that
you describe at a different level for me in reports. Also, note that I have,
at times, signed nondisclosure agreements with companies.
Reports can be whatever:
- pseudocode,
- code,
- requirement spec,
- design spec,
- testing plans, testing results,
- diagrams, discussion,
- website with some explanation (for example, why you
chose the technologies you did, or why you designed as you did).
If you know what you will deliver, e.g., you know the first thing you
will give me is a Requirements Specifications, then put that as the
deliverable instead of a generic report.
The reports/deliverables don't need to be long, just clear.
I always like meta-information as well, especially in the final
report. Tell me about the process. For example,
- What did you learn? What do you wish you would have learned?
- How did you enjoy what you're doing?
- Things that went well? Things that didn't go well?
Things you would change if you did it over?
- Was the mentoring handled well? Why or why not?
- What were the challenges in your project?
Did you have to communicate with non-technical people?
If so, how did it go?
- Problems? Cool things?
- Would you like to continue working at your internship company?
Why or why not?