Knowledge sharing is an important, but usually ignored activity because of time and effort required are hardly available; especially the documentation based knowledge sharing approaches have hard time gaining acceptance by contemporary software development teams in general and Agile methods users in particular. Agile followers heavily promote the use of face-to-face interactions and source code based artefacts for knowledge sharing. However, these practices have severe limitations for sharing knowledge in globally distributed software development teams. We assert that artefacts can be important source of knowledge that needs to be shared for effective and efficient development and evolution of a software system. One of our case studies has reported the strengths and limitations of artefacts based cultural of knowledge sharing the context of GSE. Our study has empirically explored the key reasons and practices of achieving a shared understanding of software technical specifications (e.g., requirements, designs, and analysis models) through artifact-based knowledge sharing.