Yeah. Which actually doesn’t have to be bad as long as leadership accepts that this exploratory work (sometimes called a “spike”) might have to be thrown away, if findings reveal better paths.
The trouble begins when you start shipping your proof-of-concepts (without immediately paying back that tech debt).
The few times I’ve been on an agile project it amounted to start writing without understanding what product we’re building.
Yeah. Which actually doesn’t have to be bad as long as leadership accepts that this exploratory work (sometimes called a “spike”) might have to be thrown away, if findings reveal better paths.
The trouble begins when you start shipping your proof-of-concepts (without immediately paying back that tech debt).
It very quickly becomes an unmaintainable mess.