A large backlog cripples your product

Don't embrace unverified assumptions, embrace discovery

Back in the old days, we used to write thick requirement documents. We would seek stakeholder approval and after that, design and coding kicked off. Months later, we would deliver our functionality. Unsurprisingly, this functionality often did not do what our users wanted. Requirements were misinterpreted, resulting in functionality they didn’t want. Or…