Minimum-documentation is one of the basic features of agile development (intuitive GUI, visually rich documentation, automated tests replaces it). But usually software development goes hand in hand with the development/reengineering of business processes and (in opposite to agile software development) the introduction and the implementation of the business processes require detailed and throughout documentation. That being said - can software developers expect that business processes that are mentioned in the user stories are well-documented and that the business documentation for business processes can be used more or less directly in the design and development phase?
I have sad experience that sometimes there is little rethinking and little documentation of the business processes themselves and that makes development and maintenance of software quite hard. Sometimes it happens that the definition of business processes occurs at the same time when the requirements for software are defined. It is quite strange. Because business processes should be defined at the higher level of the chain of management.