Impact of Change Management on a
New Library Automation Software
Development Research
By
PROTITI MAJUMDAR GUPTA
Why this topic
An endeavour to discover new or collated old facts etc by the scientific study of
a subject or by a course ...
What is Change Management
It is an approach to shifting or transitioning individuals, teams and
organizations from a curre...
Why Change Management:
Economic downturns,
Changes in strategy,
Government legislation,
Labour market pressure,
Techn...
When Change Management:
‘Change is the unchangeable fact of the life’ Change can happen any time any where
depend upon a f...
How Change Management:
By following few below mentioned steps change management can be done
successfully:
 Finding
 Eval...
Change Management Case Study:
Developed a New Library Automation Software: KONIKA
A project done by Jadavpur University de...
What Change Done
Koha Konika
Customization of Koha
Why this Change?
To develop a library automation software which can serve the need of small
libraries e.g. Acquisition, Ci...
When this Change?
After analyzing the existing automation software and finding the loophole of existing
software
How Change Management Done?
FINDING EVALUATING ANALYZING DEVELOPING TESTING TRAINING
What exactly
the need of
small
librar...
03/04/2014
Our Change Management Journey
We are going to develop a
new lib automation software
Why so???
Existing software...
Analysis of Feed-back from workshop
School Libr
Public Libr
other
Types of participants in workshop
How many of them aware
about Koha
Koha Used
Koha
never usd
How many of them used Koha
Comfortable using Koha
Comfortable
using koha
want simplified
Koha
Want simplified
version of Koha
User need
Outcome of our change management
USER’S EXPECTATION
CONCLUSION
Simplified KOHA i.e.
KONIKA
KOHA with basic feature
and
KOH...
Upcoming SlideShare
Loading in...5
×

Impact of Change management on new software development research

82

Published on

Published in: Education, Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
82
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Impact of Change management on new software development research

  1. 1. Impact of Change Management on a New Library Automation Software Development Research By PROTITI MAJUMDAR GUPTA
  2. 2. Why this topic An endeavour to discover new or collated old facts etc by the scientific study of a subject or by a course of critical investigation. So, Research output= new or collated old facts New or collated old facts= People discomfort, not want to except willingly People discomfort, not want to except= Unsuccessful research Research output + Change management= Successful Research
  3. 3. What is Change Management It is an approach to shifting or transitioning individuals, teams and organizations from a current state to a desired future state.
  4. 4. Why Change Management: Economic downturns, Changes in strategy, Government legislation, Labour market pressure, Technological changes Natural evolvement.
  5. 5. When Change Management: ‘Change is the unchangeable fact of the life’ Change can happen any time any where depend upon a factor. These factors may be Technology, strategy, economic condition, etc. To handle this change effectively and efficiently Change Management is necessary.
  6. 6. How Change Management: By following few below mentioned steps change management can be done successfully:  Finding  Evaluating  Analyzing  Developing  Testing  Training
  7. 7. Change Management Case Study: Developed a New Library Automation Software: KONIKA A project done by Jadavpur University department of Library and Information Science under University with Potential for Excellence
  8. 8. What Change Done Koha Konika Customization of Koha
  9. 9. Why this Change? To develop a library automation software which can serve the need of small libraries e.g. Acquisition, Circulation, Catalouging, User Database creation.
  10. 10. When this Change? After analyzing the existing automation software and finding the loophole of existing software
  11. 11. How Change Management Done? FINDING EVALUATING ANALYZING DEVELOPING TESTING TRAINING What exactly the need of small libraries. Features of existing automation software. SWOT analysis of existing software. Customization of KOHA. Install, reinstall, finding the bugs. Arranging workshop with handouts. Create library holding database, Patron database, Circulation and Report Acquisition, Circulation, Periodicals Journal Indexing, Authority, Web enquiry, Book hire, Patron database creation. Too many features for small libraries which basically leads towards confusion. Developed KONIKA Install, reinstall KONIKA in different systems, Found out bugs. Modification done on the basis of need Arranged a four day workshop with handouts to train people how to use KONIKA.
  12. 12. 03/04/2014 Our Change Management Journey We are going to develop a new lib automation software Why so??? Existing software are good enough ! Why do we need a new one? We don’t want a new software!!!!! Our new software is the customization of KOHA We will try to adapt KONIKA We have tested the new taxonomy with F&B team with promising results We are very happy with KONIKA
  13. 13. Analysis of Feed-back from workshop
  14. 14. School Libr Public Libr other Types of participants in workshop
  15. 15. How many of them aware about Koha Koha Used Koha never usd How many of them used Koha
  16. 16. Comfortable using Koha Comfortable using koha want simplified Koha Want simplified version of Koha User need
  17. 17. Outcome of our change management USER’S EXPECTATION CONCLUSION Simplified KOHA i.e. KONIKA KOHA with basic feature and KOHA minus extra features A successful Change Management OUR CREATION OUR CREATION USER’S EXPECTATION
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×