Some teams estimate based on effort.

Others use complexity.

And some… try both.

But which one actually helps your team plan better?

That depends on more than you think.

Here’s what we unpack in the full article:

Mike Cohn’s view:

Story points should reflect effort; how much total work a team can take on.

Eficode’s take:

Story points = complexity. Don’t tie them to hours or you lose their power.

Thoughtworks’ perspective:

Estimation should evolve. Mature teams often shift from points to flow metrics.

Whether your team’s early in its Agile journey or rethinking its rituals, this article breaks down:

✅ When to use effort vs. complexity

✅ How to avoid the trap of dual-tracking (points and hours)

✅ What SaaS teams can learn from experts and each other

✅ How tools like Rally let you flex your estimation model without adding chaos

Because the real question isn’t, “What’s the best metric?”

It’s: What works for your team right now?

Read the full article here: https://www.rallybetter.com/blog/effort-vs-complexity-choosing-the-right-estimation-metric-for-your-team/?utm_source=dev_to&utm_medium=rally_social