Today most of the documentation to the project is kept in Confluence or Jira. These tools became de-facto industry standard for the requirements development and architecture description. But with the ease of use they bring denial of already known approaches verified previously in many requirements management tools. The result is the documentation which is often obsolete, rarely maintained and is useless. In this talk I'm going to discuss the problems which arise while using Confluence and Jira for requirements management and architecture documentation. In the end I will outline possible ways how to improve project documentation so that it will bring benefits for the team.
