My supervisor has regular fortnightly meetings with his students. I prepare slideshows for each meeting, as if I was preparing a talk for a conference or seminar. These slideshows grow as I progress. For issues that I need his help with, I have a separate "trouble-shooting" slideshow. After reaching a certain milestone, he will ask me to write it up. I never write anything before it is theorised or before all the tables and figures are done and okayed by him. It saves an enormous amount of time and makes progress visible. This process of course is not possible outside semester times when there are no meetings but those longer periods are then used for reading, clarifying issues and problems, and editing older drafts. It has made the supervision process super efficient.
I used grounded theory methodology and manual data analysis.
My research was interview based. I would open code multiple responses to a question present it in a word doc and send this to my supervisor. We would send this back and forth until we agreed. I would then code the rest of the questions. I used the same process for the following GT coding stages.
I now use this system with my students, the depth of the analysis/coding stages dependent on the level of degree being studied.
Hope this helps.
- Badges
- Science topic
- Similar topics
- Computer Science and Engineering
- Software