Good practices to accelerate agile team knowledge sharing by Mikhail Podurets
•Download as PPTX, PDF•
5 likes•1,467 views
Next webinars: http://www.luxoft.com/agile-lean-webinars-schedule Video: https://youtu.be/LfmCUxfk988 We all are the knowledge workers. When we manage, write code, test code, create architecture or plan the project we work more with our brains rather than with our hands. In this case the availability of knowledge and expertise, the understanding of team members’ experiences, competences and commitments is vital for the project success. This webinar covers the ways to better knowledge sharing: * Tacit and explicit knowledge * Good practices for Agile documentation * Practices to make knowledge explicit like code review, pair programming and the community of practice * Information refrigerators and radiators
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (10)
Similar to Good practices to accelerate agile team knowledge sharing by Mikhail Podurets
Similar to Good practices to accelerate agile team knowledge sharing by Mikhail Podurets (20)
More from LuxoftAgilePractice
More from LuxoftAgilePractice (20)
Recently uploaded
Recently uploaded (14)
Good practices to accelerate agile team knowledge sharing by Mikhail Podurets
- 1. www.luxoft.com GOOD PRACTICES TO ACCELERATE AGILE TEAM KNOWLEDGE SHARING Luxoft Agile Practice Webinar Part of ICAgile ICP Certification Mikhail Podurets
- 2. www.luxoft.com Mikhail Podurets Agile/Lean Coach @ Luxoft Agile Practice mpodurets@luxoft.com Mikhail.Podurets Mikhail-Podurets
- 3. www.luxoft.com The International Consortium for Agile (ICAgile) http://www.icagile.com
- 4. www.luxoft.com Topics to Discuss COST OF DOCUMENTATION CREATION AND MAINTENANCE GOOD PRACTICES FOR AGILE DOCUMENTATION EXPLICIT AND TACIT KNOWLEDGE PRACTICES FOR SHARING TACIT KNOWLEDGE
- 5. www.luxoft.com What Is It All About We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. http://agilemanifesto.org/ Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 7. www.luxoft.com The Costs of Documentation Creation and Maintenance
- 8. www.luxoft.com Good Practices for Agile Documentation
- 9. www.luxoft.com Agile Docs Good Practices: Executable Specs Prefer Executable Specifications Over Static Documents. Requirements can be captured as “executable documentation” in the form of the test.
- 10. www.luxoft.com Agile Docs Good Practices: Simplicity Keep Documentation Just Simple Enough, but not Too Simple. The best documentation is the simplest that gets the job done.
- 11. www.luxoft.com Agile Docs Good Practices: Information Radiator Display Information Publicly. Whiteboard, corkboard, internal video site. Transfer information through the application of Information Radiator.
- 12. www.luxoft.com Agile Docs Good Practices: Golden Source Golden Source. Keep all relevant documentation in one known place that everyone has an access. We also suggest using wiki and social engines for easy collaborative editing and sharing.
- 13. www.luxoft.com Explicit And Tacit Knowledge
- 14. www.luxoft.com Tacit Knowledge vs. Explicit Knowledge Codifiability and mechanism of transferring knowledge. Tacit knowledge is intuitive and unarticulated knowledge cannot be communicated, understood or used without the ‘knowing subject’. Main methods for the acquisition and accumulation. Tacit knowledge can only be acquired through practical experience in the relevant context. Potential of aggregation and modes of appropriation. Tacit knowledge is personal contextual. It is distributive, and cannot easily be aggregated.
- 15. www.luxoft.com Pair Programming Tacit to Tacit knowledge transition Two programmers code together at one workstation. Driver types code, and observer reviews and criticizes it Roles are switched periodically Pair programming is NOT mentoring, even if one is significantly more experienced
- 16. www.luxoft.com Code Review Tacit to Explicit knowledge transition Explicit to Tacit knowledge transition Improve code quality Share knowledge Improve code ownership Check conformance Verify completeness Educate Reach a consensus Try other approaches
- 18. www.luxoft.com Community of Practice (CoP) A community of practice is a like- minded or like-skilled group of individuals Primary mechanism for spreading good ideas among teams The most effective type of community of practice is one that forms organically
- 20. www.luxoft.com Luxoft Agile Practice Trainings ICAgile Certified Professional - Agile Fundamentals https://icagile.com/icagile-certified-professional ICAgile Certified Professional - Business Value Analysis https://icagile.com/icp-business-value-analysis ICAgile Certified Professional - Agile Team Facilitation https://icagile.com/icp-agile-team-facilitation Professional Scrum Master https://www.scrum.org/Courses/Professional-Scrum-Master Management 3.0 https://management30.com/events/two-day-course/ Custom Workshops Registration and more info at agile@luxoft.com www.luxoft.com/agile
- 21. www.luxoft.com Next Webinar of Luxoft Agile Practice The Path to grow high-performing Scrum teams by Vyacheslav Moskalenko When: October 30th, 2015 To apply: http://www.luxoft.com/events
Editor's Notes
- Get back to the ICAgile personal development directions and mention Master Agilist as a perfect example of a skillful T-shaped person, mastering some areas at Ri level while having Shu or Ha level knowledge in others.
- Return back to Agile Manifesto and have a look at the 2th Value Have a discussion with participants. Ask them what they mean under comprehensive documentation and why working software is more important. We can remind again about the myth that Agile does not support documentation
- Full description of Tacit Knowledge can be found here: http://en.wikipedia.org/wiki/Tacit_knowledge Codifiability and mechanism of transferring knowledge: while explicit knowledge can be codified, and easily transferred without the knowing subject, tacit knowledge is intuitive and unarticulated knowledge cannot be communicated, understood or used without the ‘knowing subject’. Unlike the transfer of explicit knowledge, the transfer of tacit knowledge requires close interaction and the buildup of shared understanding and trust among them. Main methods for the acquisition and accumulation: Explicit knowledge can be generated through logical deduction and acquired through practical experience in the relevant context. In contrast, tacit knowledge can only be acquired through practical experience in the relevant context. Potential of aggregation and modes of appropriation: Explicit knowledge can be aggregated at a single location, stored in objective forms and appropriated without the participation of the knowing subject. Tacit knowledge in contrast, is personal contextual. It is distributive, and cannot easily be aggregated. The realization of its full potential requires the close involvement and cooperation of the knowing subject.
- No need in instructor’s guide, everything is obvious here, I hope )))
- http://www.slideshare.net/alimenkou/code-review-4350089
- http://www.unusual-concepts.ru/blog/2011/11/развиваем-кроссфункциональность/ http://www.smartagilee.com/2013/03/blog-post.html
- http://www.mountaingoatsoftware.com/blog/cultivate-communities-of-practice