This is part 1 of a 3 part series.
There is no such thing as best practices. Two different teams approaching the same challenge might succeed with completely different approaches. What works well for one team may well be irrelevant for the other. What helped one team might be counter-productive for the other.
So think of the above paragraph as my disclaimer. With that out of the way, let’s proceed. ッ
Maintaining common or shared files that are used across multiple development efforts can be challenging. There are many ways to configure Dimensions CM to support this.
In this 3 part series, I will talk about the pros and cons of two different scenarios so that you can decide which approach to take. Remember that one size does not fit all; hence the reason why Dimensions CM is so adaptable and can support different processes.
At the end of each scenario, I will include how to configure Dimensions CM to support that particular scenario.
Before we get started, let’s cover some terminology and a few ground rules to avoid confusion.