# Agile Agile is a software development discipline defined by the Manifesto for Agile Software Development's values and principles. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## "Ингосстрах" на AgileDays 2026 DevFeed: ["Ингосстрах" на AgileDays 2026]() Original publisher: [Read original article]() Author: nik\_gorbunova (Ингосстрах) Published: 2026-09-16T12:31:58Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [Agile]() Tags: [agile]() ### AI overview Ingosstrakh invites readers to its booth at AgileDays Fest in Moscow on September 17, 2026. The company will present modern Agile and digital practices, including a talk on its AI transformation operating model. ### Source excerpt Всем привет! 17 сентября в Москве пройдет AgileDays Fest, и "Ингосстрах" приглашает вас посетить стенд, оформленный в стиле 90-х как метафора надежного фундамента для современных и будущих инноваций. В 90-е зарождались Agile практики в мире; в компании - цифровые решения. На наших тематических станциях среди главной атрибутики того времени вы сможете пообщаться с экспертами про современные подходы в Agile и цифре. А в 13:50 приглашаем вас посетить выступление Евгения Денисова, лидера центра цифрового развития с докладом "Операционная модель ИИ-трансформации". Евгений расскажет как развиваются подходы и практики применения ИИ в компании. Читать далее ## What Is Bmad? Understanding the Bmad Loop and how to scale It DevFeed: [What Is Bmad? Understanding the Bmad Loop and how to scale It]() Original publisher: [Read original article]() Author: Yonatan Boguslavski Published: 2026-09-01T08:40:17Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Agile](), [AI Development](), [AI-assisted coding](), [Open Source](), [Software Engineering](), [agent observability]() Tags: [agentic](), [ai](), [ai-agents](), [ai-coding](), [autonomous](), [coding](), [coding-agents](), [development](), [open-source](), [review](), [testing]() ### AI overview This article explains the BMAD method, an open source framework for AI-driven software development, and its BMad Loop for unattended story-by-story implementation, review, testing, and commits. ### Source excerpt Learn how the BMAD method runs agentic software development, from AI-driven planning to autonomous coding, review, and commits. ## A Model Portfolio for cost-efficient AI across the software development lifecycle DevFeed: [A Model Portfolio for cost-efficient AI across the software development lifecycle]() Original publisher: [Read original article]() Author: Praveen Sidda Published: 2026-09-01T07:16:01Z Content type: article Language: en Sources: [Data Science at Microsoft]() Topics: [AI Development](), [AI Models](), [Model Routing](), [sdlc](), [Agile](), [Developer experience](), [Compression](), [Requirements](), [Testing](), [Deployment](), [Code review]() Tags: [agentic-sdlc](), [ai](), [ai-cost-optimization](), [ai-models](), [code-review](), [compression](), [deployment](), [github-copilot](), [llm](), [overhead](), [requirements](), [software-development]() ### AI overview The article examines whether routing software development tasks across a portfolio of AI models can reduce costs compared with using one premium model. It reports that lower-cost models handled well-defined tasks, while premium models were reserved for architecture, implementation, and code review; context compression reduced token usage but risked losing important technical details. ### Source excerpt Image generated by AIWhat one controlled experiment taught me about matching model capability to developer work Topic: Can intelligently routing developer tasks across different AI models outperform relying on a single premium model? In this article, I put that question to the test by mapping software development lifecycle (SDLC) stages to a portfolio of AI models and comparing the outcomes. Motivation As AI becomes embedded throughout the AI-Native Development Lifecycle (AIDLC), an evolution of the traditional Software Development Lifecycle (SDLC), its cost is no longer tied to a single prompt. A single developer task can involve multiple model calls, each carrying source files, conversation history, tool definitions, and generated output. Applying the most capable model to every interaction is straightforward, but it also consumes premium model capacity on tasks that less expensive models can often complete just as effectively. This raises an important question for engineering organizations: How can teams reduce the cost of AI-assisted development without compromising quality, reliability, or the developer experience? My first instinct was to reduce token consumption. Context compression appeared to be the most direct path to lowering inference costs by shortening prompts. Although it reduced token usage, it also introduced risk. Important constraints and technical details could be lost, affecting downstream tasks. Source code, stack traces, and active instructions proved to be especially poor candidates for lossy compression. That experience shifted my focus. The objective was not to process fewer tokens, but to complete developer tasks successfully at a lower overall cost. I then experimented with model allocation. Lower-cost models handled well-defined tasks such as requirements synthesis, planning, routine test generation, deployment artifacts, and final summaries, while premium models were reserved for architecture, implementation, and code review. This appro ## What Is an Agile Coach? Key Responsibilities and Business Impact DevFeed: [What Is an Agile Coach? Key Responsibilities and Business Impact]() Original publisher: [Read original article]() Author: ANTONIA MCCULLOUGH, AGILE COACH @ TOPTAL Published: 2026-08-31T04:00:00Z Content type: article Language: en Sources: [Toptal Blog]() Topics: [Agile](), [Self-organizing Team](), [software-development]() Tags: [agile](), [business](), [collaboration](), [development](), [guide](), [leadership](), [management](), [project-management](), [scrum](), [software-development]() ### AI overview A guide to the Agile coach role, covering its responsibilities, organizational impact, differences from Scrum masters, consultants, and project managers, and the skills needed to support Agile practices across teams and departments. ### Source excerpt Navigate the evolving world of Agile coaching with this comprehensive guide. From responsibilities and skills to business impact, explore what the role looks like today and what it takes to succeed. ## Why AI Transformations May Repeat the Failures of Earlier Digital and Agile Transformations DevFeed: [Why AI Transformations May Repeat the Failures of Earlier Digital and Agile Transformations]() Original publisher: [Read original article]() Author: David Pereira Published: 2026-08-27T14:03:51Z Content type: opinion Language: en Sources: [Untrapping Product Teams]() Topics: [Artificial Intelligence](), [Agile](), [digital]() Tags: [agile](), [ai](), [alignment](), [collaboration](), [culture](), [strategy](), [teams](), [transformation]() ### AI overview This opinion article argues that many AI transformation efforts may repeat the failures of earlier digital and Agile transformations. It attributes these failures to organizations neglecting foundational issues such as culture, strategy, alignment, collaboration, and clarity, and argues that AI can amplify existing confusion and organizational problems. ### Source excerpt Different approach, same outcomes. ## UX Conference November Announced (Nov 9 - Nov 13) DevFeed: [UX Conference November Announced (Nov 9 - Nov 13)]() Original publisher: [Read original article]() Published: 2026-08-24T06:48:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [User experience (UX)](), [Agile](), [Artificial Intelligence](), [Information Architecture]() Tags: [agile](), [ai](), [best-practices](), [collaboration](), [event](), [information-architecture](), [interaction-design](), [training](), [ux]() ### AI overview An NN/G announcement for November 9-13, 2026 offers up to five live online UX courses covering best practices, AI product strategy, design systems, interaction design, management, Agile, research, and information architecture. Participants can pursue optional UX Certificate specialty recognition. ### Source excerpt Take up to 5 in-depth training courses, teaching user experience best practices for successful design. Courses focused on long-lasting skills for UX professionals. November 9 - 13, 2026. ## How to Ensure a Smooth Design Handoff DevFeed: [How to Ensure a Smooth Design Handoff]() Original publisher: [Read original article]() Author: Kasturika Kasturika Published: 2026-08-19T10:00:00Z Content type: article Language: en Sources: [UX Daily - User Experience Daily]() Topics: [User Experience](), [User interface design](), [Usability](), [Accessibility](), [Agile]() Tags: [accessibility](), [agile](), [cc-by-sa](), [collaboration](), [communication](), [design](), [developers](), [interaction-design](), [usability](), [user-experience](), [video]() ### AI overview This article explains how designers and developers can collaborate more effectively during design handoffs. It emphasizes clear communication, mutual understanding of design and development constraints, and shared responsibility for delivering a good user experience, with particular attention to specifications, accessibility, responsive behavior, and agile workflows. ### Source excerpt In your work as a designer, you will find yourself working closely with different stakeholders, and none more common than software engineers or developers, who are responsible for implementing your designs. Designers and developers share a common goal -- to do what's best for the user and for the business. But the day-to-day realities of their collaboration aren't so clear-cut and idyllic. The main reason: miscommunication. Here are some tips to help you maintain smooth relations with "the other side."Communication is the most important skill a designer must have. In fact, every deliverable a designer creates is a form of communication: personas, journey maps, storyboards, sitemaps, user flow... ## Agile Leadership DevFeed: [Agile Leadership]() Original publisher: [Read original article]() Author: Dave Ogle Published: 2026-08-10T00:00:00Z Content type: opinion Language: en Sources: [Scott Logic]() Topics: [Agile](), [Self-organizing Team](), [trust](), [Development]() Tags: [agile](), [delegation](), [delivery](), [frameworks](), [leadership](), [self-organizing-teams](), [software-development](), [teams](), [trust]() ### AI overview This opinion argues that organisational agility depends on leadership as well as agile frameworks and processes. It highlights empowerment, trust and delegation, and examines Agile2 and the British Army's Mission Command philosophy as relevant perspectives. ### Source excerpt Agile teams are built on more than frameworks and processes. This article explores why effective leadership, trust and delegation are fundamental to true organisational agility, drawing lessons from the British Army's Mission Command philosophy. ## How the Best UX Design Teams Integrate Personas into Agile Workflows DevFeed: [How the Best UX Design Teams Integrate Personas into Agile Workflows]() Original publisher: [Read original article]() Author: James Newhook Published: 2026-08-08T04:00:00Z Content type: article Language: en Sources: [UX Daily - User Experience Daily]() Topics: [Agile](), [User experience (UX)](), [Product Management]() Tags: [agile](), [churn](), [developers](), [development](), [revenue](), [ux](), [ux-design](), [workflows]() ### AI overview This article explains how UX design teams can integrate user personas into Agile workflows. It presents personas as living tools that translate user needs into actionable requirements, reduce wasted work, improve communication, and keep product decisions focused on real user needs. ### Source excerpt You've seen it countless times: Agile teams racing through sprints while personas gather dust in forgotten folders (or never get created at all). The promise of user-centered design crashes into the reality of two-week deadlines. But what if you could harness both? Build at startup speed while truly understanding your users. Transform "as a user, I want..." into "Sarah needs this because..." and watch engagement soar, revenue climb, and churn vanish. Your products will become indispensable to users' lives while you become the go-to person who made it happen.For some, it may seem like Agile and user-centered design (and therefore, personas) don't fit together. However, Alan Cooper, the Father... ## Agent Loops for Product Managers: Definitions, Stop Conditions, and Examples DevFeed: [Agent Loops for Product Managers: Definitions, Stop Conditions, and Examples]() Original publisher: [Read original article]() Author: Paweł Huryn Published: 2026-06-22T15:15:49Z Content type: tutorial Language: en Sources: [The Product Compass]() Topics: [AI Agent](), [Claude Code](), [codex](), [Agile]() Tags: [agile](), [ai-agent](), [claude-code](), [codex]() ### AI overview This tutorial explains agent loops for product managers, distinguishing routines, workflows, and goal-driven loops. It emphasizes defining acceptance criteria, success metrics, and sign-off conditions so an agent knows when to stop, and discusses Claude Code, Codex, /loop, and /goal. ### Source excerpt PMs already define done: acceptance criteria, metrics, signoff. That's what makes loops useful. Includes PRD hardening, feedback clustering, competitor watch, and ship checks. ## How Design Systems Help Designers Work More Effectively on Agile Teams DevFeed: [How Design Systems Help Designers Work More Effectively on Agile Teams]() Original publisher: [Read original article]() Author: Paivi Salminen Published: 2026-06-18T04:35:20Z Content type: article Language: en Sources: [UX Magazine]() Topics: [Agile](), [Design system](), [User experience (UX)](), [User Interfaces]() Tags: [agile](), [components](), [consistency](), [design](), [design-system](), [design-systems](), [interface](), [teams](), [ux]() ### AI overview The article examines how agile teams' continuous feature work can leave designers with too little time. It explains that design systems reduce repetitive visual-design decisions and help designers focus more on how interfaces support users' goals. ### Source excerpt One of the most common complaints designers have about working on agile teams is the feeling that there's never enough time. There's always another feature to design. Another sprint is starting. Another ticket is waiting for input. Even when a feature ships, the work doesn't necessarily stop. Agile teams are supposed to observe how the The post The Agile Trap Designers Fall into: Feeding the Beast appeared first on UX Magazine. ## 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 ## Why Agile Designers Fear Shipping Imperfect Work DevFeed: [Why Agile Designers Fear Shipping Imperfect Work]() Original publisher: [Read original article]() Author: Paivi Salminen Published: 2026-05-28T03:39:21Z Content type: opinion Language: en Sources: [UX Magazine]() Topics: [Agile](), [User experience (UX)](), [Development]() Tags: [agile](), [development](), [product-development](), [teams](), [ux]() ### AI overview This commentary examines why designers may resist releasing early versions of features in agile development. It argues that minimum viable products must be usable, because confusing or broken releases produce unreliable feedback, and that iteration is essential for early releases to provide value. ### Source excerpt One insight from Laura Klein that stuck with me is that in a minimum viable product, teams often forget the word "viable." A thing that surprised me while studying agile product development is how psychological it is. We often talk about agile as if it were purely a process. There are sprints, backlogs, standups, and The post The Part of Agile Designers Fear the Most: Imperfect Work appeared first on UX Magazine. ## Designing Small Is Harder than Designing Big DevFeed: [Designing Small Is Harder than Designing Big]() Original publisher: [Read original article]() Author: Paivi Salminen Published: 2026-05-07T04:46:27Z Content type: article Language: en Sources: [UX Magazine]() Topics: [User experience (UX)](), [Agile]() Tags: [agile](), [design](), [ux]() ### AI overview The article argues that designing for agile teams is less about working faster and more about designing smaller, self-contained slices of a broader product that can deliver value within a short development cycle. It contrasts this with designers' tendency to think holistically about complete systems and long-term experiences. ### Source excerpt After 10+ years working in Agile marketing teams, I thought I understood Agile. Then I started studying UX and realized I'd been looking at it from the wrong angle. When people talk about working on agile teams, they often describe the challenge as a matter of speed. Everything moves faster. Sprints are short. Engineers are The post Designing Small Is Harder than Designing Big appeared first on UX Magazine. ## Spec Driven Development isn't Waterfall DevFeed: [Spec Driven Development isn't Waterfall]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2026-04-09T00:00:00Z Content type: opinion Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Spec Driven Development](), [Agile](), [Kiro](), [Software Engineering](), [Artificial Intelligence]() Tags: [agile](), [ai](), [blog](), [development](), [engineering](), [software-development](), [spec-driven-development](), [writing]() ### AI overview The article argues that spec-driven development is not a return to waterfall development. It presents specifications as explicit, versioned, living artifacts that evolve through user feedback and iterative development, with implementation derived from changing requirements and design choices. In this view, AI can accelerate the iteration cycle without making the process rigid or top-down. ### Source excerpt Spec Driven Development isn't Waterfall Write down what you mean. After spending a few months writing (e.g. on the Kiro Blog), and speaking (e.g. Real Python Podcast, SE Radio) about spec-driven development, I've noticed a common misconception: spec driven development is a return to a waterfall style of software development. Specification driven development (in Kiro, for example) isn't about pulling designs up-front, it's about pulling designs up. Making specifications explicit, versioned, living artifacts that the implementation of the software flows from, rather than static artifacts. This distinction is important, because software development (like all complex product development and engineering tasks) is a fundamentally iterative process. It is extremely rare for a software project to know all of the requirements up-front. It's much more common for one of the goals of the development process being to discover requirements, most frequently through engaging users in the cycle of feedback. This is a point that's missed in strict waterfall software development processes, and missed in critiques (like Dijkstra's) of natural language specification (as I have written about before). The Agile movement is often presented as a high-minded set of ideas, but I think it's more accurate to see it as a reflection of a simple fact: as software became more complex, and filled more roles in society, top-down approaches to design simply no longer work. From the Agile Manifesto: Customer collaboration over contract negotiation Responding to change over following a plan These are simple reflections of reality. Software specifications are complex, dynamically changing, internally conflicting, and invariably incomplete. In specification driven development, the specification is the thing being iterated on, rather than the implementation. The iteration cycle is the same as before, but potentially much quicker because of the accelerating effect of AI. So if specifications aren't up-front ## 7 steps in a Legacy Modernization Project DevFeed: [7 steps in a Legacy Modernization Project]() Original publisher: [Read original article]() Author: Federico Tomassetti Published: 2026-02-25T06:55:00Z Content type: tutorial Language: en Sources: [Federico Tomassetti]() Topics: [Agile](), [Code quality](), [Code](), [modules]() Tags: [automated](), [business-value](), [code-quality](), [legacy-modernization](), [modernization](), [modules](), [project](), [rpg](), [technical]() ### AI overview This tutorial outlines seven steps for modernizing an RPG-based ERP/MRP system: assess the legacy landscape, define a roadmap, secure buy-in and budget, build the right team and partnerships, execute iterative value-driven increments, manage change, and measure and adapt the modernization effort. ### Source excerpt Embarking on an RPG-based ERP/MRP system modernization is undeniably complex. But it's also highly rewarding when aligned with your business's long-term success. By addressing both the technical and strategic facets, you turn an aging system from a liability into a competitive asset. Let's outline the 7 steps in a legacy modernization project: Step 1: Assess [...] The post 7 steps in a Legacy Modernization Project appeared first on Federico Tomassetti. ## The Design Process and Agile Development: Part 1 -- Design Is Collaborative DevFeed: [The Design Process and Agile Development: Part 1 -- Design Is Collaborative]() Original publisher: [Read original article]() Author: Daisy Mølving Published: 2026-02-05T06:00:00Z Content type: opinion Language: en Sources: [8th Light Insights]() Topics: [Agile](), [User experience (UX)](), [Development](), [Self-organizing Team]() Tags: [agile](), [delivery-and-practice](), [design-thinking](), [development](), [development-process](), [experiential-design](), [product-strategy-innovation](), [research](), [teams](), [user-experience](), [ux-design]() ### AI overview Part 1 of a series examines how design thinking and UX research can work alongside Agile development. It argues that iterative design and Agile delivery are compatible, while noting the tension between research needs, rapid timelines, client goals, and incremental development. ### Source excerpt This is Part 1 in our blog series on how the design process works alongside Agile methodology to produce results within an integrated team. Updated 2/5/2026. Originally published 2/2/2024 When it comes to developing new software, not every designer approaches the task the same way. While some use a design thinking approach, looking at the tasks from a user perspective, others use Agile methods, approaching it from an iterative project management standpoint. However, the two approaches are not mutually exclusive. The most successful designers approach their tasks using design thinking which helps inform prioritization within the Agile methodology. High performing teams delivering outcomes through the agile methodology do so with confidence when they know solutions are informed by the voice of the user. Working with Design Thinking and Agile Timelines Designers who've worked alongside Agile methodologies have likely felt the pressure of Agile timelines conflicting with the need for comprehensive design. While the approaches may feel conflicting at first, it's important to remember that both design and Agile methodologies emphasize the importance of working in small iterations to develop products that constantly evolve-- focusing on the smallest modifications that lead to making valuable products and building upon them. However, with its need for preliminary research, I've observed that user experience (UX) design can give Agile practitioners the impression of a waterfall process. Agile teams want to deliver quickly and continue iterating on the project after receiving feedback. As a UX designer, it is my responsibility to establish and fulfil the human need by talking to some users and conducting competitor research before we dive blindly into development. Working as a UX designer in this environment can feel like you're stuck between a rock and a hard place. You have a client who cares about the bottom line and wants to get to market quickly and a development team of ## The Design Process and Agile Development: Part 2 -- Collaborative Activities DevFeed: [The Design Process and Agile Development: Part 2 -- Collaborative Activities]() Original publisher: [Read original article]() Author: Daisy Mølving Published: 2026-01-16T06:00:00Z Content type: tutorial Language: en Sources: [8th Light Insights]() Topics: [Agile](), [User experience (UX)](), [Development](), [Software Engineering](), [Testing]() Tags: [agile](), [continuous-integration](), [design](), [development](), [experiential-design](), [teams](), [testing](), [user-experience]() ### AI overview This article explains how UX designers, product owners, and software developers can collaborate during an agile design process. It focuses on continuous discovery through stakeholder interviews, competitive and analogous research, user interviews, testing, and collaboration with developers on codebase, infrastructure, feasibility, and timelines. ### Source excerpt Updated 1/16/2026. Originally published 12/10/2024 As we talked about in Part 1 of this blog series, The Design Process and Agile Development: Part 1 -- Design Is Collaborative, the design process provides teams with the opportunity to join forces, paving the way for an integrated team of user experience (UX) designers, product owners, and agile software development to create a successful product. So where do you begin? You have a new project and an integrated team. You know that success can be achieved in close collaboration between your team members, each representing deep expertise in desirability, viability, and feasibility. But you need to determine which activities are most profitable for the team to put their heads together on and what their responsibilities should be. Find Out Together Finding Out is where it all starts, but it most certainly doesn't only happen at the start! We 'find out' in continuous cycles throughout the project, not just from our users, but also from our stakeholders and product and development teammates. After all, though the end product is ultimately for our end users, design is also influenced by viability, or the business, and feasibility, or the developers. So it makes sense to 'find out' collaboratively. You can do this through stakeholder interviews, competitive analysis and analogous research, user interviews and testing, and continuous integration (CI) tools. Stakeholder Interviews Stakeholder interviews are an early, integral step for determining what your stakeholders care about -- their hopes and fears, past project experiences that might drive their decision-making, key metrics they need to hit, and any assumptions they may have. Not only will you build rapport, you'll also learn how to engage your stakeholders through the design process. I've experienced that not all stakeholders have immediate faith in design, so understanding how they measure success and engaging with their success criteria throughout your work can be cruc ## Software Development Waste DevFeed: [Software Development Waste]() Original publisher: [Read original article]() Author: Dr Milan Milanović Published: 2026-01-15T16:01:54Z Content type: article Language: en Sources: [Tech World With Milan Newsletter]() Topics: [software-development](), [Software Engineering](), [Agile](), [code productivity]() Tags: [agile](), [best-practices](), [cognitive-load](), [cross-functional-teams](), [development-process](), [productivity](), [quality](), [software-development](), [switching]() ### AI overview This article explains software development waste through lean thinking. It reviews the traditional seven wastes, discusses an expanded taxonomy that includes issues such as wrong features, backlog mismanagement, over-engineering, cognitive load, communication problems, and waste from AI-generated code, and presents practices for reducing waste. ### Source excerpt Many of us can look back at a completed software project and think, "If I'd known then what I know now, I'd have done much faster." This familiar feeling reveals just how much waste creeps into the software development process. ## 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 ## Building the Web that Moves Money: inside Web engineering at Revolut DevFeed: [Building the Web that Moves Money: inside Web engineering at Revolut]() Original publisher: [Read original article]() Author: Revolut Published: 2025-10-16T09:45:59Z Content type: article Language: en Sources: [Revolut Engineering]() Topics: [Web Development](), [modern web development](), [web applications](), [Low-Code / Internal Tools](), [Agile]() Tags: [agile](), [applications](), [building](), [engineering](), [fintech](), [internal-tools](), [modern-web-development](), [revolut](), [web](), [web-applications](), [web-development](), [web-engineering]() ### AI overview Revolut describes its web engineering approach across customer-facing products and roughly a hundred internal web applications. The article discusses secure financial experiences, modern development practices, small empowered teams, and agile principles inspired by Extreme Programming. ### Source excerpt Building the Web that moves money: inside Web engineering at RevolutIntroduction In today's digital-first economy, the web is the critical touchpoint between people and their money. At Revolut, we embrace this reality in our approach to web engineering: focusing on not just building interfaces, but on creating seamless, secure, and future-proof financial experiences. Our mission at Revolut is to redefine the global standard for digital finance. Every line of code, design decision, and feature we release serves this goal: to make finance more accessible and beautifully engineered. These principles shape our culture, set a high standard for excellence, and require constant attention to detail. They also drive us to rethink modern web development tools and practices. This article focuses on the principles that help us deliver secure, beautiful financial products worldwide, and explains how engineers are building their careers along the way. The scope of Revolut web products Two independent but complementary pillars represent the current stage of the Revolut web ecosystem. Customer-facing applications These are the digital gateways through which our customers and partners experience Revolut directly: Main website and brand hub Revolut Business platform Revolut crypto exchange platform Human Resources Management Systems (HRMS) by Revolut Each of these touchpoints is an individual part of a unified ecosystem offering a consistent product experience that is closely aligned with our mobile platform. Internal web products Alongside our external platforms, Revolut operates around a hundred internal web applications. These provide our employees, operations, and partners with tools for: Back-office management Compliance and risk monitoring Customer support services Data and reporting systems Operational efficiency at scale These internal tools are the driving force behind Revolut, ensuring customer-facing products remain fast, secure, and globally scalable Core principles of we ## Management and Productivity Laws for Decision-Making and Organizational Behavior DevFeed: [Management and Productivity Laws for Decision-Making and Organizational Behavior]() Original publisher: [Read original article]() Author: Tom Published: 2025-08-26T00:00:00Z Content type: opinion Language: en Sources: [Tomasz Gągor]() Topics: [decision-making](), [Agile](), [meetings]() Tags: [business-efficiency](), [communication](), [conway-s-law](), [corporate-best-practices](), [decision-making](), [effectiveness](), [leadership](), [leadership-tips](), [management](), [management-laws](), [murphy-s-law](), [organizational-behavior](), [processes](), [productivity-principles](), [team-management](), [workplace-decision-making]() ### AI overview This opinion article introduces several management and productivity "laws," including Kidlin's Law, Gilbert's Law, Wilson's Law, and Falkland's Law. It explains how clear problem statements, explicit guidance, timely action, and avoiding unnecessary decisions can support workplace decision-making and organizational effectiveness. ### Source excerpt Discover the most influential management and productivity "laws"-from Murphy's Law to Conway's Law-that shape decision-making, leadership, and organizational behavior. Learn practical applications and scientific backgrounds to boost your effectiveness at work. ## Building High Trust: The Artisan of the Day Is John Drexler DevFeed: [Building High Trust: The Artisan of the Day Is John Drexler]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-08-10T04:04:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Product Management](), [Agile]() Tags: [agile](), [blog](), [developer](), [laravel](), [product-management]() ### AI overview This profile of John Drexler presents him as a Laravel developer and product manager who co-founded the development agency Thunk. It describes his work on Laravel Forge, game development, product consulting, and a philosophy that developers should develop product-management responsibilities and focus on trust, communication, and practical team processes. ### Source excerpt If your biggest problems at work aren't technical, you're not alone. The good news is that John Drexler has the solutions. ## How AI Tools Reshape the UX Design Process DevFeed: [How AI Tools Reshape the UX Design Process]() Original publisher: [Read original article]() Author: Chris Jones Published: 2025-07-28T22:49:08Z Content type: opinion Language: en Sources: [GumGum]() Topics: [Artificial Intelligence](), [User experience (UX)](), [Agile](), [Development]() Tags: [agile](), [ai](), [development](), [product-design](), [ux]() ### AI overview A designer reflects on adapting the UX design process to AI tools. The article argues that AI changes how designers handle automatable work while preserving the broader cycle of research, prototyping, testing, and design, and describes using NotebookLM to synthesize interview transcripts during discovery. ### Source excerpt AI enabled and ready to go! I've spent my career navigating the major shifts in tech and design, tailoring my approach along the way: Web 1.0 and Macromedia Flash, the mobile-first revolution, Agile development, Lean UX, the Double Diamond, and Design Sprints. But then, just like that, with a few new tools, I was AI-enabled. Note, I said tailored. At each stage, the next best thing or new way of working is often discussed as a radical development. However, the impact on the design process is often far less radical. We research, prototype, test, and design; we go broad, then narrow, and sometimes we even go broad again. This stuff takes time to get right (anyone want to rewatch 10 hours of user interviews?) But, as designers, our aim has always been to deliver well-thought-out solutions that approach a challenge with a unique perspective, born out of a desire to be visual in our thinking. Then, along comes AI, all innocent-like, with its polite manners and slightly sycophantic ways. "Work with me," it says. "That's a fantastic idea," it encourages. "Let me make it better for you." FINE! So I've spent the last few months ripping up my design process -- and a few long-held beliefs along the way -- to create an entirely new way of working, which also feels strangely familiar. Familiar because, like all the shifts that came before it, this one is once again forcing me to shed the tasks that can be automated and focus on what makes me human. Here we go. Discovery with AI Don't get me wrong here; I love those users. But let's be honest: the manual synthesis during the discovery phase can be a grind. We write the scripts, find the users, interview each one, watch back the recordings, make notes, lose the will to live, cover a room (or a country-sized MIRO board) in Post-its, benchmark competitors, create themes, and then finally identify and prioritise the key findings. Today? Do the interviews, then drop the transcripts into NotebookLM along with details about the Product, c [Next page]()