Tool Transitions In A CI Environment

From CitconWiki
Jump to navigationJump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Example subtext: Transitioning ClearCase as a tool to Git

Why is there resistance to change?

  • Management might resist change in general
  • Software vendors don't want to loose license sales
  • Migration of data might be difficult, impossible, or costly
  • Migration of work-methods/procedures might also be difficult
  • Requires some prioritization/negotiation with other required work
    • Delay of releases not be tenable.
  • Might require man-hours of research of new tools or new versions
  • Migration from old tool to new tool requires coexistence of two tools
    • New stuff uses new tool, old stuff uses old tool

What are some solutions to this resistance?

Why do we need change at all?

Retrieved from "http://citconf.com/wiki/index.php?title=Tool_Transitions_In_A_CI_Environment&oldid=7258"