Good news everyone! My magnum opus on Scrum just dropped, clocking in at almost 9K words! Prepare a drink, strap yourselves in, and enter the Torment Nexus.
https://ludic.mataroa.blog/blog/tossed-salads-and-scrumbled-eggs/
Good news everyone! My magnum opus on Scrum just dropped, clocking in at almost 9K words! Prepare a drink, strap yourselves in, and enter the Torment Nexus.
https://ludic.mataroa.blog/blog/tossed-salads-and-scrumbled-eggs/
@ludicity "Instead I believe that Scrum and the assorted mutations that it has acquired simply reflect a broader lack of understanding of the systems that drive knowledge work, and the industry has simply adopted the methodology that slots most neatly into our most widely-held misconceptions."
Dicaprico-pointing.gif
Dysfunctional knowledge work (and lack of "awareness of the meta" about knowledge work) feel like a root cause in so many issues; the whole AI-at-work also.
@ludicity Sometimes it also feels like there‘s a meta about the meta. (That‘s an ilusion - knowledge work is simply recursive. You can knowledge work about knowledge work. It‘s like the distilled formalism of self-awareness.)
But belike, for work, doing knowledge work - why are you doing it? What motivates the questions that need answering? What needs demand knowledge work, and why do the things making these needs exist on the business?
@Sevoris I asked someone yesterday if I should codify some norms that had developed in a community. They said I don't need to write the norms down because they're evident in the culture, and I've been sliding down a rabbit hole of "Culture is self-describing". This makes me think of that as well.
Maybe this also illustrates why some people "get it" and some people don't. When I say someone "gets it", I just mean they're in the knowledge work metagame.