7 ms·
That is not Documentation that is Specification. How do you Document something that isn't built yet unless you have perfect foresight? Last I checked humans c
by rjspotter 11y ago
That is not Documentation that is Specification. How do you Document something that isn't built yet unless you have perfect foresight? Last I checked humans could not yet perfectly predict the future. Thus, the value of Working Software that can be interrogated and probed vs "Comprehensive Documentation" that may or may not be based on wishful prospection.
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.
- kuschku 11y agoUsually, 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.
- dustinleblanc 11y agoYou 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?