This is part of a series of posts on using NVivo 10 in the context of a team project. It assumes you do not have access to NVivo Server (which allows multiple users to work on the same project at the same time) and are therefore working with stand-alone projects, which can only be opened by one user at a time.
If you have more than one person working on a single project, you can keep track of what each person does through user profiles and the project log. If you need a bit more than this, memos can be a helpful channel of communication. Here are some examples:
A log that each user should update at the end of a stint, with the date, what they have done and any emerging ideas. This one is taken from the sample project that ships with NVivo 10:
Project structure memo
A record of how a particular element of the project has been set up – in this case, how the interview transcripts have been coded:
Notes and ideas
Memos are helpful to keep track of emerging ideas, comments, problems, strategies etc. These might be stand-alone memos or linked to individual project items, and you can group them together in a folder for easy access. See more on this in NVivo coding – using memos to keep track.
‘To do’ lists
Always useful for both team and individual projects, ‘to do’ lists speak for themselves (just remember to keep them updated!):
The above are just some ideas for using memos to keep all project users in harmony. Use any or all of them, or create your own, as suits your project.