Extreme knowledge (XK) is an approach to learning, working and product delivery that follows principles & practices in extreme programing (XP). The intent is to reduce time to delivery, reduce risk, improve learning, reduce errors and promote understanding.
XK improves knowledge work in four essential ways; communication, simplicity, feedback, and courage. XK workers communicate with their customers and fellow knowledge workers. They keep their design open, simple and clean. They get feedback by testing their products starting on day one. They deliver their product to the customers as early as possible and implement changes as suggested. With this foundation XK workers are able to courageously respond to changing requirements and technology.
XK / XP "requires an extended development team. The XP team includes not only the developers, but the managers and customers as well, all working together elbow to elbow. Asking questions, negotiating scope and schedules, and creating functional tests require more than just the developers be involved in producing the software".
Extreme Programming (XP) was created in response to problem domains whose requirements change. Your customers may not have a firm idea of what the system should do. You may have a system whose functionality is expected to change every few months. In many software environments dynamically changing requirements is the only constant. This is when XP will succeed while other methodologies do not.
For my money, knowledge workers will greatly benefit by following XP practices and principles as these promote tacit knowledge transfers, foster learning and trust, leading to greater understanding, awareness and agility.Resources:
Do you have any XK experiences to share?