Related Content
 |
The Importance of Timing when Implementing Change Too many changes at once can prolong upheaval and delay people's adjustment to the new norm. If you are planning to start a complex project, introduce a new tool, or undertake any other major initiative, and employees are still reeling from other changes, it may be wise to delay the planned change if you can. |
|
 |
Container-Based Deployments and the Future of IT Operations Container-based deployments have become the preferred approach for managing the build and release of complex applications. Many of the tasks handled by IT operations today may not be necessary in the world of containers. Will Ops continue in its current role, or will it need to evolve with the new challenges? |
|
 |
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |
|
 |
A Strange Story of Version Control and Software Customization As he was doing an inventory of a company’s commercial software and version control, Payson Hall got an odd response from a vendor: Their software has no versions. Each client has a unique, customized edition of the software. How can the vendor possibly support that many products? How would that work? |
|
 |
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |
|
 |
DevOps or NoOps: Can You Have Too Much Automation? Some DevOps thought leaders have been promoting “NoOps,” which is the notion that IT resources can be provisioned in a fully automated way that does not require operations engineers to manage. There have been notable successes with this approach, but also some challenges. Can you have too much automation? |
|
 |
The Importance of Agile Source Code Management If agile teams do not effectively utilize source code management, they can miss out on key benefits and sometimes even lose essential source code used for application deployment. But done well, a source code management solution can provide the best platform for effective agile practices. Bob Aiello explains. |
|
 |
Reliability Is Possible with Environment Management To have completely reliable systems, we must have effective IT controls in place that help to identify risks before they turn into incidents. Change management meetings are very helpful for coordination. Effective environment management and change control can keep your systems reliable and secure. |
