Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

snarf21 posted elsewhere in this thread a perfect example. I'd like to refer to his Agile list as some other roles in the organization might see it.

"Value individuals and interactions over processes and tools"

Management - Processes and tools are exactly how we ran our business. It's the only way that scales (and is also lawsuit-proof!).

"Value working software over comprehensive documentation"

QA - How am I going to test that software if I don't have good documentation of what it needs to do and how it works? Documentation is necessary for working software, not something to be balance against working software.

"Value customer collaboration over contract negotiation"

Management - We do need to get paid you know. On that matter, our interests are not exactly aligned with the customer's. Furthermore, having clear expectations and legal protections for both sides is a form of collaboration, a necessary one in fact.

"Value responding to change over following a plan"

Investors - Ah, so you're just following the market and have no intention of initiating change on your own? How is your company going to be the next Apple if you keep up like that?

I'm not necessarily saying the other characters are right - but these perspectives are a given in today's organization and are going to influence the actual process. Indeed, given that managers have more power, these are going to be the defining influences, way over some manifesto.



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: