I am not sure. I never found much value in companies internal confluence pages. Mostly outdated and poorly organized.
Long README for project setup is code smell. Things should "just work" with obvious commands. Best code documentation is automated tests.
I think the most important documentation should be your issue tracker. User stories should have clear AC, all work should be captured in tickets and organized in Epics/tags.
My big problem with agile is that the total amount of work done for a particular feature is not captured very well. This makes it hard to make strategic decisions. You might have multiple teams re-inventing the same wheel or facing similar problems.
Long README for project setup is code smell. Things should "just work" with obvious commands. Best code documentation is automated tests.
I think the most important documentation should be your issue tracker. User stories should have clear AC, all work should be captured in tickets and organized in Epics/tags. My big problem with agile is that the total amount of work done for a particular feature is not captured very well. This makes it hard to make strategic decisions. You might have multiple teams re-inventing the same wheel or facing similar problems.