Usually, you can decide on structure of code before implementing it. You can even have tests up and running before implementing it.
And in many cases this actually works.
Re:Scrum is the new waterfall
by dustinleblanc on Wednesday November 11, 2015 @11:42AM
(#10547515)
You can do agile test first too.
"hey here's a feature we're pretty sure we need:
As a foo, I need to bar, So that baz
okay, write the test, make the test pass, refactor"
What about that isn't possible in agile?
The Manifesto values Collaboration over "Contract Negotiation" leaving off the Negotiation part is a straw-man argument.
Similarly, "Responding to Change" it is not the Change that the Manifesto values it is "Responding to Change". What it values "Responding to Change" over is "Following a Plan" not making a plan or doing any planning.