With the traditional waterfall method of testing, achieving quality and faster time to market is difficult. Agile testing has emerged as an alternative, where development and testing take place simultaneously instead of operating in their respective silos. Let’s look at what it means to perform agile testing, what practices are necessary, and how agile testing can benefit your software releases.
There is a lot of interest in organizations around a transformation to agility. However, the focus is usually on agile development, so it may not be clear how software testing is done in agile. If you're responsible for leading your testing teams, don't let them be left behind. Here’s how you can make testers part of the transformation, too—step by step, because this is agile, after all.
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.
Part of the path to DevOps requires adoption of agile methodologies. What does it mean for testing when you switch from the traditional waterfall model, with a few long release cycles per year, to the agile model, with changes occurring every two weeks? Here are five key factors to achieve the agile software testing necessary in DevOps.
Following agile ceremonies may make an organization feel good, but that’s only a start. “Great big agile” requires leadership at all levels to focus on self-organization and empowerment as a universal framework.
Migrating an organization to continuous integration requires adoption new processes, tools, and automation. DevOps relies on dramatic culture change to encourage total transparency and collaboration among all project stakeholders.
In this interview, Jason Wick, senior manager at MakeMusic, discusses his STAREAST presentation about eight ways you could be making your one-on-one meetings completely useless. He discusses in depth what he feels is the number one way to ruin these meetings: holding back on feedback. He also offers advice on how you can educate your team leader to avoid the pitfalls that lead to ineffective one-on-ones.
Chris Loder, automation architect at InGenius, talks about being a self-taught automation developer, why learning new skills is so important, and the synergy between manual testers, automation testers, and developers.
In this interview, Bob Galen, an agile methodologist, practitioner, and coach, explains why in order to become agile, people need to overcome their resistance to change. Bob details why agile works, how people's jobs will be safe, and why "change from the bottom up" can only get you so far.
In this interview, Adam Auerbach, the vice president of quality and DevOps engineering at Lincoln Financial Group, explains how major corporations can learn to take advantage of agile and quickly adjust to the speed it demands, as well as the methods he uses to implement enterprise agile.
Successful agile software development depends on a healthy product backlog. Too often, teams attempting to adopt an agile methodology for a project with a new product owner struggle in their transition due to a sparse product backlog.
There are many companies today implementing agile and DevOps practices, usually enabled by a microservices architecture. Most of them are focused on continuously delivering value to their customers within the boundary of a time-bound sprint.
When agile transformations fail, many agilists blame their executives for not caring about or understanding agile. However, few people focus on the different languages that IT and business people speak, and the different outcomes that both sides desire.