This document discusses knowledge management in an Indian IT company that changed from a waterfall model to an agile model. It describes the waterfall and agile models and principles of agile. The company faced challenges in transitioning employees accustomed to waterfall to the new iterative agile method. This required training employees and hiring experts. Coordination between teams also increased, as did client interaction. Employees were initially frustrated reworking software in multiple iterations. However, after implementing agile the company saw more satisfied customers, better software, and lower costs by catching problems earlier.

1. KNOWLEDGE
MANAGEMENT IN IT
ORGANISATIONS
SHASHI KUMAR

2. OBJECTIVES
o To study the impact of changes in an IT organisation
after major changes in the organisation process
o To understand how knowledge management system is
implemented in IT organisations

3. INTRODUCTION
o The organisation in study is an IT company in India
which works in various facets of IT Technologies and
services
o The company in study creates various software
packages and websites for various platforms for local
and foreign customers
o The company used to have waterfall model earlier and
changed to agile model after using it for several years in
search of higher efficiency

4. WATERFALL MODEL
This model works in a sequential method through various
phases of :
o Conception
o Initiation
o Analysis
o Design
o Construction
o Testing
o Production/ Implementation
o Maintenance

5. LIMITATIONS OF WATERFALL
MODEL
o Clients were many a times not so sure of what they
want before they are able to see a working software and
may change their requirements leading to redo the whole
work again
o Designers not able to forecast future hurdles, which
lead to coming up with major challenges after accepting
a project
o This method is heavily regulated and micro-managed

6. AGILE MODEL
Agile Model Focuses on simple iteration model which has
a test-driven approach,
focuses on active stakeholders participation and
effective documentation throughout the life cycle

7. PRINCIPLES OF AGILE MODEL
1. Customer satisfaction by early and continuous delivery of
valuable software
2. Welcome changing requirements, even in late
development
3. Working software is delivered frequently
4. Close, daily cooperation between business people and
developers
5. Projects are built around motivated individuals, who
should be trusted
6. Face-to-face conversation is the best form of
communication
7. Working software is the principal measure of progress
8. Sustainable development, able to maintain a constant

8. CHALLENGES FACED DURING
CHANGE
o Transition from waterfall model to agile model needed
all employees to learn new method which was a
challenge in itself as employees were habitual of the
earlier model
o Expertise in the model was needed to implement it in
the company, that means hiring new employee to provide
support
o Client interaction increased
o All teams from different facets of development needed
to maintain higher coordination
o Employees frustration due to repeating the
development of software due to multiple iterations
o Complex problems become much more complicated to
implement in the new model in the starting

9. AFTER EFFECTS OF THE
CHANGE
o More Satisfied Customers
o Better Software applications
o Less Cost due to check on problems are caught in the
initial phases itself