title: Best practices for a microstrategy workflow
body: <p>we are a team of 5 people working with microstrategy. We share every role, but we have no worklfow.</p>
  
  <p>Everybody may build or change attributes and change the schema. This leads often to reports not working. Furthermore, there is no "good" documentation. We tried to establish a documentation with sharepoint, but there we also had no workflow.</p>
  
  <p>Originally, we had an old project where for every report all the attributes where constructed newly. So we did not reuse any existing schema object.</p>
  
  <p>Hence, we started a new project. We realized that due to lack of understanding and lack of workflow we make and made a lot of mistakes. We feel that we understand things better slowly (parent child), but the workflow is still horrible.</p>
  
  <p>We have a development project and a lice project, but with the way we are working now, we have a lot of problems. Particularly, the missing version control system is killing us. We perform changes and forget what we did. Hence, we have to use backups, destroying useful work on a given day</p>
  
  <p>So what are best practices to:
   * deploy new attributes, facts and reports
   * ensure that old reports work after constructing new attributes and facts
   * improve documentation
   * attributes defined on fact tables and parent-child relationships</p>
  
  <p>Any help is appreciated</p>