By Mark Schettenhelm
Yes, your current implementation is complex and you’ve probably invested thousands or millions of dollars and hours getting it to work. But this is not a reason to stay with it, it is more a reason to change.
In his 2016 report “Avoiding the Sunk Cost Fallacy in the Mainframe Shop,” Jason Bloomberg of Intellyx writes that too many mainframe shops “are loathe to make a change” from tools they’ve invested years and dollars in, even if they’re inadequate for this day and age.
“Such thinking, however, is fallacious—and making the mistake of basing a decision on a sunk cost can be very expensive for your organization,” Bloomberg writes.
Without realizing it, you have bent your build processes to fit within the limitations of your current SCM tool. But it doesn’t have to be this way. A migration effort gives you the chance to implement SCM that will support your development needs, not work against them.
Read the entire article at http://insidetechtalk.com/waterfall-agile-scm-conversion/