This website uses cookies to store information on your computer. Some of these cookies are used for visitor analysis, others are essential to making our site function properly and improve the user experience. By using this site, you consent to the placement of these cookies. Click Accept to consent and dismiss this message or Deny to leave this website. Read our Privacy Statement for more.
Agile Projects in a non-agile Environment: What is your experience?
Agile Projects in a non-agile Environment: What is your experience?

In This Casestudy

May 2018 | Agile Research Network | Agile Transformation

Download

This case study presents the story of one organisation’s challenges when integrating Agile.

Created by the Agile Research Network

Anim pariatur cliche reprehenderit, enim eiusmod high life accusamus terry richardson ad squid. 3 wolf moon officia aute, non cupidatat skateboard dolor brunch. Food truck quinoa nesciunt laborum eiusmod. Brunch 3 wolf moon temS.

Click Here

Agile Projects in a non-agile Environment: What is your experience?


Summary

81 employees completed the survey, the majority being software developers. The following list summarises the main findings:

  • Informal discussions are the most common way of sharing knowledge within project teams and with company colleagues
  • Meetings are the most common way of sharing knowledge with the customer
  • Knowledge sharing is easier within project teams than with company colleagues or customers
  • Staff are motivated to share knowledge because they want to rather than because the company asks them to
  • The more Agile practices staff use, the easier they find knowledge sharing with team members
  • The more Agile practices staff use, the more frequently they share knowledge within teams and with customers

We suggest the following for improving organisational knowledge sharing:

  • Enable a knowledge sharing culture with flat management organisation, trust, respect and rewards for sharing
  • Balance the use of technology, processes, expertise networks and physical space in knowledge sharing
  • Build on existing successful knowledge sharing networks, both official and unofficial
  • Create efficient and successful mechanisms for knowledge sharing beyond the team with management, peers and different specialists

Introduction

Knowledge is awareness or understanding of something such as information or skills. Knowledge has value only when it is applied, and the value of knowledge often increases when shared. Organizational knowledge sharing aims to transfer to the organization information, skills and experience gained by a person. This is essential for sustaining the development of quality in software intensive companies. Knowledge is the core resource for Agile development companies that is transformed to products and services in the development process. Moreover, Biao-wen claims that the software industry requires more knowledge management than any other sector.

Knowledge sharing contributes towards putting knowledge into practice in various ways and towards creating new knowledge, i.e. organisational learning. It is a core practice for continuous improvement and innovation. It helps to increase organisational success, enhances creativity, and optimises learning. Knowledge can be tacit (personal, context specific) or explicit (transmittable in formal, systematic language). The two main strategies for knowledge sharing are codification and personalisation. The first systematises and stores information (people-to-documents) the second relies on information exchanges in the company (people-to-people).

Agile methods facilitate knowledge sharing in the team but offer limited support for knowledge sharing outside the team. Agile methods tend to support tacit knowledge shared informally using face-to-face communication (personalisation strategy) in contrast to traditional knowledge management practices. This can present challenges for organisations where Agile methods are only used for IT development. On the other hand, the lack of knowledge sharing practices beyond the team can hinder organizational learning and impair sustaining organizational knowledge in Agile organisations.

Four main factors can endanger the permanence of sufficient organizational knowledge.

  1. an organization might not be able to attract a knowledgeable workforce.
  2. knowledge can be lost via high turnover rates and retirement.
  3. the pace of technology change can outstrip the time developers have to update their knowledge.

Knowledge hoarding might happen due to interpersonal issues but often it is a cultural problem if the organization has not built a knowledge sharing climate.

It can endanger development quality and even the company’s ability to compete with rivals if developers cannot keep their technological knowledge current.

Download the full whitepaper here

 

Contact Us

Tel: + 44 (0)1233 611162
Email: info@agilebusiness.org

Agile Business Consortium
Second Floor
International House
Dover Place
Ashford, Kent
TN23 1HU
United Kingdom

About Us

The Agile Business Consortium is the professional body for Business Agility, and our high value, low cost membership is open to everyone.

Wherever you are on your journey to agility, we are there to support you. We create and share agile research, case studies, resources and tools that help you to compete in today’s disrupted world.

We’ve been contributing to agile knowledge for 25 years and are the world’s oldest agility-oriented organisation. A registered not-for-profit, we’re the brains behind AgilePM®, AgileBA®, AgilePgM® and AgileDS™ and organise the longest running annual Agile Business Conference on the planet. Over 100,000 people around the globe are now AgilePM certified.

© 2019 Agile Business Consortium Limited

Agile Business Consortium Limited is a not-for-profit organisation limited by guarantee.

Registered address: Second Floor, International House, Dover Place, Ashford, Kent, TN23 1HU

Registered in England & Wales. Registration No. 3030597.