Agile is knowledge-sensitive. Knowledge feeds the entire adaptive life cycle from envision to transition. Main agile frameworks (i.e., SAFe®), toolkits (i.e., DA® – Disciplined Agile) and standards (i.e., PMBOK® 7th Edition) underline in different ways and at different levels of detail the relevance of knowledge for generating business value. So, all right? Everything is fine? Are we on the same page? In principle yes, but there are three main knowledge lacks: implicit knowledge, knowledge framework, knowledge roles/responsibilities. Therefore, negative effects are determined at different ontological levels: project performance, team dynamics, personal development. Presently, the agile landscape shows a relevant awareness of the topic of knowledge. However, this awareness is fragmented, ambiguous in key concepts, poorly addressed, even misleading in some cases. Knowledge in the agile environment is too often a fuzzy topic. The self-dimension of an agile team (self-directing, self- organizing, self-learning, self-empowering) erroneously assumes that knowledge is well addressed, wasting time, money, resources, decreasing performance and results. This paper provides a practical framework and tips for avoiding these negative effects. The AKP® – Agile Knowledge Projector might be a practical solution for better addressing knowledge in an agile project environment, improving value. AKP® is an organizational framework that fosters the creation of a dynamic mix of knowledge, combining in a continuous way explicit organizational artifacts, implicit team patterns and tacit individual expertise, for the entire duration of the agile project. AKP® consists of nine processes, focused on main agile dynamics of a complex and innovative project. AKP® is a powerful but not self-regulated framework: thus, it needs to be carefully designed and administered, according to specific knowledge roles and rules.
Read full abstract