Codified vs. Personalized – A Vertical Approach to the Dilemma of the Knowledge Management Strategies EuroSPI Grenoble, France September 2 nd , 2010 Karsten Jahn, jahn@cs.aau.dk Peter Axel Nielsen, pan@cs.aau.dk
Introduction Sharing of knowledge / experience is fundamental part in software process improvement Knowledge management depends on organization’s strategy Tools support one strategy only Dilemma:  Different strategies on different organizational levels
Knowledge Management Strategies Hansen et al. 1999 codification personalization Document driven Linking people Reports Meetings Formalization Communication Focus on reuse of codified knowledge Focus on finding individual expertise Specialization Flexibility ERP Wiki
The Case Logica Denmark IT and business solutions 800 Specialists in five Danish cities Many very different projects huge amount of rules, guidelines and processes Two main knowledge management problems: Large gap between process definition and implementation Different project settings cause many isolated islands of information
Design: The Two Tier KMS Top management layer needs codification to follow processes and guidelines Reporting, analyzing and planning documents Development layer depends on the people’s skills and their connection Who knows what, how can what be solved, etc. Project manager organizes information exchange between the layers
Design: The KiWi Systems Project Management Application ERP System Manager access only Data Exchange Agent Synchronizes data between the other systems Manager access only KiWi Platform Enhanced Wiki Access for whole team
Conclusion Main knowledge management problems adressed: Direct feedback bridges gap  between process definition and implementation Global wiki simplifies information access Vertically partitioned organization supports two strategy approach: Top management level continues processes compliance Development team gains support for communication Project manager has direct access on team’s input

Codified vs. Personalized – A Vertical Approach to the Dilemma of the Knowledge Management Strategies

  • 1.
    Codified vs. Personalized– A Vertical Approach to the Dilemma of the Knowledge Management Strategies EuroSPI Grenoble, France September 2 nd , 2010 Karsten Jahn, jahn@cs.aau.dk Peter Axel Nielsen, pan@cs.aau.dk
  • 2.
    Introduction Sharing ofknowledge / experience is fundamental part in software process improvement Knowledge management depends on organization’s strategy Tools support one strategy only Dilemma: Different strategies on different organizational levels
  • 3.
    Knowledge Management StrategiesHansen et al. 1999 codification personalization Document driven Linking people Reports Meetings Formalization Communication Focus on reuse of codified knowledge Focus on finding individual expertise Specialization Flexibility ERP Wiki
  • 4.
    The Case LogicaDenmark IT and business solutions 800 Specialists in five Danish cities Many very different projects huge amount of rules, guidelines and processes Two main knowledge management problems: Large gap between process definition and implementation Different project settings cause many isolated islands of information
  • 5.
    Design: The TwoTier KMS Top management layer needs codification to follow processes and guidelines Reporting, analyzing and planning documents Development layer depends on the people’s skills and their connection Who knows what, how can what be solved, etc. Project manager organizes information exchange between the layers
  • 6.
    Design: The KiWiSystems Project Management Application ERP System Manager access only Data Exchange Agent Synchronizes data between the other systems Manager access only KiWi Platform Enhanced Wiki Access for whole team
  • 7.
    Conclusion Main knowledgemanagement problems adressed: Direct feedback bridges gap between process definition and implementation Global wiki simplifies information access Vertically partitioned organization supports two strategy approach: Top management level continues processes compliance Development team gains support for communication Project manager has direct access on team’s input

Editor's Notes