DevOps
Articles
How to Guarantee Failure in Your Agile DevOps Transformation Many organizations make the same agile and DevOps scaling mistakes year after year, then attempt to rectify them by putting together a great new strategy—only to miss the reasons causing the failure. If you want to refuse to evolve and, as a result, cause your organization’s agile and DevOps transformation efforts to deliver zero business value, be sure to follow these seven antipatterns. |
||
Create an Agile DevOps Environment That Fosters Flexibility over Features When a company makes the move from software as a service (SaaS) to an API-first platform, a change in mindset is required. The successful transitions come from those who shift from features to flexibility. Technology teams should look to remove constraints and broaden the possibilities of their platform by constantly exploring ways to make their platform as flexible as possible. |
||
When Postmortems Meet Retrospectives: Improving Your Agile Process If you want secure, reliable systems, you need all stakeholders actively communicating. This means involving both IT operations and developers in discussions after deployments, to ascertain if anything went wrong and can be avoided, and what went well or could be refined. Integrating your postmortems and retrospectives facilitates collaboration and improves processes. |
||
Business and Development: Working Together to Build Better Products Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand. |
||
Use Lean Thinking to Accelerate DevOps Performance for Agile Teams Leaders in agile organizations should consider adding lean techniques to their DevOps practices. Lean thinking can accelerate DevOps delivery by providing a set of processes and principles to help create more beneficial products, save money, boost productivity, reduce waste, and map to value. |
||
Revitalize Your Retrospectives with Gamification Agile and DevOps teams, which emphasize continuous improvement, can benefit greatly from effective retrospectives. However, retrospectives can get monotonous, and that’s when they become ineffective. Using gamification in your retrospectives brings a completely different dimension of thinking—and even makes the process fun. |
||
Common Misconceptions about Agile: Agile Is Just a Project Management Framework When it comes to transitioning to agile, if a team only goes off what it's heard from other teams and doesn't take a class or read any books about the process, misconceptions can abound. And that leads to problems. Read on to have three common agile myths debunked and to learn why agile is a cultural change, not just a project management framework. |
||
Using Containers for Continuous Deployment Pini Reznik explains how containers can help shorten the software development feedback loop by drastically reducing the overhead involved in deploying new software environments. This leads to faster build and test executions and simplifies the standardization of the development and production environments, allowing for an easier transition to continuous deployment. |
||
Streamlining Build Processes and Configuration Management for Truly Agile Organizations Technology-driven companies, regardless of size and scale, are facing the increasing need to ship better code faster while meeting business requirements. This requires collaboration and interaction among the traditional information technology infrastructure library (ITIL), information technology service management (ITSM), and development teams for a truly agile organization to emerge. |
||
Introducing the DevOps Database Gap Yaniv Yehuda details how DevOps is a natural evolution within the software industry as it drives business value and enables the organization. This article will describe how database management and the database administrators need to be part of any comprehensive DevOps approach. |