Software Development Agile Backlog Management

A Backlog Isn’t a To-Do List: Ivan Gekht on Product Clarity in Agile

Svetozar Eliseev

24 Oct 2024 — 1 min read

In its recent guide to the Product Backlog, Plaky breaks down the what and why of one of Agile’s core artifacts. But as Gehtsoft CEO Ivan Gekht often reminds teams—it’s not the format that matters. It’s the thinking behind it.

“A backlog is a living hypothesis about value. If it’s not pruned, it becomes fiction.”

At Gehtsoft, we treat the backlog not as a list of features, but as a strategic lens—one that reflects real constraints, risk, and evolving priorities. In regulated environments and zero-margin projects, clutter kills clarity. That’s why we push for:

Ruthless prioritization (even when it’s uncomfortable)
Acceptance criteria tied to real-world outcomes, not internal wishes
Regular backlog refactoring as an engineering task, not just PM overhead

Want Agile to actually deliver? Start with a backlog you can defend in front of a CFO—or a compliance officer.

Read the full article: Product Backlog 101 – Plaky

The Real Management Failure Is Not Lack of Frameworks. It Is Ideology Replacing Operational Judgment.

Over the last two decades, I have worked with organizations across very different environments: regulated finance, SaaS platforms, operationally constrained delivery, large engineering organizations, transformation programs, and Agile implementations at multiple scales. And one pattern appears repeatedly. Organizations stop managing operational reality and start managing management ideology. Sometimes the ideology

Risk Management under Real Velocity: Push Detection Downstream, Limit Blast Radius

I was recently quoted in a TechBullion article on balancing speed and security in business risk management. The core idea was simple: increasing business velocity does not remove the need for risk management. It changes its economics. This is not a technical nuance. It is a decision problem. At higher

AI and the missing first step in learning

What could be the long-term impact of AI on career progression in knowledge work? I saw a post recently asking whether AI will replace junior Scrum Masters. That question itself is not new. But it triggered a realization I had not connected this way before. And it is not very

Code Is No Longer the Bottleneck. Now What?

An advantage that everyone has is not an advantage. Agentic tools handle boilerplate, tests, and even non-trivial features. If your bottleneck was implementation speed, it's gone. Yet Amdahl's Law still applies: the speedup you get from accelerating one part is limited by the parts that don&

Read more

The Real Management Failure Is Not Lack of Frameworks. It Is Ideology Replacing Operational Judgment.

Risk Management under Real Velocity: Push Detection Downstream, Limit Blast Radius

AI and the missing first step in learning

Code Is No Longer the Bottleneck. Now What?

Cookie Settings