Skip to content

Comment on Ask HN: Is it time to retire Agile?parent

Comments

I like this analysis. It looks like instead of Agile we need Fluid.

Technically speaking, you have an equation where the number of variables is too high to successfully optimize against.

From a business point of view you need to have one person or a team that:

- Knows the organization very well.

- Knows the industry very well.

- Knows the domain and the problem very well.

- Knows the tech very well.

- Has the history of what was tried and what worked.

- Has the authority and an exceptional organizational abilities to analyze and improve the process all the time.

- Has exceptional people skills and a sense of rhythm to not increase the attrition by introducing changes too often.

When you frame it this way you see that the problem of designing the right process is really hard. You need to recognize the context and then create an ad-hoc process to fit that context. And keep optimizing.

People rely on frameworks and systems and you offer them none. It's like offering programmers switching from functional, to procedural, to OOP, to logical, to pen and paper all the time.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.