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
You’re welcome…regarding what I mentioned about using post-it notes, you’ll probably hear this first from me…there’s a cool new tool called “Span” from Nureva on online ideation. Check it out here: http://www.nureva.com/span-ideation-system
Just realized this is an old posting (2013). Not sure why this is on Top Content listing. The question still has relevance as this is a process question. Your requirements workshop is part of a Business Analysis process. To guide you, I recommend getting a template for a Business Requirements document both high-level and detailed types. Not sure how much time you have for your workshop, your audience SP experience, and your scope for this SP project, but looks like you may not have enough time. You might want to schedule the high-level requirements first then another workshop for the details.
I found this BRD sample from Slideshare (this could be high-level then you can create the detailed version that includes the User Stories/Use Cases mapped to the requirements):http://www.slideshare.net/joshuaflewelling/Smartbox-IT-Solutions-Bu… You can add the wireframes and Excel sheets as Appendices. Hope you get signoffs on these (part of the process).
Here’s a link to User Stories/Use Case resources: http://www.slideshare.net/search/slideshow?searchfrom=header&q=…
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.
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
