Hacker News Reader

If your product iteration does not result in a potentially stoppable software, it's not True Scrum :TM: and you've failed.

View on HN

Not true. Delivery doesn't necessarily mean Release. Before the "Continuous Delivery" mantra took flight, Scrum et al came with Delivery Plans and, crucially as a separate artefact, a Release plan. This was specifically to address the nuanced distinction between a bunch of stuff being "done" and "releasable."

Now it seems everyone is unable to distinguish between Continuous Delivery and agility.

Even under Continuous Delivery there's still a distinction between "delivered" and "released". It might be delivered behind a feature flag. It might be delivered to a staging/release-planning environment of some sort. (CD doesn't always mean "completes all the way to Production each sprint". The original idea of CD was just focused on development and QA environments to catch what CI doesn't about the usability state of the application as different developer efforts merge together for the first time.)

> you've failed

Yes, and this is very common

> potentially stoppable

So this is a key difference. ShapeUp is much more focused on Actually Shipping vs `potentially`

Reply on news.ycombinator.com