Thanks lr4444lr for highlighting and aligning the various principles the Agile manifesto with the minutiae details of the project I described. I definitely see

Thanks lr4444lr for highlighting and aligning the various principles the Agile manifesto with the minutiae details of the project I described. I definitely see your point (which I interpret as Agile is not a set of rigid techniques but one can adapt a team's makeup and culture to whatever will make software people feel motivated/empowered to do the work and have quick responsive/iterative cycles with the customer folks). >Presuming that you're delivering more responsively and quickly to the customer than you were before, which you didn't mention In the interest of full disclosure, I think we had a project time over-run of 2x (estimated 4 months to 8 months) mainly due to "feature creep" (is that a feature or a bug in Agile iterative cycles?); the project is a high-throughput data pipeline for genome sequencing and annotation. We overran time as a case of our customers/users wanted to add more bells and whistles to the tail end of the pipeline as they saw the end product more and more and proposed more added steps.