Question:
Hi,
I'm wondering how this operates in other companies:
Most have Dev - Test - Production setup.
Say a program is changed in Dev and moved into Test: what is stopping someone else from changing the same program in Dev a later stage (while the first change is still in Test) and moving it into Test? If the second change gets confirmed in Test quicker then the first change, then the program gets moved into Production, however the first change is now copied into Production as well.
I'm wondering what transport policies companies have designed for this kind of scenario? Thanks.
Answer:
This is an "overtaking" transport. You have to put controls in place, possibly electronic, possibly paper based, to ensure that transports are imported in the same order as they are released. You will always have exceptions to this rule, but then they face the risk of the scenario you describe.
One product that deals effectively with this issue (though it introduces others) is polylogic - which despite having a rather amateurish website is rather a neat solution. http://www.polylogic.ch/
And no, I have no financial interest in it whatsoever.
m@t
_________________
TULY The quality of answers is roughly proportional to the quality of the question.
The downside of being better than everyone else is that people tend to assume you're pretentious.
Answer:
Thanks m@t.
I see another similar product http://www.skywiresoftware.com/ to the one you mentioned. And I don't have any financial interest in it either!
I'm still interested in other companies specific attempts at controlling this process...
Thanks.