Hi Randy, thanks for your comment, but I disagree. There are several principles and values in the Agile Manifesto that are inclusive of repeated revision of a feature including:
- Welcoming changing requirements, even late in the process, and harnessing change.
- Architectures, requirements and designs emerging.
- Responding to change over following a plan.
Whilst not explicitly saying "thou must repeat", they do all suggest that changes will come late, and responding to those changes is important.
However, the Lean Startup makes the idea of repeating and pivoting quite explicit.
I agree that at some point you switch over from pragmatism to perfectionism, and this needs to be balanced. But almost all creative work improves after a few iterations or revisions, including writing documents, painting, music, and writing software. If you only ever build each feature once and only once, then almost certainly each feature is sub-optimal in some way - just the same as any of the other creative works I mentioned.
You might also find a couple of previous articles of mine interesting reading:
https://medium.com/catum/i-iterate-therefore-i-am-cae07f77630c
