Articles
 |
When DevOps Gets Lost in Translation The waterfall method of developing software is a bunch of translation activities: The design is a translation of the requirements into the language of architecture, the code is another, and a formal test process is a third. And with each translation, there’s the opportunity to introduce error. When your DevOps team is isolated, it creates another handoff, and another point of failure. |
|
 |
Rowing in the Same Direction: Use Value Streams to Align Work Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together. |
|
 |
Why You Need to Be Doing Continuous Integration It’s usually easy and inexpensive to set up a continuous integration environment for either an agile or a waterfall project. Perhaps the most obvious benefit of CI is the elimination of the integration phase that existed in traditional waterfall projects, where we typically slip the worst on deadlines. But there are many other benefits to continuous integration that you may not have considered. |
|
 |
DevSecOps: Incorporate Security into DevOps to Reduce Software Risk DevSecOps is a growing movement to incorporate security into DevOps practices in order to ensure flaws and weaknesses are exposed early on through monitoring, assessment, and analysis, so remediation can be implemented far earlier than traditional efforts. By failing fast with security testing, organizations reduce risk of a security incident and decrease the cost of rework. |
Better Software Magazine Articles
 |
Using Agile and DevOps to Achieve Quality by Design When software nears completion, it is the wrong time to focus on quality. Product delivery improves if you invest in a plan, validate in small increments, and focus on continuous testing. |
|
 |
Building Autonomous DevOps Capability in Delivery Teams After setting up a DevOps team and adopting continuous delivery practices, product releases may not be as smooth as they could be. The missing ingredient requires empowerment and autonomy. |
|
 |
The Power of Thinking Upside Down Software developers can become bogged down trying to keep up with agile process and procedures. Get better results by rethinking your approach to balancing focus, agility, management, and testing. |
|
 |
Reshaping Our View of Agile Transformation Transforming a software development team to agile may not go as planned. The real change requires a phased approach to earn agile acceptance. That mindset must extend beyond the team to the entire organization. |
Interviews
 |
Finding Microefficiencies in Agile Practices: An Interview with Melissa Tondi Melissa Tondi discusses retuning your standard agile practices to better engage the project team, enabling them to write code that will pass testing and free testers to assume the role of user advocate. |
|
 |
Identify Bottlenecks in Your Agile and DevOps Processes: An Interview with Tanya Kravtsov In this interview, Tanya Kravtsov, a director of QA at Audible, explains why identifying bottlenecks is so critical when you’re turning to agile and DevOps, as well as how automating manual processes can lead to better quality. |
|
 |
Accelerate Testing and Development with Continuous Delivery: An Interview with Naga Jayadev
Video
In this interview, Naga Jayadev of CA Technologies digs into continuous delivery, continuous testing, DevOps, and virtualization. He explains what he does at CA Technologies, the trends when it comes to testing, and the value of velocity within your development lifecycle. |
|
 |
DevOps: Find Solutions, Not More Defects: STARWEST 2015 Interview with Andreas Grabner
Video
In this interview, TechWell speaks with Andreas Grabner, a performance engineer who has been working in this field for the past fifteen years. At STARWEST 2015, he presented DevOps: Find Solutions, Not More Defects. |
Conference Presentations
 |
Unlocking Retrospectives
Slideshow
Retrospectives empower teams to learn and improve. But many teams fail to reach their true learning potential. Ryan was part of a team that held retrospectives for a year and a half to fix one line of code. Through the story of this team, he will show you how they turned their retrospectives from a meeting with meaningless action items to one that accomplished a meaningful improvement. Ryan will explore the resistance that was met and how it was overcome. He will show how to shift to a hypothesis-driven retrospective that to guides specific improvements and learning goals. His team made significant changes to their retrospectives and were rewarded with a radical improvement. Breaking through their retrospective impediments and finally embracing a learning mindset empower Ryan's team to fix the legacy line of code that had held the team back for over year. |
Ryan Latta
|
 |
Innovation: The Art of Being Wrong
Slideshow
[video:https://youtu.be/S_fDFUC4ISY width:300 height:200 align:right] |
Stefana Saxton
|
 |
Migrating from Test Cases to Real-World Telemetry Measures
Slideshow
Ken Johnston sees today’s software ecosystem in the light of Everything as a Service (EaaS). Operating systems like Windows, Android, and Chrome OS all ship regularly like a service. Browsers automatically update every few weeks, and apps are constantly updating through all the app stores. Although getting a test to pass once and signing off has gone by the wayside for software testing, still we run test cases over and over again. Ken shares how Microsoft took millions of test cases—yes, actually millions—and turned the important ones into measures based on real world telemetry. Massive amounts of data coming in from real devices and real users measure product quality and tie it to key customer satisfaction metrics. |
Ken Johnston
|
 |
Enough about Process, Let’s Use Patterns
Slideshow
When new developers and testers join the company, we want them to learn the “way we do software here.” So we give them the “stone tablets”―the volumes of process documentation― to study. However, the problem is that the details in this documentation are primarily for beginners and don’t... |
Paul E. McMahon, PEM Systems
|
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.