Quotes About Integration

You've helped me see that IT is not merely a department. Instead, it's pervasive, like electricity. It's a skill, like being able to read or do math.

Patty thinks for a moment, "It's strange. Even though we have so much data on projects, changes, and tickets, we've never organized and linked them all together this way before.

Without automated testing, continuous integration is the fastest way to get a big pile of junk that never compiles or runs correctly.

Imagine a world where product owners, Development, QA, IT Operations, and Infosec work together, not only to help each other, but also to ensure that the overall organization succeeds. By working toward a common goal, they enable the fast flow of planned work into production (e.g., performing tens, hundreds, or even thousands of code deploys per day), while achieving world-class stability, reliability, availability, and security.

You know, deployments are like final assembly in a manufacturing plant. Every flow of work goes through it, and you can't ship the product without it.

It is virtually impossible to make any business decision that doesn't result in at least one IT change.

Kanban boards are an ideal tool to create visibility, and visibility is a key component in properly recognizing and integrating Ops work into all the relevant value streams. When we do this well, we achieve market-oriented outcomes, regardless of how we've drawn our organization charts.

Instead of IT Operations doing manual work that comes from work tickets, it enables developer productivity through APIs and self-serviced platforms that create environments, test and deploy code, monitor and display production telemetry, and so forth.

Another benefit of having Development and Operations using a shared tool is a unified backlog, where everyone prioritizes improvement projects from a global perspective, selecting

They start making a list: Every developer uses a common build environment. Every developer is supported by a continuous build and integration system. Everyone can run their code in production-like environments. Automated test suites are built to replace manual testing, liberating QA people to do higher value work. Architecture is decoupled to liberate feature teams, so developers can deliver value independently. All the data that teams need is put in easily consumed APIs

To even get feedback from our integration process would require twenty-four to thirty-six hours.

This is the reality of operating complex systems; no single person can see the whole system and understand how all the pieces fit together.

we need to design our systems so that they are continually creating telemetry, widely

However, for decades we have ended up with silos of information, where Development only creates logging events that are interesting to developers, and Operations only monitors whether the environments are up or down. As

She looks around at the entire floor. Over a hundred developers are typing away, working on their little piece of the system on their laptops. Without constant feedback from a centralized build, integration, and test system, they really have no idea what will happen when all their work is merged with everyone else's.

Integration problems result in a significant amount of rework to get back into a deployable state, including conflicting changes that must be manually merged or merges that break our automated or manual tests, usually requiring multiple developers to successfully resolve.

should be as easy as writing one line of code to create a new metric that shows up in a common dashboard where everyone in the value stream can see it.

all team members as well as passers-by can see the latest information at a glance: count of automated tests, velocity, incident reports, continuous integration status, and so on. This

By doing this, Development and Operations may end up creating a shared work queue, instead of each silo using a different one (e.g., Development uses JIRA while Operations uses ServiceNow). A significant benefit of this is that when production incidents

Everyone around here thinks features are important, because they can see them in their app, on the web page, or in the API. But no one seems to realize how important the build process is. Developers cannot be productive without a great build, integration, and test process.

Then it hits me. The majority of our marketing projects can't be done without it. High touch marketing requires high tech. But if there's so many of us assigned to these Marketing projects, shouldn't they be coming to us?

Testing is done in scarce integration test environments, which often require weeks to obtain and configure. The

business project work as one.

Continuous Delivery.