# 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.

## Stochastic Modeling of the Mean Time Between Software Failures: A review

DevFeed: [Stochastic Modeling of the Mean Time Between Software Failures: A review](<https://devfeed.tech/articles/stochastic-modeling-of-the-mean-time-between-software-failures-a-review-139579.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.21619>)

Author: Gabriel Pena, Veronica Moreno, Nestor Barraza

Published: 2026-11-18T05:00:00Z

Content type: comparison

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Software Process](<https://devfeed.tech/topics/software-process.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [failures](<https://devfeed.tech/tags/failures.md>), [methodologies](<https://devfeed.tech/tags/methodologies.md>), [model](<https://devfeed.tech/tags/model.md>), [modeling](<https://devfeed.tech/tags/modeling.md>), [models](<https://devfeed.tech/tags/models.md>), [performance](<https://devfeed.tech/tags/performance.md>), [process](<https://devfeed.tech/tags/process.md>), [processes](<https://devfeed.tech/tags/processes.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [review](<https://devfeed.tech/tags/review.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [stat-ap](<https://devfeed.tech/tags/stat-ap.md>), [testing](<https://devfeed.tech/tags/testing.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

The review compares how established non-homogeneous Poisson process models and a recently proposed contagion model derive mean time between software failures, with attention to Agile projects where testing and debugging are iterative. In the Poisson models, failure rate varies with time; in the contagion model, it also depends on the number of failures already detected. The authors place these models within the broader class of non-homogeneous birth processes and outline a general theory for expected times to failure and between failures. The excerpt states the review's evaluation focus but gives no comparative performance results.

### Source excerpt

arXiv:2611.21619v1 Announce Type: new Abstract: A review of several models for the software failure detection stochastic process is per- formed. We focus on how the Mean Time Between Failures is obtained from those models and present a comparative study. The models considered involve some of the well known based on non- homogeneous Poisson processes and a recently proposed model based on contagion. Our main target is to evaluate the models performance when they are applied to modern software projects developed under Agile methodologies. Recently developed Software Engineering practices (TDD, Scrum, etc.), propose an iterative procedure be- tween development, testing and debugging, introducing this way, particular challenges to Software Reliability modeling. As opposed to the non-homogeneous Poisson processes, the failure rate of the contagion model depends not just on time but also on the number of previously detected failures. All the considered models are particular cases of non- homogeneous Birth Processes, a general fundamental theory on how to obtain time to failure and time between failures expectations is also shown.

## Software developers need an Agentic manifesto

DevFeed: [Software developers need an Agentic manifesto](<https://devfeed.tech/articles/software-developers-need-an-agentic-manifesto-129004.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4246952/software-developers-need-an-agentic-manifesto.html>)

Author: Nick Hodges

Published: 2026-11-11T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Spec Driven Development](<https://devfeed.tech/topics/spec-driven-development.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [versioning](<https://devfeed.tech/topics/versioning.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agile-development](<https://devfeed.tech/tags/agile-development.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-development-approaches-generative-ai-software-development](<https://devfeed.tech/tags/artificial-intelligence-development-approaches-generative-ai-software-development.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [development-approaches](<https://devfeed.tech/tags/development-approaches.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [manifesto](<https://devfeed.tech/tags/manifesto.md>), [software](<https://devfeed.tech/tags/software.md>), [software-developers](<https://devfeed.tech/tags/software-developers.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [specification](<https://devfeed.tech/tags/specification.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article argues that coding agents could make implementation cheap enough to shift software development toward iterating on specifications with customer feedback. It outlines two loops: either customers approve each revised specification before implementation, or they review only the working application while the specification remains the source of truth. It considers rebuilding from scratch, modifying the prior implementation, or combining both approaches, and proposes comprehensive agent-written tests as a possible way to validate iterations. The author presents this as a blend of Waterfall's emphasis on specifications and Agile feedback, while raising unresolved concerns: natural-language ambiguity, maintainability when developers have not written the code, costs, and specifying qualities such as security, performance, accessibility, and look and feel. The proposed approach is described as most applicable to greenfield projects; its broader effects remain uncertain.

### Source excerpt

I can't decide whether Agile development is completely dead or about to make a huge comeback. Or maybe Waterfall will. Who knows? Coding agents are changing everything -- and I don't think we've quite figured out how they are going to update our methodology, or how we are going to organize ourselves to take advantage of them. We have barely scratched the surface. Folks who have been around a while will remember the Waterfall method for developing software. Because coding was the hardest part of any project, Waterfall called for figuring everything out before you even started writing code. You would write a huge specification, detailing everything, then turn it over to the development team. The development team would build to the spec and pass the software on to the testing team who would verify it, and finally the project would be delivered to customers. Never mind that by the time the thing was built and tested, what the customer wanted had probably changed dramatically. And if the customer decided they wanted a widget here and a sprocket there after the specification was written? Well, that would be a formal change request and would require a whole lot more time and money, thank you very much. Yeah, they really did it that way. Waterfall bad, Agile good It didn't take long for everyone to figure out that the Waterfall way wasn't going to cut it. Projects were almost always late and not at all what customers wanted. There had to be a better way, and eventually a bunch of software luminaries quite literally got together in a room and wrote the Agile manifesto. They argued that you didn't have to be so rigid to actually get things done. It was quite revolutionary at the time. The Agile manifesto helped popularize methods like Scrum and other implementations of Agile, which of course have been much debated. We software developers like to kibitz about how to write software, but despite petabytes of bits dedicated to what Agile is and isn't, we all generally agreed that

## Mitigating Risks in Software Development through Effective Requirements Engineering

DevFeed: [Mitigating Risks in Software Development through Effective Requirements Engineering](<https://devfeed.tech/articles/mitigating-risks-in-software-development-through-effective-requirements-engineering-93681.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2305.05800>)

Author: Valentin Burkin

Published: 2026-10-21T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Requirements](<https://devfeed.tech/topics/requirements.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [risk-management](<https://devfeed.tech/topics/risk-management.md>), [Specifications](<https://devfeed.tech/topics/specifications.md>)

Tags: [cs-se](<https://devfeed.tech/tags/cs-se.md>), [requirements-engineering](<https://devfeed.tech/tags/requirements-engineering.md>), [risks](<https://devfeed.tech/tags/risks.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The paper presents requirements engineering as a way to reduce software project risks that begin with unclear or faulty requirements, while noting that evidence on defect costs has been criticized. It surveys elicitation, analysis and negotiation, specification, validation, and change management; distinguishes requirements from domain properties, assumptions, and definitions; and compares how waterfall, spiral, Rational Unified Process, and agile lifecycles handle requirements. It also covers stakeholder identification, elicitation techniques and obstacles, and approaches for turning vague or conflicting statements--including security and performance expectations--into precise, verifiable, prioritized requirements. The supplied text is an abstract-level overview, not the full paper.

### Source excerpt

arXiv:2305.05800v2 Announce Type: replace Abstract: Problems that originate in requirements are common and expensive in software projects, and they are a recurring cause of late delivery, budget overruns and cancellation. This paper is a narrative overview of requirements engineering (RE) as a means of reducing these risks. It outlines the core RE activities (elicitation, analysis and negotiation, specification, validation and change management) and the kinds of statements a requirements document contains, including the distinction between requirements, domain properties, assumptions and definitions. It reviews the evidence on the cost of requirements defects, together with the main criticisms of that evidence, and compares how the waterfall, spiral, iterative (Rational Unified Process) and agile lifecycles treat requirements. It then discusses stakeholder identification, elicitation techniques and common obstacles to elicitation, and describes practical ways of turning vague or conflicting stakeholder statements, including security and performance expectations, into precise, verifiable and prioritized requirements. The paper is intended as an introduction for practitioners and students who work with requirements but are not RE specialists.

## Deliberate Practice and Continuous Improvement in Software Teams

DevFeed: [Deliberate Practice and Continuous Improvement in Software Teams](<https://devfeed.tech/articles/deliberate-practice-and-continuous-improvement-in-software-teams-89925.md>)

Original publisher: [Read original article](<https://deanhume.com/deliberate-practice-and-continuous-improvement-in-software-teams/>)

Author: Dean Hume

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [Dean Hume](<https://devfeed.tech/sources/dean-hume.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [Kanban](<https://devfeed.tech/topics/kanban.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [kanban](<https://devfeed.tech/tags/kanban.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [teams](<https://devfeed.tech/tags/teams.md>), [technical-leadership](<https://devfeed.tech/tags/technical-leadership.md>)

### AI overview

The article applies deliberate practice to software teams, arguing that retrospectives, goals, measurement, and honest feedback support improvement when teams act on what they learn. It cautions that ceremonies and metrics can become ineffective when teams go through the motions or misuse them.

### Source excerpt

Doing something for 10,000 hours doesn't make you an expert. This post looks at what deliberate practice really means, and how Scrum and other Agile approaches can help teams keep improving.

## Quality is speed: Where engineering discipline moves in the AI era

DevFeed: [Quality is speed: Where engineering discipline moves in the AI era](<https://devfeed.tech/articles/quality-is-speed-where-engineering-discipline-moves-in-the-ai-era-65603.md>)

Original publisher: [Read original article](<https://www.thoughtworks.com/insights/articles/quality-is-speed-AI-era>)

Author: Joe Murray

Published: 2026-10-06T00:00:00Z

Content type: article

Language: en

Sources: [Thoughtworks Insights](<https://devfeed.tech/sources/thoughtworks-insights.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [auditability](<https://devfeed.tech/tags/auditability.md>), [building-software](<https://devfeed.tech/tags/building-software.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [delivering-value](<https://devfeed.tech/tags/delivering-value.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [quality](<https://devfeed.tech/tags/quality.md>), [speed](<https://devfeed.tech/tags/speed.md>)

### AI overview

Thoughtworks Chief Scientist Martin Fowler discusses how software teams can adapt engineering discipline as AI changes development. The interview argues that quality enables delivery speed, recommends using evidence and feedback loops to guide experiments, and describes security controls for AI agents with broad permissions. It also presents Thoughtworks' 3/3/3 delivery framework and an example of modernizing a legacy system.

### Source excerpt

Quality is speed: Where engineering discipline moves in the AI era

## Prisma ORM Manifesto 2026: Open, Extensible, Collaborative

DevFeed: [Prisma ORM Manifesto 2026: Open, Extensible, Collaborative](<https://devfeed.tech/articles/prisma-orm-manifesto-2026-open-extensible-collaborative-64068.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/prisma-orm-manifesto-2026>)

Author: Will Madden

Published: 2026-10-02T00:00:00Z

Content type: article

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [Prisma](<https://devfeed.tech/topics/prisma.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [developers](<https://devfeed.tech/tags/developers.md>), [discord](<https://devfeed.tech/tags/discord.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [dx](<https://devfeed.tech/tags/dx.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [manifesto](<https://devfeed.tech/tags/manifesto.md>), [orm](<https://devfeed.tech/tags/orm.md>), [prisma](<https://devfeed.tech/tags/prisma.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Prisma presents ORM 8 as an open, extensible TypeScript framework intended to let its community build database support and integrations. Its principles include making database migrations explicit, verifiable, and safer to delegate to agents; improving developer experience; and supporting modern JavaScript environments. The manifesto also describes a shift in the core team's role toward maintaining the foundation and supporting community contributors.

### Source excerpt

The five principles behind Prisma ORM 8: an open framework and ecosystem, tools that are safe to delegate, exceptional DX, modern JavaScript, and stewardship.

## How AI and discovery practices can reduce uncertainty before building an MVP

DevFeed: [How AI and discovery practices can reduce uncertainty before building an MVP](<https://devfeed.tech/articles/start-at-the-beginning-how-to-get-the-most-out-of-discovery-and-alpha-59231.md>)

Original publisher: [Read original article](<https://blog.scottlogic.com/2026/09/24/get-most-out-of-discovery-alpha.html>)

Author: Ann Cooper

Published: 2026-09-24T15:10:00Z

Content type: article

Language: en

Sources: [Scott Logic](<https://devfeed.tech/sources/scott-logic.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [iteration](<https://devfeed.tech/topics/iteration.md>), [Demo](<https://devfeed.tech/topics/demo.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [digital-government](<https://devfeed.tech/tags/digital-government.md>), [digital-transformation](<https://devfeed.tech/tags/digital-transformation.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [institute-for-government](<https://devfeed.tech/tags/institute-for-government.md>), [mvp](<https://devfeed.tech/tags/mvp.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [risks](<https://devfeed.tech/tags/risks.md>), [uncertainty](<https://devfeed.tech/tags/uncertainty.md>)

### AI overview

This article argues that discovery and alpha phases should reduce uncertainty and test major risks rather than rush teams toward an MVP. It examines how AI accelerates proofs of concept and demos while warning that faster iteration can still lead teams in the wrong direction.

### Source excerpt

AI is making it faster and easier than ever to build proofs of concept and MVPs, but in this post I argue that discovery and alpha phases deliver the most value when they focus on reducing uncertainty and testing the biggest risks.

## AI product-management expertise requires more than courses, certificates, and tool familiarity

DevFeed: [AI product-management expertise requires more than courses, certificates, and tool familiarity](<https://devfeed.tech/articles/dare-to-be-different-59507.md>)

Original publisher: [Read original article](<https://dpereira.substack.com/p/dare-to-be-different>)

Author: David Pereira

Published: 2026-09-24T12:29:17Z

Content type: opinion

Language: en

Sources: [Untrapping Product Teams](<https://devfeed.tech/sources/untrapping-product-teams.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [building-with-ai](<https://devfeed.tech/tags/building-with-ai.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [certification](<https://devfeed.tech/tags/certification.md>), [courses](<https://devfeed.tech/tags/courses.md>), [llms](<https://devfeed.tech/tags/llms.md>), [product](<https://devfeed.tech/tags/product.md>), [product-owner](<https://devfeed.tech/tags/product-owner.md>), [prompting](<https://devfeed.tech/tags/prompting.md>)

### AI overview

The article argues that learning AI tools, improving prompts, building agents, and collecting courses or certificates does not necessarily make someone a better product manager. It compares the current AI-product-management training market with the earlier Agile certification boom and emphasizes practical field experience over credentials.

### Source excerpt

Something interesting is happening now.

## Starting an Agentic Software Project with Existing Context and Evolving Specs

DevFeed: [Starting an Agentic Software Project with Existing Context and Evolving Specs](<https://devfeed.tech/articles/my-first-agentic-project-the-blank-page-was-the-hardest-part-58512.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/my-first-agentic-project/>)

Author: Kendra Haan

Published: 2026-09-23T12:00:03Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [AI Development](<https://devfeed.tech/topics/ai-development.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [context](<https://devfeed.tech/topics/context.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Figma](<https://devfeed.tech/topics/figma.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-for-developers](<https://devfeed.tech/tags/ai-for-developers.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [figma](<https://devfeed.tech/tags/figma.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [review](<https://devfeed.tech/tags/review.md>), [skills](<https://devfeed.tech/tags/skills.md>), [software](<https://devfeed.tech/tags/software.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

An account of starting an agentic software project by combining kickoff context, a Figma Make design, reusable agent skills, and an initial set of product specs. The article argues that teams need enough context for agents to take a meaningful first step, while allowing specs and process to evolve through agile iteration and review.

### Source excerpt

I expected my first project using agentic development to feel smooth and easy to pick up from day one. After all, I read Atomic's agentic playbook and stayed up to date on the latest trends and models. But when I started, I suddenly had more questions than answers. Do I need to design this whole [...] The post My First Agentic Project: The Blank Page Was the Hardest Part appeared first on Atomic Spin.

## A Software Startup's Clash With Waterfall Bureaucracy

DevFeed: [A Software Startup's Clash With Waterfall Bureaucracy](<https://devfeed.tech/articles/it-s-all-part-1-of-the-process-58894.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/it-s-all-part-1-of-the-process>)

Author: Ellis Morning

Published: 2026-09-23T06:30:00Z

Content type: opinion

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Software](<https://devfeed.tech/topics/software.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [meetings](<https://devfeed.tech/topics/meetings.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [feature-articles](<https://devfeed.tech/tags/feature-articles.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [priority](<https://devfeed.tech/tags/priority.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

A software startup building stock-market surveillance systems clashes with a customer's rigid waterfall process. When the startup creates an unplanned custom reporting module to meet users' needs, the change triggers meetings, documentation updates, and project-plan revisions.

### Source excerpt

Our submitter Tim C. shares his tale of an especially brutal culture clash: I had co-founded a software startup doing stock market surveillance. In the early 2000s, the WTF Exchange (WTFX) was a major customer of ours. We were one part of a major project of theirs, a complete overhaul of their trading engine and IT systems. Compared to our other clients, WTFX was quite bureaucratic. There seemed to be a strong focus on the process, rather than the mission or the result. They were even explicit about this, telling us, "The process is the deliverable." I believe they made that explicit in talking to us because our culture was quite agile and thereby contrasted, or clashed, with the culture of everyone else working on the project. "Predictability" was another buzzword they used to admonish us. We were required and expected to abide by the grand "waterfall" design and project plan and project timeline. The grand project was controlled via an enormous Gantt chart and they hated having to make any change to the Gantt chart. There was one report which was central to the Exchange's surveillance department. The occasional opportunities I got to talk directly to end-users, they always stressed the importance of this report, and the importance of it updating immediately to changes in the filtering criteria, and the importance of the fine details such as colour-coding cells based on certain rules. It became clear to me that we could not handle this report using a report definition file fed into our general report-writing module. It called for a custom piece of software. So over the course of the next weekend, in my hotel room, I whipped up a solution for these users: a whole new module to be added to our suite. It was maybe not perfect, but it was largely complete by the time I proudly unveiled my creation the next Monday. However, instead of a pat on the back, I was greeted by looks of horror. This module had a whole new name, was not mentioned anywhere in the giant Gantt char

## CISO Conversations: Noopur Davis - The Accidental Global CISO at Comcast

DevFeed: [CISO Conversations: Noopur Davis - The Accidental Global CISO at Comcast](<https://devfeed.tech/articles/ciso-conversations-noopur-davis-the-accidental-global-ciso-at-comcast-55798.md>)

Original publisher: [Read original article](<https://www.securityweek.com/ciso-conversations-noopur-davis-the-accidental-global-ciso-at-comcast/>)

Author: Kevin Townsend

Published: 2026-09-21T14:30:00Z

Content type: article

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ciso](<https://devfeed.tech/tags/ciso.md>), [ciso-conversations](<https://devfeed.tech/tags/ciso-conversations.md>), [ciso-strategy](<https://devfeed.tech/tags/ciso-strategy.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [developer](<https://devfeed.tech/tags/developer.md>), [director-of-engineering](<https://devfeed.tech/tags/director-of-engineering.md>), [featured](<https://devfeed.tech/tags/featured.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [management](<https://devfeed.tech/tags/management.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

An interview with Noopur Davis describes her path from software developer and engineering leader to Global CISO at Comcast. It discusses leading distributed security teams, software engineering process management, applied organizational research, and the people-focused principles of the Agile movement.

### Source excerpt

Noopur Davis never planned a career in cybersecurity. She was a developer at Intergraph, and for many years that was all she wanted to be. The post CISO Conversations: Noopur Davis - The Accidental Global CISO at Comcast appeared first on SecurityWeek.

## Digital transformation fails without this culture shift

DevFeed: [Digital transformation fails without this culture shift](<https://devfeed.tech/articles/digital-transformation-fails-without-this-culture-shift-50541.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4222873/digital-transformation-fails-without-this-culture-shift.html>)

Author: Akio Ueda

Published: 2026-09-17T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [digital](<https://devfeed.tech/topics/digital.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [adapting](<https://devfeed.tech/tags/adapting.md>), [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [change](<https://devfeed.tech/tags/change.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [digital-transformation](<https://devfeed.tech/tags/digital-transformation.md>), [digital-transformation-it-leadership](<https://devfeed.tech/tags/digital-transformation-it-leadership.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [organizational-culture](<https://devfeed.tech/tags/organizational-culture.md>), [psychological-safety](<https://devfeed.tech/tags/psychological-safety.md>)

### AI overview

The article argues that stalled digital transformation is often caused by organizational culture rather than technology. It recommends creating psychological safety so people can take risks, learn from failure, and adapt through an agile approach.

### Source excerpt

In companies where digital transformation (DX) isn't progressing as expected, the common barrier is not technology but the organization. You've introduced AI tools. You've organized your data. You've developed DX talent. Why aren't you seeing results? Could the reason be that the organizational culture hasn't been established where people feel safe to take on challenges and safe to fail? The essence of DX is transformation -- in other words, embracing change. The key players in adapting to that change are people, and DX will not move forward unless people take on the challenge. Especially in today's VUCA era, no one knows the right answer for how to manage a business or drive DX. There is no secret manual that guarantees success. It is commonplace for the goal to become obscured, change, or for the path to become interrupted while you're in the midst of the process. That is precisely why an agile approach is the best way to reach the true goal quickly: Try it first -> Fail more and faster than others -> Learn from failures and pivot quickly -> Turn that into growth But what is the reality within your organization? Is it: The person who speaks up gets the short end of the stick Failure leads to a lower performance evaluation New plans and proposals get rejected because there's no precedent or no other companies have done it? Elaborate plans are drawn up, but since no one wants to fail or take responsibility, the plans are never executed If such a negative, stagnant atmosphere prevails, it is quietly and surely robbing the organization of its spirit of challenge. As such, the greatest enemy of DX is not failure. It is stopping the pursuit of challenges. What exactly is organizational culture in the first place? What exactly is organizational culture in the first place? Since culture is something you can't see, don't you get the impression that it's elusive and difficult to improve? I, too, have seen and heard various definitions of the term organizational culture over the

## Nobody needs a human router

DevFeed: [Nobody needs a human router](<https://devfeed.tech/articles/nobody-needs-a-human-router-54745.md>)

Original publisher: [Read original article](<https://www.theengineeringmanager.com/growth/nobody-needs-a-human-router/>)

Author: James Stanier

Published: 2026-09-17T08:26:10Z

Content type: article

Language: en

Sources: [The Engineering Manager](<https://devfeed.tech/sources/the-engineering-manager-2.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Code](<https://devfeed.tech/topics/code.md>), [debugging](<https://devfeed.tech/topics/debugging.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [growth](<https://devfeed.tech/tags/growth.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [retrospectives](<https://devfeed.tech/tags/retrospectives.md>)

### AI overview

An article argues that engineering managers are increasingly expected to move beyond routing information and spend more time with technical details, contributions, decisions, and execution. It frames this shift in the AI age as a rediscovery of dormant technical skills rather than a need for entirely new skills.

### Source excerpt

Over the last decade, much has changed in the role of engineering management. Through the 2010s into the peak of Covid in 2021, for many, the role began to optimize for one thing. That one thing was moving information around. Managers translated context upwards from the team and decisions downwards from leadership, honing their craft [...] The post Nobody needs a human router appeared first on The Engineering Manager.

## Engineering managers are being asked to contribute more technically in the AI age

DevFeed: [Engineering managers are being asked to contribute more technically in the AI age](<https://devfeed.tech/articles/nobody-needs-a-human-router-42033.md>)

Original publisher: [Read original article](<https://theengineeringmanager.substack.com/p/nobody-needs-a-human-router>)

Author: James Stanier

Published: 2026-09-15T16:30:44Z

Content type: opinion

Language: en

Sources: [The Engineering Manager](<https://devfeed.tech/sources/the-engineering-manager.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [individual-contributor](<https://devfeed.tech/tags/individual-contributor.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [manager](<https://devfeed.tech/tags/manager.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [mentor](<https://devfeed.tech/tags/mentor.md>), [retrospectives](<https://devfeed.tech/tags/retrospectives.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [technical](<https://devfeed.tech/tags/technical.md>)

### AI overview

The article argues that engineering managers should move beyond primarily routing information through reports, meetings, and status updates. As organizations become flatter and tooling improves, managers are increasingly expected to engage deeply with technical details, contribute technically, and advance decisions and execution. The author frames this as a rediscovery of dormant individual-contributor skills, aided by AI tools.

### Source excerpt

We should do more than push information around.

## 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](<https://devfeed.tech/articles/what-is-bmad-understanding-the-bmad-loop-and-how-to-scale-it-12176.md>)

Original publisher: [Read original article](<https://www.port.io/blog/bmad-method-explained>)

Author: Yonatan Boguslavski

Published: 2026-09-01T08:40:17Z

Content type: tutorial

Language: en

Sources: [Port](<https://devfeed.tech/sources/developer-experience-platform-engineering-blog-port.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [AI Development](<https://devfeed.tech/topics/ai-development.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [development](<https://devfeed.tech/tags/development.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [review](<https://devfeed.tech/tags/review.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### 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.

## What Is an Agile Coach? Key Responsibilities and Business Impact

DevFeed: [What Is an Agile Coach? Key Responsibilities and Business Impact](<https://devfeed.tech/articles/what-is-an-agile-coach-key-responsibilities-and-business-impact-4491.md>)

Original publisher: [Read original article](<https://www.toptal.com/project-managers/agile/agile-coach>)

Author: ANTONIA MCCULLOUGH, AGILE COACH @ TOPTAL

Published: 2026-08-31T04:00:00Z

Content type: article

Language: en

Sources: [Toptal](<https://devfeed.tech/sources/toptal-blog.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [business](<https://devfeed.tech/tags/business.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [development](<https://devfeed.tech/tags/development.md>), [guide](<https://devfeed.tech/tags/guide.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [management](<https://devfeed.tech/tags/management.md>), [project-management](<https://devfeed.tech/tags/project-management.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

### 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](<https://devfeed.tech/articles/just-another-transformation-40042.md>)

Original publisher: [Read original article](<https://dpereira.substack.com/p/just-another-transformation>)

Author: David Pereira

Published: 2026-08-27T14:03:51Z

Content type: opinion

Language: en

Sources: [Untrapping Product Teams](<https://devfeed.tech/sources/untrapping-product-teams.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [digital](<https://devfeed.tech/topics/digital.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alignment](<https://devfeed.tech/tags/alignment.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [culture](<https://devfeed.tech/tags/culture.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [teams](<https://devfeed.tech/tags/teams.md>), [transformation](<https://devfeed.tech/tags/transformation.md>)

### 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)](<https://devfeed.tech/articles/ux-conference-november-announced-nov-9-nov-13-9045.md>)

Original publisher: [Read original article](<https://www.nngroup.com/training/november/>)

Published: 2026-08-24T06:48:00Z

Content type: article

Language: en

Sources: [NN/g latest articles and announcements](<https://devfeed.tech/sources/nn-g-latest-articles-and-announcements.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Agile](<https://devfeed.tech/topics/agile.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Information Architecture](<https://devfeed.tech/topics/information-architecture.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [event](<https://devfeed.tech/tags/event.md>), [information-architecture](<https://devfeed.tech/tags/information-architecture.md>), [interaction-design](<https://devfeed.tech/tags/interaction-design.md>), [training](<https://devfeed.tech/tags/training.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### 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](<https://devfeed.tech/articles/how-to-ensure-a-smooth-design-handoff-9061.md>)

Original publisher: [Read original article](<https://ixdf.org/literature/article/how-to-ensure-a-smooth-design-handoff>)

Author: Kasturika Kasturika

Published: 2026-08-19T10:00:00Z

Content type: article

Language: en

Sources: [UX Daily - User Experience Daily](<https://devfeed.tech/sources/ux-daily-user-experience-daily.md>)

Topics: [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Usability](<https://devfeed.tech/topics/usability.md>), [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [agile](<https://devfeed.tech/tags/agile.md>), [cc-by-sa](<https://devfeed.tech/tags/cc-by-sa.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [communication](<https://devfeed.tech/tags/communication.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [interaction-design](<https://devfeed.tech/tags/interaction-design.md>), [usability](<https://devfeed.tech/tags/usability.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [video](<https://devfeed.tech/tags/video.md>)

### 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...

## How the Best UX Design Teams Integrate Personas into Agile Workflows

DevFeed: [How the Best UX Design Teams Integrate Personas into Agile Workflows](<https://devfeed.tech/articles/how-the-best-ux-design-teams-integrate-personas-into-agile-workflows-9058.md>)

Original publisher: [Read original article](<https://ixdf.org/literature/article/how-the-best-ux-design-teams-integrate-personas-into-agile-workflows>)

Author: James Newhook

Published: 2026-08-08T04:00:00Z

Content type: article

Language: en

Sources: [UX Daily - User Experience Daily](<https://devfeed.tech/sources/ux-daily-user-experience-daily.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Product Management](<https://devfeed.tech/topics/product-management.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [churn](<https://devfeed.tech/tags/churn.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [revenue](<https://devfeed.tech/tags/revenue.md>), [ux](<https://devfeed.tech/tags/ux.md>), [ux-design](<https://devfeed.tech/tags/ux-design.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### 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...

## Agile design 101: How teams build better products faster

DevFeed: [Agile design 101: How teams build better products faster](<https://devfeed.tech/articles/agile-design-101-how-teams-build-better-products-faster-54776.md>)

Original publisher: [Read original article](<https://penpot.app/blog/agile-design-101-how-teams-build-better-products-faster/>)

Author: Paula Tienza

Published: 2026-08-06T18:04:45Z

Content type: tutorial

Language: en

Sources: [Penpot Blog](<https://devfeed.tech/sources/penpot-blog.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [iteration](<https://devfeed.tech/topics/iteration.md>), [development-process](<https://devfeed.tech/topics/development-process.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [Requirements](<https://devfeed.tech/topics/requirements.md>), [Self-organizing Team](<https://devfeed.tech/topics/self-organizing-team.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai](<https://devfeed.tech/tags/ai.md>), [beginners](<https://devfeed.tech/tags/beginners.md>), [design](<https://devfeed.tech/tags/design.md>), [development-process](<https://devfeed.tech/tags/development-process.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [iteration](<https://devfeed.tech/tags/iteration.md>), [product-development](<https://devfeed.tech/tags/product-development.md>), [products](<https://devfeed.tech/tags/products.md>), [rapid-prototyping](<https://devfeed.tech/tags/rapid-prototyping.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

A practical refresher on Agile design for cross-functional teams. It explains iterative sprints, user feedback, rapid prototyping, collaboration between designers and developers, and how AI and design systems are changing design practice.

### Source excerpt

Agile design itself is changing fast as AI upends how design gets practiced. This guide is a quick Agile design refresher, useful to revisiting the fundamentals.

## Managing 8 engineers now feels like managing 4 teams

DevFeed: [Managing 8 engineers now feels like managing 4 teams](<https://devfeed.tech/articles/managing-8-engineers-now-feels-like-managing-4-teams-39426.md>)

Original publisher: [Read original article](<https://www.blog4ems.com/p/product-is-the-new-bottleneck>)

Author: Stephane Moreau

Published: 2026-08-02T11:12:30Z

Content type: opinion

Language: en

Sources: [Blog for Engineering Managers](<https://devfeed.tech/sources/blog-for-engineering-managers.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [career-growth](<https://devfeed.tech/tags/career-growth.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [manager](<https://devfeed.tech/tags/manager.md>), [meetings](<https://devfeed.tech/tags/meetings.md>), [product](<https://devfeed.tech/tags/product.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

An engineering manager reflects that managing a team of eight engineers increasingly feels like managing four teams because the main bottleneck has shifted from engineering to product. The article contrasts this with an earlier model of clearly defined roles and collaborative roadmap planning.

### Source excerpt

The bottleneck moved from engineering to product.

## Agent Loops for Product Managers: Definitions, Stop Conditions, and Examples

DevFeed: [Agent Loops for Product Managers: Definitions, Stop Conditions, and Examples](<https://devfeed.tech/articles/agent-loops-for-pms-20-you-can-run-this-week-39180.md>)

Original publisher: [Read original article](<https://www.productcompass.pm/p/loop-engineering-for-pms>)

Author: Paweł Huryn

Published: 2026-06-22T15:15:49Z

Content type: tutorial

Language: en

Sources: [The Product Compass](<https://devfeed.tech/sources/the-product-compass.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Agile](<https://devfeed.tech/topics/agile.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [codex](<https://devfeed.tech/tags/codex.md>)

### 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](<https://devfeed.tech/articles/the-agile-trap-designers-fall-into-feeding-the-beast-9087.md>)

Original publisher: [Read original article](<https://uxmag.com/articles/the-agile-trap-designers-fall-into-feeding-the-beast>)

Author: Paivi Salminen

Published: 2026-06-18T04:35:20Z

Content type: article

Language: en

Sources: [UX Magazine](<https://devfeed.tech/sources/ux-magazine.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [components](<https://devfeed.tech/tags/components.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [design](<https://devfeed.tech/tags/design.md>), [design-system](<https://devfeed.tech/tags/design-system.md>), [design-systems](<https://devfeed.tech/tags/design-systems.md>), [interface](<https://devfeed.tech/tags/interface.md>), [teams](<https://devfeed.tech/tags/teams.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### 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.

[Next page](<https://devfeed.tech/topics/agile.md?cursor=WyIyMDI2LTA2LTE4VDA0OjM1OjIwKzAwOjAwIiwgImNhMjgxNGY1LWQzM2QtNDRjYS1iMGNlLWFhM2M3OTdiMjhmMSJd>)