# agile-testing Published articles for agile-testing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## SDET Lean Coffee #1: With AI, what is useful testing and what is workslop? SQGNE, June 2, 2026 DevFeed: [SDET Lean Coffee #1: With AI, what is useful testing and what is workslop? SQGNE, June 2, 2026]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-06-02T20:35:29Z Content type: opinion Language: en Sources: [T.J. Maher]() Topics: [Testing](), [Agile](), [sqgne](), [Development]() Tags: [agents](), [agile](), [agile-testing](), [ai](), [sqgne](), [team](), [teams](), [testing](), [work]() ### AI overview A report on the first SDET Lean Coffee organized by the Software Quality Group of New England. Attendees discussed useful testing practices with AI, AI-generated workslop, AI workflows, the testing of AI agents, and the pressures faced by software testers. The article also explains the Lean Coffee meeting format and announces the next session. ### Source excerpt With AI, what is useful when it comes to testing and what is workslop? How do you create workflows in AI? With AI producing massive amounts of code, how can a tester keep up? These are some of the topics attendees decided to talk about in our first ever SDET Lean Coffee, as part of the Software Quality Group of New England ( sqgne.org ). We exchanged war stories, horror stories, shared insights, and provided a bit of group therapy as we talked about the stress involved being the main support role of the software development team. A surprise guest was Lisa Crispin (LisaCrispin.com), author of "Agile Testing: A Practical Guide for Testers and Agile Teams". Lisa has been working with DORA, Google Cloud's DevOps Research and Assessment division. Recently, Lisa gave a talk teaming up with the "Beyond Quality" podcast, sharing what she has been doing "AI, testing, and the DORA AI Capabilities Model" at Lisa's site at https://lisacrispin.com/2026/04/20/ai-testing-and-the-dora-ai-capabilities-model/ discussing: The Dora AI Capabilitues Model How we need to test AI agents since AI agents can degrade over time What is a "Lean Coffee"?"Lean Coffee is a structured, but agenda-less meeting. Participants gather, build an agenda, and begin talking. Conversations are directed and productive because the agenda for the meeting was democratically generated". This format arose over fifteen years ago, when "Jim Benson and Jeremy Lightsmith wanted to start a group that would discuss Lean techniques in knowledge work - but didn't want to start a whole new cumbersome organization with steering committees, speakers, and such. They wanted a group that did not rely on anything other than people showing up and wanting to learn or create", according to LeanCoffee.org. When Is The Next SDET Lean Coffee? SDET Lean Coffees for the SQGNE will (usually) be held the first Tuesday of each month at 12:00 pm to 1:00 pm EDT. Interested in attending the next session Tuesday, July 7th? Register at the Soft ## Agile vs. Waterfall QA: A Comparative Guide DevFeed: [Agile vs. Waterfall QA: A Comparative Guide]() Original publisher: [Read original article]() Author: Pankaj Dusane Published: 2026-01-09T12:06:15Z Content type: comparison Language: en Sources: [Helpshift]() Topics: [Agile](), [Testing](), [Development](), [Self-organizing Team](), [Software Engineering]() Tags: [agile](), [agile-testing](), [guide](), [qa](), [software-development](), [testing](), [vs](), [waterfall-testing]() ### AI overview This comparative guide explains how quality assurance differs between Agile and Waterfall software development. It describes Waterfall QA as a dedicated testing phase after development, with fixed requirements and less flexibility, while Agile integrates QA throughout iterative development with continuous testing, feedback, and collaboration. ### Source excerpt Quality Assurance (QA) is a critical aspect of software development, ensuring that the final product meets the desired standards and functions as intended. While QA practices are integral to all development methodologies, the approach to QA can vary significantly depending on whether a project follows the Agile or Waterfall methodology. In this blog post, we'll compare these two methodologies, focusing on their impact on QA processes, workflows, and outcomes. What is Waterfall QA? The Waterfall model is a linear and sequential approach to software development. In this methodology, each phase -- from requirements gathering to design, development, testing, and deployment -- is completed before moving to the next. QA in the Waterfall model is typically conducted during a dedicated testing phase after development is complete. Key Characteristics of Waterfall QA: Late Involvement: QA is often involved only after development is finished. Fixed Scope: Testing is based on a predefined set of requirements and test cases. Extensive Testing: Since QA occurs after development, it often involves extensive end-to-end testing. Minimal Flexibility: Changes to requirements or functionality after testing begins can be costly and disruptive. Predictability: The linear nature of the process makes timelines and deliverables more predictable. Advantages of Waterfall QA: Clear documentation and test plans. Structured processes provide clarity on responsibilities and timelines. Suitable for projects with well-defined requirements and minimal expected changes. Challenges of Waterfall QA: Delayed feedback loops can prolong the discovery of critical issues. Limited ability to adapt to changes or new requirements. Potential for larger defects due to the lack of continuous testing. What is Agile QA? Agile methodology emphasizes flexibility, collaboration, and iterative development. Unlike Waterfall, Agile integrates QA throughout the development lifecycle, ensuring continuous testing and feedback