Hacker News Reader

Don't distract. I'm genuinely trying to help us figure out how to build quality software, using AI, while avoiding all the problems we're seeing on so many teams.

View on HN

No distraction. Genuine question. The whole point of the Agile Manifesto is to encourage removal of VP and similar roles from an organization; turning to a flat organizational structure. What motivates you, a VP, to latch onto that? How do you think that will help (with or without amendments)? Do you, perhaps, think in the age of AI your org will be better off if you 'step down' into a development/AI steerer role?

I was around when the agile manifesto was drafted. It wasn't about eliminating hierarchy in organizations. That's something that started happening later, around and after 2010. The agile manifesto was singularly focused at helping people see how to deliver software without leaning on the old waterfall methodologies.

The Agile Manifesto was published in 2001. You asserted earlier your software career began in 2006. What brought you to the Wasatch Mountains at that time when you had no ties to the industry?

Winston Royce, in his book, invented the waterfall methodology as a hypothetical of what not to do in order to help explain his core thesis. It is not a real thing. Why do you suggest the Agile Manifesto was created to help avoid leaning on a strawman?

Reply on news.ycombinator.com