Versionning is always tricky in organisations and this is true for a lot of different environment. You can either be in sales, logistics, engineering, maintenance, HR,etc. There is also an issue with versionning. And it is strange because best practices have been discussed a lot, but it is sometimes hard for people to have a common way to think about versionning. I was recently discussing with a colleague with whom we are working on a new interface where the versionning is to be shown and available to the user. And as he comes more from a software development environement and I’ve been 100% in PLM without to much including source code management, we realized we had a different feeling about versionning.
Difference of intentions
It is funny, because I hear more and more leads and customers talking about intentions when they want to describe a software and that was exactly my feeling when we stumbled upon this difference on how we thought about versionning.
- For the software development oriented person, versionning means saving or tagging. It means that the actual work has to be saved because we want to keep a state of the actual work. “I want to keep a state, I make a version, this version is stored”
- In my view, related to main PLM concepts, versionning is creating something new. “I want to start a new work or I want to change a document, I version it. my new version is my working copy”.
The difference is not that big, but the difference of intention in the term “versionning” is surprisingly quite important.
We realized that it could be just a matter of interface because the backend can have the same logic. The issue is that we were on a software which would be used by users from different departments and with different experiences but where we couldn’t have two interfaces. So it needed some discussions to make sure we understood the same concepts and we would make compromise to use one single software interface on that product.
What is your “version” of “versionning” ?