Related Content
 |
Why Frequently Delivering Working Software Is Crucial to Agile While completing documentation is often an indication that some progress has been made, until software has been implemented, tested, and approved by a customer, the amount of progress cannot be measured. Here are some common reasons agile teams fail to frequently deliver working software—and how to avoid them. |
|
 |
Measuring Objective Continuous Improvement in DevOps When you're beginning your DevOps journey, it is incredibly important to know where you are starting. You will want to know later on what progress you have made, and you won’t be able to figure that out unless you have benchmarks from the beginning. Here are six steps to objectively measure your continuous improvement. |
|
 |
A Lean, Flexible Measurement Dashboard for Agile and DevOps If you’re moving from a more traditional software development approach to agile and DevOps, or if you’re struggling with implementing metrics, consider reviewing, revising, and refining your measurements. Leave those that add no value behind and look at a monitoring system that has these five essential categories. |
|
 |
DevOps and Test Automation: You Missed a Spot The key success factor for DevOps is the commitment from teams, managers, and other stakeholders. There should be agreement that tests and their automation can be important re-usable products, which need attention and cooperation to be able to support approaches like DevOps effectively. |
|
 |
What’s in the Fall 2017 Issue of Better Software Magazine Better Software magazine editor Ken Whitaker highlights content from the latest issue, including articles on bridging the divide between agile and waterfall, scaling agile through empowered teams, DevOps and IoT, and continuous development. |
|
 |
Performance Testing for Our Modern, DevOps World As DevOps-based methodologies are more broadly adopted, we'll increasingly move to a continuous testing model. Containerized environments and microservices make it easier to optimize your application by validating changes to the environment or system configuration, allowing you to deliver better products faster. |
|
 |
Use Continuous Backlog Grooming to Refine Agile Requirements Continuous backlog grooming means systematically refining your user stories: breaking up larger stories, obtaining detailed requirements, writing the requirements in terms of acceptance criteria and acceptance tests, and sharing and refining these details with the team. Acceptance test-driven development can help. |
|
 |
DevSecOps Could Have Prevented the Equifax Breach The Equifax cyber security breach compromised millions of people's confidential information. If you’re worried about how you can prevent an IT disaster of this scale at your own organization, there is an answer: DevSecOps, which incorporates security into DevOps practices to ensure weaknesses are exposed early on. |
