Articles

Hand holding black rotary telephone 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.

Matthew Heusser's picture Matthew Heusser
Racecar on a track Test Faster: How We Cut Our Test Cycle Time in Half

In just a year, one test team reduced its test cycle by more than 50 percent. It took analysis, planning, and effort—first they looked into how they spent their time, and then they questioned whether they could reduce time in any of those areas. Once they knew where they could be more efficient, they could start tackling their blockers. Here's how you can, too.

John Ruberto's picture John Ruberto
Identical bugs under a magnifying glass When Testers Should Consider a Bug a Duplicate

When can a bug report be considered redundant because it is already reported in the bug management system? If you ask the developers, if two bugs are caused by the same mistake in the code, it’s enough to report one of them. But Michael Stahl has good arguments from a tester's perspective about why it's better to err on the side of over-reporting bugs.

Michael Stahl's picture Michael Stahl
Requirements model Requirements Mapping Using Business Function Test Suites

On this team, testers were overcommitted, avoidable defects were surfacing, and documentation was hard to find. Worse, trust and morale were low. Upgrading tools was out of the question, so the testers decided to take matters into their own hands and create incremental change themselves. Here's how a team added a new type of traceability to its requirement test case world.

Balazs Schaffhauser's picture Balazs Schaffhauser

Better Software Magazine Articles

Using Agile and DevOps to Achieve Quality by Design 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.

Michael Sowers's picture Michael Sowers
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.

Miiro Juuso's picture Miiro Juuso
handstand 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.

Paul McMahon's picture Paul McMahon
Reshaping Agile Transformation 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.

Jason Little's picture Jason Little

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.

Jennifer Bonine's picture Jennifer Bonine
Why Manual Testers Shouldn't Fear Automation: An Interview with Chris Loder
Video

In this interview, Chris Loder, automation architect at InGenius Software, addresses the misconception that the goal of automation is to replace manual testers.

Jennifer Bonine's picture Jennifer Bonine
Geoff Meyer Analytics, Data, and How Testing Is like Baseball: An Interview with Geoff Meyer
Video

In this interview, Geoff Meyer, a test architect in the Dell EMC infrastructure solutions group, explains how test teams can succeed by emulating sports teams in how they collect and interpret data. Geoff explains how analytics can better prepare you for the changing nature of software.

Jennifer Bonine's picture Jennifer Bonine
Tanya Kravstov 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.

Josiah Renaudin's picture Josiah Renaudin

Conference Presentations

Agile DevOps East You Can't Improve What You Can't See
Slideshow

From value stream mapping to burndown charts, making things visible is a core component of the continuous improvement process. But even with all this visibility, much of the data surrounding how your teams work is either not captured or not understandable. This data represents a great opportunity for insights and improvement. Think about it: Your management team tells you that your velocity is too low. What do you do? First, you need more information. What does “too low” mean? Why was the velocity low? Did the team deliver value? Brandon Carlson will share one team’s surprising insights when they analyzed previously invisible data. He'll also tell you how to discover what the highest risk areas of the system are for enabling the most cost-effective regression test strategy. It's all there, only tucked away where no one can see.

Brandon Carlson
Agile Dev West 2018, Better Software West 2018, DevOps West 2018 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
Better Software West 2018, Agile Dev West 2018, DevOps West 2018 Innovation: The Art of Being Wrong
Slideshow

[video:https://youtu.be/S_fDFUC4ISY width:300 height:200 align:right]

Stefana Saxton
STAREAST 2018 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

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.