Discussion Forum > Testing a new system or a tweak
I'm baffled. How could you possibly use two systems that do the same thing at the same time? That seems a recipe for both getting muddled. You can easily have two systems at once if they are complementary.
May 20, 2012 at 17:01 |
Alan Baljeu
Alan Baljeu
Alan,
probably thats the reason why asked that question ;-)
How do you make sure, that if you start to try a new system and completely turn the switch, that nothing gets lost - how can you trust the new system, if you start new without having an eye to the "old" system/stuff. Probably you miss some landmines which are lying in the field of the abandoned system. Otherwise you have to transfer all the stuff from the old system to the new one?!
Probably I don't see the trees for the forest :-(
probably thats the reason why asked that question ;-)
How do you make sure, that if you start to try a new system and completely turn the switch, that nothing gets lost - how can you trust the new system, if you start new without having an eye to the "old" system/stuff. Probably you miss some landmines which are lying in the field of the abandoned system. Otherwise you have to transfer all the stuff from the old system to the new one?!
Probably I don't see the trees for the forest :-(
May 22, 2012 at 10:22 |
Jens
Jens
It depends on the old system. Unless it requires a lot of time to "work the system", keep the old one around as a safety net, then update and review it daily? weekly? semi-weekly?
May 22, 2012 at 16:03 |
Cricket
Cricket
Whenever I've made a transition from one system to another, I would treat the old system like any other backlog: add it to my list of things to deal with, in the new system.
May 23, 2012 at 2:11 |
Seraphim
Seraphim
every once a while I feel the urge to test a tweak or -luckily very seldom- I want to try a completely new approach.
What I find is, that testing a new system or tweak while running parallel the current system has two side-effects:
a/ It throws obstacles into to the current system and makes it perform worse - so, the feeling that I need a new system/tweak grows (probably unnecessarily)
b/ the new system got interfered by the struggle to keep the current system running.
Tips for testing a new system/tweak while keeping the current system alive?
Or, is it recommended to give up the current system while testing - IMHO this could end in an untrustworthy system?