I happened upon an overview of how the OneNote team uses OneNote for collaboration (thanks to the ever informative Daniel Escapa) which I thought you’d all enjoy.
The question is how does the OneNote team use OneNote for collaboration and in particular spec reviews? As a PM it is our job to come up with the feature specifications for a given feature and create a document outlining what the feature will look like, behave like, what scenarios the feature will fulfill and what goals we are going to accomplish. To start the spec we use a template, in Office we have a standard Word template we use for all Office specs. This template has sections pre-populated and also has custom fields which tie into SharePoint which is pretty slick. I start by creating a new spec in SharePoint which launches Word and enter all of the metadata in Word and then I go and write my spec.
Once I have completed the spec I will save it back up to the spec library and send an email to the team saying that the spec is ready for review. This email is a call to arms for people on the team to read the spec and give me feedback. This is where OneNote comes into play! We have a team shared notebook stored up on SharePoint and we have a section called “Spec Discussion” and in this section we have a page for each spec/feature we are working on. We have organized this section by using subpages; the top-level pages are titled with the name of a PM and under that page we create a subpage for each spec/feature written by that PM.
Each page uses a template that we use for feedback, the template pretty much looks like this:
Then each individual will go in there and enter their comments and questions, usually we add a new table row for each comment even if it is by the same person. I have also seen people print the spec to OneNote, write their comments with their Tablet pen and then copy the page to the shared notebook; but 90% of the time people just write their comments in this table. This way we have a running list of what comments people have and it isn’t in email or just hallway conversations.
Then as the PM it is my job to go through those comments and see what questions people have. At this point I will typically look through the list and see if I need to update the spec and I also will reply with my own comments. I write my comments inline and the resulting page looks like this:
Then I typically email the people who gave me comments and let them know that I replied, just so they can see that I listened to them and their feedback was incorporated into the spec. Then we do the final review where the PM (and the Dev & Tester) present the spec to the managers of the team to make sure this is a good plan and get approval before coding begins. Also during the review someone will take notes in this same spec discussion page so the notes from the meeting are recorded and stored in the same place. It also gives the PM a good place to go when they are done with the review and they want to look through all of the feedback and update the spec for coding begins.
We have also learned to insert links to the spec discussion page to the Word doc (the spec) so you can always get the right place. This system has worked well and allowed me to review spec offline and when I come back they all sync up, no write locks and everything is in one place and everyone on the team can see the feedback and the PM’s comments back to the commenter.