Related Content
 |
4 DevOps Antipatterns to Avoid While lots of organizations are making good progress with DevOps, there are others that have fallen prey to common DevOps antipatterns. Signs usually include a slowdown or stopping of progress toward a fully collaborative organization operating at a high velocity. Here are four DevOps antipatterns to watch out for. |
|
 |
Building Security into DevOps: A Slack Takeover with Larry Maccherone Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Larry Maccherone, senior director at Comcast, hosted this Slack takeover and discussed what DevSecOps means, how to get started with security, and the changing role of security specialists. |
|
 |
How to Get Security Groups to Join Your DevSecOps Journey DevSecOps shifts security practices left and assures earlier that your application isn't vulnerable to breaches. But convincing a security group to get on board with your DevSecOps journey may not be an easy task. These four points can help you prove to your security group that DevSecOps is in everyone’s best interest. |
|
 |
Scrum Can Help You See the Forest and the Trees In project management, it's easy to focus on details to the extent that you lose track of the larger goal. Scrum can help you identify flaws and gaps, and skipping or trivializing Scrum events will just hide the fact that there are things you need to improve. Finding problems is something to be celebrated, not hidden. |
|
 |
Get Your Defect-Tracking Database Back on Track When defects are ignored or mismanaged, it can compromise the integrity of the defect-tracking database. When this happens, defects could go unfixed, or code fixes may not be verified by the production release. Before you can resolve a compromised defect-tracking database, you need to know how to recognize one. |
|
 |
Take Credit for Your Risk Management Activities If you have an important implementation date, early identification of the minimum viable product is a vital risk-management step that helps focus your team’s attention on what's important. Rather than apologizing for intelligent phasing of functionality to manage risk, explain it to stakeholders and take credit. |
|
 |
Is Everything Code? As modern software processes become automated, one might argue that nearly everything in software development is code. Obviously, our software applications are comprised of code, but that’s only the start of it. Our tests, delivery orchestration, and someday even our software production could be automated. |
|
 |
The Agile Culture You Need for Faster Pull Requests Is your process for pull requests compromising your team's agility? You can structure your changes in a way that facilitates more rapid feedback, but even then it is still possible to have a slow integration time if people don’t review pull requests promptly. Mechanics are part of it, but culture also matters. |
