In most enterprises, individual teams may have open source or home grown build systems in place or use point tools for testing and other tasks, but they are isolated, disconnected and not accessible to other groups. This creates a costly environment where assets and procedures must be duplicated across multiple groups and where development managers and IT operations must support multiple, disconnected groups.
 |
 |
Support multiple teams, working in multiple locations, and programming in multiple languages with a single system |
 |
 |
 |
Enable sharing of assets and reusable procedures which eliminates duplicate work and makes it possible to deploy cross-company standards |
 |
 |
 |
Dynamically provision either physical or virtual resources to consolidate machines and reduce costs |
 |
 |
 |
 |
 |
 |
| |
| Disconnected build and release processes across teams |
 |
 |
 |
Redundant work, inability to enforce corporate standards |
 |
 |
 |
Enterprise-class production automation system allows multiple teams to leverage a single system and provide libraries of standard procedures |
|
| Geographically distributed teams |
 |
 |
 |
Costly to maintain multiple software production infrastructures |
 |
 |
 |
Remote teams can leverage a single system while project mechanism keeps each team's assets secure and distinct |
|
| Manually configured and maintained resources for software production |
 |
 |
 |
Expensive to continually re-configure hardware to meet testing needs |
 |
 |
 |
Dynamically provision teams with physical or virtual machines with no manual intervention |
|