Even though jumping onto the agile bandwagon is tempting for businesses, it is not always easy, and a transition to agile is likely to come with a slew of challenges for testing in particular. In order for agile to enable delivery of quality products at speed, testing has to begin much earlier in the process than ever before. Enabling certain practices will help your organization achieve a more successful transition to agile testing.
Testers and developers often have a strained relationship. Each side has a certain level of expectations as to what the other side should know and do, while there is little understanding of the constraints, conditions, and requirements that the other team has to work within. But it does not have to be this way. A little effort in giving more specific and helpful feedback can go a long way toward improving attitudes.
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.
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.
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.
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.
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.
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.
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.
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.
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.