Knowledge Management in Distributed Agile Software Development
2 likes1,961 views
This document summarizes research on knowledge management processes in distributed agile software development teams. It identifies four key knowledge management processes: knowledge generation, codification, transfer, and application. Knowledge generation occurs through activities like customer collaboration, training, and self-learning. Codification involves documenting knowledge in wikis and other documents. Knowledge is transferred between teams through daily stand-up meetings, pair programming, tools, visits, and rotations. Finally, knowledge is applied to problem-solving and improving future sprints. The research was based on interviews with practitioners from various countries and used grounded theory to analyze the results.
Knowledge Management in Distributed Agile Software Development
- 1. Knowledge Management in Distributed Agile Software Development Siva Dorairaj, James Noble and Petra Malik , VUW @Agile Conference, 2012 Speaker: Kir Chou, NCU 1
- 2. Goal Knowledge Management : how Agile teams gather, store, share and use knowledge Distributed : in different location Agile Software Development 2
- 3. Define Knowledge Tacit Knowledge •openly expressed •action-oriented Explicit Knowledge •in written, verbal forms •academic knowledge 3 KM : manage both in individuals of organizations. Know how Know what
- 4. Research Method Grounded Theory (GT) suitable to be used in areas that are under-explored study social interactions and behaviour of people Why is GT? literature of agile method is still scarce agile method focus on people Distributed started with a general area, rather than specific area 4
- 5. Research Context 45 people from 28 companies 5 Position Scrum Master, Agile Coach, Developer, Business Analyst, Quality Analyst, Product Owner, Senior Management Location USA, Western Europe, India, Australia, China, UK, Argentina, Japan Team size Small team: 7~30 Big team: more than 50 Duration (Months) 6~24 (including ongoing) Iteration (Weeks) 1~3
- 6. Research Know How Open-ended question how to overcome challenges of distributed agile team Ongoing analysis guided the future questions 6 0. Transcribed text 1. Code 2. Concept 3. Category Key point GT’s constant comparison method constant comparison method
- 8. 1. Knowledge Generation divided into two main sub-processes: knowledge creation exists within the individuals knowledge acquisition acquired from external sources 8
- 9. Knowledge Generation -1 1. Inception *with clients shared vision prepares development team 2. Customer collaboration improves communication with development teams enhance knowledge creation 9 Before start After start
- 10. Knowledge Generation -2 3. Formal training *soft & technic skills standardize training content across multiple teams 4. Communities of practice across multiple projects 5. Self-learning *peer & community learning learning takes time 10
- 11. Knowledge Codification Translation of tacit into explicit knowledge 11
- 12. Knowledge Codification-1 1. Wiki *comment bug a collection of web pages knowledge creation in the team facilitate individual learning 2. Documents *test cases, design for using, maintaining and evolving agile methods reduce the emphasis on documentation 12 Frequent Infrequent
- 13. Knowledge Codification-2 3. Presentation sharing of valuable ideas content can be captured and stored 13
- 14. Knowledge Transfer Movement of knowledge from sender to receiver not guarantee a full replication often modified 14
- 15. Knowledge Transfer -1 1. Daily Scrum *valuable information synchronize possible impediments schedule other meetings 2. Inception a small team is formed documents 15 Before start
- 16. Knowledge Transfer -2 4. Pair programming *junior + senior knowledge dissemination & retention in organization 5. Tools conserve and distribute knowledge gathered 16
- 17. Knowledge Transfer -3 6. Visits critical situations need effective knowledge sharing 7. Rotation *specific knowledge knowledge gap between offshore & on-site 8. On-site customer continually providing their needs domain concerned knowledge 17
- 18. Knowledge Transfer -4 9. Cross-functional teams focus on the whole solution 10. Discussions subject matter experts 18 RD Team Client Expert
- 19. Knowledge Application Using knowledge to create and sustain competitive advantage in organizations 19
- 20. Knowledge Application 1. Similar Context *wiki similar project-context activities 2. Problem Solving *wiki consolidate and understand related information 3. Future Sprint/Projects *Scrum tunes and adjusts behaviour of members accordingly review and retrospectives meetings 20
- 21. Limitation By GT, author don’t claim that… their findings are universally generalisable to all distributed Agile projects. 21
- 22. Conclusion Agile method, Scrum and XP have KM.... Knowledge required is Context-dependent and is difficult to transfer and store context Critically analyzing the knowledge before reuse 22
- 23. Thank you 23