Whats the best practice for documentation in Jira and Confluence?

Markus_ct0073

I have seen many different approaches for documentation in Jira and Confluence and was wondering what the official recommendation is?

 

Things i've seen:

• Document everything related to a User Story within the User Story (Confluence is for Epic and above Documentation)
• Add only the most important documentation to the User Story, create the detailed documentation for each user Story inside of Confluence (so each US = one page)
• and the classic: "Dont document anything cause we are agil"...

Alex Koxaras -Relational-

Hi @Markus 

I dont think that there is such thing as an official documentation on best practices. There is however this article from Atlassian, in which you will see basic things. And another article here. Organizing information and content is part of Information Architecture, for which many books have been written. After a quick google search you can read a small guide here. But feel free to search for your own.

However about the last bullet "and the classic: "Dont document anything cause we are agile", this is completely wrong since the Agile manifesto states:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

 So this doesn't mean that if you are Agile, you don't document things. You do. But you give your priority in working software.