In one of my projects, user surveys are about to complete and my next tasks are creating the personas and generating the user requirements document. Since this is one of my first UX projects, my proposal took a very by-the-book approach based mostly on A Project Guide to UX Design. That book mentions user requirements but doesn't really elaborate on how they should look.
In my former career in software development, I dealt with requirements that were written out very formally in CMMI style ("The system shall...") and with less formal, wiki-style functional technical specifications on agile projects. I'm wondering how to approach user requirements in this UX redesign project.
This client is an informal group, so I don't want to overwhelm them with information to the point where they will not read it.
So, several questions:
What categories of information do I need to spell out in a UX user requirements document? (Are any redesign-specific?)
If user surveys are calling for a feature that was not agreed on in the proposal, how should the user requirements address this?
Is there a free template for a UX user requirements document online?
Is there a book that spells out how to do user requirements? (I'd very much prefer an online template; it's free, and I can start the document sooner.)