These days business activities are changing at very rapid rate and there are increasingly complex requirements set on programming solution that puts traditional software development methods (also called heavyweight) at the rear and leads to the need for other development practices which can overcome the problem of software crises. Modern approaches, also known as agile or lightweight methodologies, claim to provide solution to above said problem. Heavyweight methodologies, commonly known for its traditional ways to develop software put emphasis on comprehensive planning, detailed documentation, and expansive design. Unlike traditional methods, agile methodologies employ short iterative cycles, and rely on tacit knowledge within a team. Knowledge Management (KM) can be easily accepted into agile software development environments. Following are two reasons in favor of this point of view. First, the agile cultural infrastructure already encourages values such as cooperation, communication and knowledge sharing; specifically, agile software development processes include some practices that support KM, e.g. stand-up meetings, the planning game, pair programming and the informative workplace. Second, KM is about learning, and ASD set up an environment that supports learning processes. In this paper, attempt is made to find out specific agile practices which promote KM.

1. Beck, M. K. 1999 Embracing change with Extreme Programming. IEEE Computer, Vol. 32.
2. Awad, M. A. 2005 Comparison between Agile and Traditional Software Development Methodologies, Honours Programme Thesis, University of Western Australia.
3. Fowler, M. 2000 The New Methodology , http://www.martinfowler.com/articles/newMethodology.html accessed on 11.11.11
4. Lycett, M. Macredie, R. Patel, C. and Paulk, R. J. 2003 Migrating Agile Methods to Standardized Development Practice, Computer, Vol. 36, issue 6, pp. 79-85.
5. The CHAOS Report, 1994 www.standishgroup.com/sample_research/chaos_1994_1.php, accessed on 15.10.11
6. Glass, R. L. 2001 Agile Versus Traditional: Make Love, Not War, Cutter IT Journal, Vol. 14, No. 12, pp12-18.
7. Agile Alliance 2001 Manifesto for Agile Software Development, www.AgileAlliance.org accessed on 12.11.11
8. Highsmith, J. Orr, K. and Cockburn, A. 2000 Extreme Programming, E- Business Application Delivery, pp. 4-17
9. Job Trends www.indeed.com/jobtrends?q=agile%2C+scrum%2C+%22extreme+programming%22%2C+%22test+driven%22&l=,accessed on 11.11.11
10. Tudor, D.2006 An update on Agile methods, ITadviser, Issue 56.
11. Highsmith, J and Cockburn, A. 2001 Agile Software Development: The Business of Innovation, Computer, Vol. 34,No. 9, pp. 120-122.
12. Desouza, K.C. 2003 Barriers to effective use of knowledge management systems in software engineering, Communications of the ACM, Vol; 46 (1). pp 99–101.
13. Disterer, G. 2002 Management of project knowledge and experiences, Journal of Knowledge Management Vol. 6 (5) pp. 512–520.
14. Davenprot, T. H. Prusak, L.1998 Working Knowledge: how organizations Manage what they Know, Harvard Business School Press, Boston, USA.
15. Tiwana, A, 2000 The Knowledge Management Toolkit, Upper Saddle River, NJ: Prentice Hall PTR, Prentice-Hall, Inc.
16. Nonaka, I. 1986 A Dynamic Theory of Organizational Knowledge Creation, Organization Sciences, Vol. 5(1), 1986, pp. 14-37.
17. Spender, J. C. 1998 Pluralist Epistemology and the Knowledge-Based Theory of the Firm, Organization, Vol. 5(2), pp. 233-256.
18. Aurum, A. Jeffery, R. Wohlin, C, and Handzic, M. (Ed.), 2003 Managing Software Engineering Knowledge, Springer-Verlag, New York.
19. Hansen, M.T., Nohria, N. and Tierney, T. 1999 What's Your Strategy for Managing Knowledge?, Harvard Business Review, March/April, pp106-116 Jashapara, A. (2004) Knowledge Management, Prentice Hall.
20. Abou-Zeid, E. S. 2002 A knowledge management reference model. Journal of Knowledge Management, Vol. 6(2) pp. 486-499.
21. Manville, B. 1999 Complex adaptive knowledge management, in The Biology of Business, J.C. III, Editor. 1999, Jossey-Bass: San Francisco. pp 89-111
22. Bonifacio, M. Bouquet, P. and Traverso, P.2002 Enabling Distributed Knowledge Management: Managerial and Technological Implications. Novatica and Informatik/Informatique, Vol. 3(1) pp, 22-29
23. Boehm, B. and Turner, R. 2004 Balancing Agility and Discipline, Addison-Wesley.
24. Hazzen, O. Levy, M. 2009 Knowledge Management in Practice:The Case of Agile Software Development. In Proceeding of ICSE Workshop on Cooperative and Human Aspects on Software Engineering.
25. Hazzan, O. and Dubinks . 2008 Agile Software Engineering, Undergraduate Topics in Computer Science (UTiCS) Series, Springer.
26. Ding, W. and Marchionini, G. 1997 A Study on Video Browsing Strategies. Technical Report. University of Maryland at College Park.
27. Fröhlich, B. and Plate, J. 2000. The cubic mouse: a new device for three-dimensional input. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
28. Hazzan, O. and Dubinsky, Y. 2003. Teaching a Software Development Methodology: The Case of Extreme Programming, In proceedings of the 16th International Conference on Software Engineering Education and Training, Madrid, Spain, pp. 176-184.
29. Bennet, D. and Bennet, A. 2003 The Rise of the Knowledge Organisation, chapter 1 in Holsapple, C.W. (ed.), Handbook on Knowledge Management,Vol 1, Springer, Berlin, pp. 5–20.
30. Reifer, D. J. 2002 How to Get the Most out of Extreme Programming/Agile Methods , In proceeding Proc. Extreme Programming and Agile Methods - XP/Agile Universe
31. Dove, R. 1999 Knowledge management, response ability, and the agileenterprise", Journal of Knowledge Management, Vol. 3 Iss: 1, pp.18 - 35
32. Harald Holz, Melnik, G. Schaaf, M.: Knowledge Management for Distributed Agile Processes: Models, Techniques, and Infrastructure. WETICE 2003 pp 291-294
33. Spek, R. Kruizinga, E Annelies Kleijsen, 2009 Strengthening lateral relations in organisations through knowledge management, Journal of Knowledge Management, Vol. 13 Iss: 3, pp.3 – 12
34. Version one, 2008 3rd Annual Survey: The State of Agile Development, www.versionone.com/pdf/3rdAnnualStateOfAgile_FullDataReport.pdf.
35. Version one, 2007 Agile development: Result Delivered, http://www.versionone.net/pdf/AgileDevelopment_ResultsDelivered.pdf.
36. Versiion One, 2009 4th Annual Survey 2009, www.versionone.com/agilesurvey.
37. Avison, D.E. and Fitzgerald, G. 1995. Information Systems Development: Methodologies, Techniques and Tools. 2nd ed., Maidenhead: McGraw Hill
38. Beck, K. 1999 Extreme programming explained: embrace change, Addison-Wesley Longman Publishing Co., Inc. Boston, MA, USA
39. Schwaber, K. and Sutherland, J. 2011 The Scrum Guide, www.scrum.org/storage/scrumguides/Scrum%20Guide%20-%202011.pdf

Scrum Extreme Programming Knowledge Sharing