We don't eliminate documentation completely. My ideal thing would be to have the user on the team at my team meeting, because there I have all the cross-functional components. I have operational people and developers and all the people I need to create the solution. Then we sit around and ask if the system that we built last week works. They're either ecstatic or they're not. We get that feedback and then we build some more.
I think whenever possible it's an absolutely mandatory requirement for agile that you have strong interface with the user or the payer of the system, the person who's buying or using it. They have to be on the team and engaged, and I think government can do that.