FAQ

Does this replace Agile?

hydro just evolves on Agile for the AI era. Core values remain, but practices adapt. Dependency-driven waves instead of sprints, possibility expansion instead of story points.

How is this different from just adding AI tools to Agile?

Most approaches add AI as assistants to existing processes. hydro redesigns the entire workflow around AI capabilities, with an important focus on keeping AI right on track.

Quality, production-grade software requires adpated ways of work. AI assistants are powerful tools, but for a real resource orchestration, there's more to be done.

What AI tools do I need?

The methodology is tool-agnostic. Most teams use code-capable AI assistants like GitHub Copilot, Claude, or similar tools that can generate working code from specifications.

Is this only for new projects?

No. It works for new development, maintenance, and modernization projects. Any project with clear technical requirements and dependencies can benefit.

Especially mature projects pose very serious development chalanges in AI-generative world - limited context windows vs large repositories. hydro provides the tools and techniques to address complex situations.

What if our team resists changing from familiar processes?

Start with a pilot project to demonstrate benefits. Most developers appreciate focusing on architecture over implementation. Show results rather than requiring belief upfront.

---

Hydro Methodology © 2025 Licensed under Creative Commons Attribution 4.0 International (CC BY 4.0)