|
Who Needs Standards, Anyway? Many CM experts are familiar with the guidance found in the IEEE, ISO, and ANSI/EIA industry standards. But if you want to really accelerate your agile development, it is wise to learn what is involved with implementing such industry standards. Bob Aiello explains the different types of standards and how organizations go about creating them.
|
|
|
Critical Questions to Ask When Choosing a Third-Party API This article exposes the risks and hidden costs involved in the seemingly innocent decision of which third-party APIs to use to gather and report data, offload critical functionality, and save implementation time. It addresses some typical reasons the decision-making process over third-party use is overlooked, as well as how to make good choices confidently and consistently.
|
|
|
Go Bimodal in Your Enterprise: Stop Shaving the Yak! Going bimodal refers to an enterprise supporting two modes of operation: the first, the stable mode, is the secure, robust, reliable one you already know. The second, the agile mode, is a fast path that exists alongside the first and allows you to get results done quickly and without much fuss while not compromising the integrity of your IT.
|
|
|
Simplifying Your Software Code Audit Software code audits can be arduous and time-consuming, as today’s software projects use a mix of proprietary, commercial, and open source software. This article outlines a number of methods to simplify and streamline your audit process and understand the best practices in organizing, documenting, labeling, tracking, and managing open source and third-party content brought into software portfolios.
|
|
|
The Lost Art of Change Control Change control exists to review and approve important modifications, but done wrong, you chance confusion, chaos, failures, and outages. Poorly run change control wastes everyone’s time, but far worse is the missed opportunity to assess and manage risk. Here, Bob Aiello gets you up to speed on the lost art of change control.
|
|
|
DevOps: The Pathway to Stellar Digital and Business Results DevOps is the key to unifying technology with business results. Customers abandon apps and sites if their expectations are not met almost instantly, so issues must be resolved earlier in the pipeline before end-users are impacted. This article highlights the need for adopting a DevOps culture and some best practices for doing so.
|
|
|
Convention over Configuration: Replace Scripting with New Build Names Bernie Zelitch writes that his company’s build system scales well because early on, they scrutinized their build naming convention, saw its implications to the build ecosystem, and made radical changes. Their new naming convention takes some getting used to, but once it was fully adopted, it improved economy, flexibility, and functionality.
|
|
|
How Enterprise Configuration Management Architecture Fits with DevOps When it comes to DevOps, the fundamentals of CM may be forgotten (erroneously) by some practitioners. DevOps tools can be strategic assets, but they are not as important as established CM standards and process. It's up to us as practitioners to ensure that the DevOps tool chain implementation supports the corporate CM policy.
|
|
|
Harnessing the Collective Unconscious to Understand Organizational Culture Process improvement requires that we understand and influence human behavior by helping people improve the way in which they perform their work. By understanding the organization's collective unconscious, you will be more capable of designing effective process improvement strategies that are aligned with the corporate culture.
|
|
|
Where Did Configuration Management Go? Amid all the excitement of DevOps, continuous delivery, and the magic of single-push-button deploys, some folks have forgotten the prerequisites. You cannot implement continuous anything without effective configuration management. This article will help you reassess where you are and ensure that you have the basic building blocks in place to ensure success.
|
|