DEV> Test, and DEV>Prod is more flexible; it allows multiple Test models, and Test models to be created and deleted without compromising Prod. It also supports segregation of duties Best Practice arti…
Master Dashboards will delete any personal dashboards. Techniques to minimize user disruption include creating a copy and have a migration process to move users to the new dashboards Related to Rule: …
After a revision, create multiple revision tags with different switchover dates prior to starting new development Best Practice article: Managing Frequent Structural Changes During Development
This is a technique that reverts the model to a previous revision, allows you to make a fix, sync to Production, and then return Development back to where it was Best Practice article: Saving incomple…
Test models should be treated as Production Models. This gives a true representation of testing and also prevents inadvertent synchronises from Test to Prod Best Practice article: ALM Explained—Part 2…
