I'm not sure you realize all that Agile gave you that you described: kanban, a direction and goal, self-organized, iterative builds, I assume version control, d

I'm not sure you realize all that Agile gave you that you described: kanban, a direction and goal, self-organized, iterative builds, I assume version control, daily builds possible, in front of stakeholders, adjust, repeat, necessary documentation. Probably in DevOpsy environments built regularly. Before and outside Agile we had months of requirements gathering, nominally with stakeholders, months of break-down and design (by a different set of individuals, barely seen by stakeholders), and then devs would march to the Gantt chart. We were lucky that "make" would be successful in our own component most days, integration test with other major components were on an ad-hoc basis. Version control? Backups, if lucky. Somewhere near the end of that Gantt chart we would start "testing" by hand-delivering hand-built components to the test systems. After testing we would build for delivery. What? That step wasn't on the plan? Oops. Hand-deliver to production. Oh, and don't ever mess around on those systems because no one knows how they were built or updated. That most teams these days do pervasive version control, iterative build, regular delivery, and system builds is simply a massive transformation of the industry. The Lean Methodology folks were on the right track but they never delivered usable, actionable practices until the Agilists started documenting them.