Hi community
I am co-running a requirements workshop for quite a typical  intranet:  Home area and Departmental sites team.  I really want keep the meeting fairly business focussed ( so no HNSC discussions!)  and ensure we capture the key requirements, ahead of my build phase.
I am thinking it would be great to have a number of documents to present/edit, so to capture business focussed requirements
- A spreadsheet to cover site columns, content types and meta data – I have got my first pre-filled draft of this
- A requirements table to which references at  high level user story , id , intended audience and UI hints – is there a good example of  word/pp/excel template for this? #notreinventingthewheel
- User Story in detail
- Test scripts to accompany User story
- ???
- Site Topology Visio diagram – quite good stencils out there  as a starter
- potentially a bit of wireframe modelling tho I think this might be a bit too early for the team
Be interested to hear the thoughts of the community.
Daniel
I found myself facilitating discussion and taking notes for display on screen. This was very difficult and not entirely satisfactory. I hope you will have a good scribe.
Interstingly I found wire frame quite useful. The audience had web site experience and responded to the visual challenge of drawing on white board and A0 paper. From these balsamiq wire frames were sketched out and used to drill into SP functional IA to work out how to deliver what they wanted. This surfaced metadata, site columns, page layout, front page, articles, audiences, content type, search, etc. As audience did not know SP functionality they had to be led into understanding how SP can deliver static and dynamic content, and the controls (governance) required to put vision in place.
Mike B
