Acceptance criteria can be helpful in expanding on user stories in order to capture requirements for agile projects. However, acceptance criteria should not be a route back to long, detailed documents, and they are not a substitute for a conversation. This article tells you how and when acceptance criteria should be written and employed.
This article details a team’s experience in implementing pair programming as a way to get work done as part of its agile transformation. It delves into the many positive results from the pairing experiment, as well as some of the negatives that were encountered, and weighs whether developers think pair programming is a worthwhile endeavor.
Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches.
Mike Talks shares with us the unlikely story of how his pet German Shepherd inadvertently became his team's QA manager. Talks explains how his German Shepherd was able to gather people together and have them talk to each other, similiar to what a QA manager does—keeping people on task, handing out assignments, and following up with team members.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
Finding defects late is a common issue when teams don't consider levels of precision or detail. You must take into account how stories and features fit into the system. In this FAQ column, Janet Gregory tells you how you should remember the big picture—even while testing the small stuff.
Improving product quality is often a very difficult task for even the best software development organizations. Rajini says the additional benefits of automation include benchmarking, code scanning analysis, end-to-end test cases, and compatibility validation.
To fully detect, isolate, and resolve quality issues in a traditional, large-scale data warehouse requires that several approaches be used together. Wayne identifies types of data quality issues and then illustrates how to best attack and resolve those pesky issues.
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.
In this interview, Janet Gregory discusses changing the testing conversation from bugs to solutions, why testers need to focus on the actual business, and simple methods that teams can employ right now to measure value and to focus on the positives rather than the negatives.
In this interview, Zephyr founder and CEO, Samir Shah, discusses how to make the agile transition as either a big or small company. He also digs into the changing nature of test management, as well as the times when you really need to automate your testing.
In this TechWell interview, Facebook's Simon Stewart digs into his company's shocking approach to testing, which is that they don't have a testing department. He also talks about the challenges and pressure that comes along with producing so many different mobile builds per year.
Capital One has a highly integrated environment, which creates many dependencies for its agile teams. Because these dependencies are often not completed until late in their sprints, Capital One faced prolonged integration and regression testing phases, and did not realize the expected...
Today, many test methodologies can be used to achieve high quality and productivity ―Agile/Scrum, TDD, data modeling, risk analysis, and personas, just to name a few. So how do you pick the best approaches and techniques for your team and projects? Learn how Steve Hares helped build a...
Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by...
A great deal of confusion surrounds the concepts of release automation, continuous integration, continuous delivery, and continuous deployment. Even some industry experts are confused about the differences. How these concepts work progressively to achieve high quality software...