Continuous delivery of software-driven innovation

Principle #4

The whole system shapes the goals.

IBM DevOps emphasizes the collaborative performance of the system as a whole, rather than the performance and output of individual contributors or teams.

In a traditional workflow, requirements are identified (by business teams), built (by development and test teams), and passed to IT operations for deployment and delivery to the user. Each team functions in its own silo, often with different tools and internally competing goals. Business teams want solutions that are profitable (control costs); development and test teams want solutions that address as many new features and defects as possible (maximize change); IT operations teams want solutions that are stable, secure, and non-disruptive (minimize change).

In a DevOps workflow, business teams engage often and early with customers to continually shape and reshape the requirements. Development and test teams work collaboratively with operations teams and use shared goals and processes to build solutions that are stable and easy for IT operations to deliver and maintain. For example, delivery tasks are tracked in one place, continuous integration and official builds are unified, and the same deployment tool is used for all development and test environments, so that any errors are detected and fixed early.

The whole system contributes to rapid and successful deliveries. In a DevOps workflow, the quality, or business value, of a solution is continually enhanced as each team contributes to it.

Continuous integration is more than just successful merges of your code base, demonstrates Maciej Zawadzki, IBM Director of Deploy and Release products | 4:44

Video: title

Develop, test, refine, repeat. Smile.

Mobile Quality Assurance: Application testing in the cloud.