Deliverables is NOT the first thing you should worry about

When I talk to governance people about Agile, the first questions they have are typically about deliverables, and specifically documents.  If you're unwary, this is where you might get drawn into a "Does Agile mean no documentation?" "No it doesn't" debate which mostly misses the point.

The issue is not about what deliverables method X has vs method Y.  The issue is how one should think about methods.

If you want to understand a process, the priority is:

1. Outcome
2. Activities and how people interact
3. Artefacts and outputs

The problem I have is not so much about what deliverable your Agile process should have or not.  The problem I have is that you started the discussion with the lowest priority issue (artefacts and outputs) rather than the highest priority issue (outcomes).