Select a strategic toolset
Define a tools strategy based on five criteria
From the developerWorks archives
Date archived: December 16, 2016 | First published: February 04, 2014
Many organizations choose tools to automate aspects of the development and delivery process, based on a tactical, project-specific, need. This approach to tool selection is fraught with business challenges, such as the cost to maintain a disparate toolset; and technical challenges, such as the lack of integration between tools acquired in different parts of the organization. This article describes five key characteristics to consider when selecting a strategic toolset.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.