In recent projects I have been on with Readify, I have seen the rise of using OneNote to share most of the artifacts related to project. We still had requirement documents and proposals and all, and also tracking systems for ongoing and future work (backlog), but we used OneNote to record all sorts of information you’d store in a Wiki and/or in email and floating documents everywhere like:
- Induction information (why does the project exist? how to setup dev environment? etc.)
- Demo notes (what items are ready to demo? what are the steps? which users/links are needed?)
- Meeting notes (demo meetings, sprint retrospectives)
- Essential communication (Copies of release notes after sending, special notes coming in email / chat)
The availability of OneNote pretty much everywhere (including mobile devices, and web, as it’s hosted in out Office 365) and automatic synchronization made it a perfect alternative to a wiki for internal communication.
And yes, although I haven’t noticed this earlier, but OneNote also keeps track of all revisions and modifications, just like a proper wiki does.
If you want to learn more about how this approach worked for us in Readify, Tatham Oddie, one of our Readify Principal Consultants had an extensive writing of this model and other related communication strategies that help us excel at Readify.
Check it out: BEING AN OPEN RECIPIENT
Of course this is more applicable in situations where we do have more control over the way of communication. Not all projects follow this yet, and many projects work according to the established ways of our clients as long as they get the job done.
- - -
P.S. If you liked this post, please help me out by checking the ads on the site and clicking through the one you like. Also, I'm giving away a free newsletter for web developers that you can sign up for from here.