> to plan everything out in detail and start building it all at once very rarely works, is expensive, slow and can’t handle changing requirements. And requireme

> to plan everything out in detail and start building it all at once very rarely works, is expensive, slow and can’t handle changing requirements. And requirements always change. I’m struggling with the opposite. 90% of what we have to do is realizing requirements we get from externally (our competitors get the same requirements more or less). We can only release an update when we have done all the external requirements. Still we’re supposed to be an agile company so you don’t work directly with the external requirements but a project manager creates a stream of work items, so you never have the time to try to get the big picture. Most of the time you don’t know what you have to create and working in increments makes sense to find that out. But there’s also stuff that you can plan for ahead. If you don’t you will end up with a worse product and you will also drive people mad.