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
Before the wireframes, at the initial workshop for UI design of SP pages, I used colored post-it notes that I stick on the white board so the audience can see high-level hierarchies or to illustrate use of Promoted Links. We aim for clean, visually appealing landing pages. Not recommended for detailed site page discussions for lists, libraries, etc.
