Ray ((Frankenstein))

Face-to-face communication and avoiding writing anything down has been used by tyrants and criminals for milennia to avoid dissemination of information. So lets use it when designing complicated software.

I was skeptical, but this point is devastating. Nothing written leaves a lot of room for gaslighting and assorted power games, which always skew towards privilege.

The worst #agile gaslighters are selective about what’s written down. They’ll want everything you do painstakingly documented in JIRA (so they can skewer you with it later) but they fall back on “we’re agile—lightweight process” when you ask that their actions leave a paper trail

You're aware that such behavior is in total contradiction to the agile manifesto?

And yet so intrinsic to scenarios with up/down power dynamics, which circles right back to @sarahmei ‘s point: agile/XP in stock form is broken for diverse/heterogeneous teams.

Caveat white dude speaking... I recognized agile as a power move by developers immediately upon first hearing about it. But it took this thread to point out how it only moves power between management and esteemed devs.

I think #agile on-paper has a non-understanding of the realities of software development in the same way communism on-paper had no understanding of human nature and capitalism on-paper has no understanding of compounded structural racism.

The whole point of agile was and is to *change* the realities of SD, to adapt it to the realities of how good software is developed. That most probably includes changing your team culture.