Visualizing your workflow is a key component of agile methods. But if we want to solve problems, we have to do a bit more than just visualize them with sticky notes. We have to perform some actual problem management. And to manage problems, a good start would be to measure them.
Continuing to manage highly complex IT environments in a reactive mode leaves IT specialists vulnerable, when really they need to understand the actual causes and effects of what’s happening among the many technologies in use across the enterprise. Instead of constantly fighting fires, IT operations teams should aim to prevent the fires from starting.
An enterprise release consists of individual releases, some independent and some dependent. If we think of an enterprise release as a song, then the individual releases can be thought of as the musical notes that make up the song. This article discusses problems associated with an enterprise release and ways in which these problems can be overcome, resulting in release harmony.
DevOps is a set of principles and practices that are effectively used to improve communication and collaboration between development and operations. But how exactly does one implement DevOps, and, more importantly, how do we scale DevOps to meet the needs of a larger enterprise application development? This article will help you get started with scaling DevOps.
Continuous delivery meshes well with agile development: Both facilitate the need to move quicker and deal with ever-changing requirements, delivering the best quality possible but usually with not enough resources. Agility is what is expected from technology companies and IT divisions. So, what does it take to have continuous delivery in your database?
Mistakes happen. But team members can engage in very dysfunctional behavior after they have made mistakes—often because their organizations punish mistakes and cause damage trying to cover them up. Here’s what we learn from positive psychology about creating an environment where employees can be empowered to address their mistakes in an open, honest manner.
Change management is a dynamic process that has to evolve with the changing needs of the business, organizational size, and project outcomes. This article addresses some challenges with change management and some tactics that can be used for choosing the right strategies for overcoming these challenges. The key is to stress the importance of keeping change management scalable and lean at every stage of the organizational improvement process.
David Lawton writes that with a few changes to capital project business processes and the implementation of a content management interoperability services (CMIS) database, operations content can be extracted directly from originating tools and populated into a data model that helps operations manage the lifecycle configuration. Consuming the project content during the project provides a vehicle to transform and feed subsequent processes.
Lean Six Sigma is a leadership methodology that significantly improves process quality, speed, costs, and agility. One of the concepts applied is called a pull system, and in this article Steven Bonacorsi explains how to design one for your process. Doing so will help you to stabilize a process flow into a predictable work control system.
Almost any description of a job involving software configuration management—or more generally, application lifecycle management—will include the words “best practices.” Kareen Kircher writes on how to make best practices a reality for your work. The five ingredients to making successful changes happen are relationship, timing, automation, pertinent documentation, and refining.