Tool Transitions In A CI Environment

From CitconWiki
Revision as of 10:56, 25 April 2009 by Macetw (Talk | contribs) (New page: 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 licen...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

What are some solutions to this resistance?

Why do we need change at all?