That said, however, there are still some questions --
A) Are the Product Managers, Manual writers, those engaging with the Clients part of the Review?
B) Is this an internal product or an external one?
C) Are there a lot of bugs discovered on further testing?
Does the Dev Team feel they can do more? If it makes sense, it may be worth asking the rest of the team whether we can take on more (e.g. writing manuals), or adding some other members on the Dev team.
B) Both, our product are used by ourselves and by our clients.
C) Yes, our product is so big, complex and has questionable design choices that when you introduce a feature, somewhere else (can) break. Despite that the Development team is continuously improving themselves. Unit testing, pair programming and CI are subjects that will be introduce shortly.
And no the Development team is not capable in writing these functional manuals. Our Product Managers are hired and skilled to write these manuals.
I guess the big question is: what would you do if stories never gets completely approved during the Sprint Review. There are various (and in my opinion) valid reasons such as:
1) what the Development team built is still error-prone. Its not the fault of the current Development team but bad legacy coding.
2) software is for external usage so the manual needs to be created before launching it.
3) software is for external usage so clients needs to be notified.
4) what we usually hear from PO is that the Sprint Review is too short to do a good User Acceptance Testing.