|
Fixing a Broken Deployment Process When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.
|
|
|
DevOps: Collaboration with a Purpose Development, operations, and QA have long recognized the importance of coexistence, but they've still had weak or unbalanced relationships. DevOps emphasizes collaboration, rejecting the "us versus them" mentality. Every department needs information, feedback, and support from every other department, helping everyone see how they enable each other.
|
|
|
You Can’t Buy DevOps There are organizations that want to “buy DevOps,” like it is a plugin to add to the development process. They often create a new role, team, department, or infrastructure. But you can't buy DevOps, and it's not a designated team, either. It is the idea of people working together. Here are some approaches to get you there.
|
|
|
Use Version Control to Unlock Your Development Velocity Effective source code management provides a basis for every essential development best practice, including continuous integration and continuous delivery. The key is realizing just how much valuable metadata is being created in your source code management system and establishing the tools and procedures to make this information available.
|
|
|
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.
|
|
|
The Risks and Rewards of Adopting a Microservices Architecture in Your DevOps Enterprise Adopting microservices can be a great way to split up existing monolithic legacy applications in order to gain some flexibility and accelerate the development of new features. But the learning curve is steep, and you may need to make some sacrifices. Andrew Phillips outlines the potential impact this implementation can have on architecture and operations in an enterprise environment.
|
|
|
Testers: An Integral Part of the DevOps Team Building innovative software faster and better is imperative to an organization’s success, so it makes sense to take advantage of DevOps. But what some teams fail to consider is that testing is a crucial part of the process. Without a “test early and often” mentality, DevOps would only be able to release software faster—not better.
|
|
|
Visualizing the Complex Software Development Process Software development is an elaborate process, so many organizations follow defined procedures. But it can be difficult to keep track of every step. It is often helpful to try to visualize the complex processes involved; seeing them outlined can help you understand what needs to be completed and how to manage the overall effort.
|
|
|
6 Traits to Seek in an Outsourced Product Development Partner Lower costs, specialized designers, and rare skills sets are among the reasons companies consider working with outsourced product developers. But there are differences between working with these vendors versus the traditional enterprise software solution vendors you may be used to. Here are six qualities to look for when making your selection.
|
|