A Two-Week Sprint for Knowledge

· Source: Intentional Arrangement · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Project & Product Management · Depth: Advanced, long

Summary

The article argues that Agile and Scrum methodologies, originally developed for manufacturing and software development during the Third Industrial Revolution, are fundamentally ill-suited for complex knowledge work and the demands of the Fourth Industrial Revolution. It highlights that Scrum assumes "tame problems" with discrete, additive components, whereas knowledge organization involves "wicked problems" that defy definitive formulation and require continuous exploration rather than efficient delivery of known requirements. The author proposes that Design Thinking, with its recursive approach to problem discovery, and the disciplined, patient work of building semantic infrastructure (like controlled vocabularies, taxonomies, and ontologies) are more appropriate frameworks. Furthermore, Large Language Models (LLMs) are categorized as information-processing tools that only become "knowledge tools" when grounded in semantic layers providing meaning and provenance, a process that cannot be achieved through short sprints. Ultimately, knowledge creation is presented as a spiral, not a sprint, demanding foundational epistemological alignment and infrastructure, which constitutes a strategic "moat" that Agile cannot build.

Key takeaway

Agile/Scrum, optimized for manufacturing and software, is fundamentally misapplied to the "wicked problems" of knowledge work, semantic systems, and AI. Its sprint-based, additive increment model fails to build coherent knowledge components like ontologies, leading to inconsistent systems and AI hallucinations without proper grounding and provenance. Professionals should adopt Design Thinking and Library & Information Science principles, such as the Ontology Pipeline™, to foster innovation and create robust, explainable knowledge infrastructure.

Topics

Best for: AI Product Manager, AI Architect, Director of AI/ML, Consultant

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Intentional Arrangement.