5

Theme- Micro-Finance & Technology

main tests i.e., the load test and

Many times higher management

boundary test. Such software often

may want to automate but lower

fails when there is increase in load

functionaries might resist for fear of

and boundary -- inappropriate

mistakes  being  revealed  or

design does not cater to load

deliberate deviant practices

situations and boundary tests. For

coming to the fore. Thus, while staff

normal and rural-based clients it is

may pay lip service to the software,

difficult to distinguish between

in reality may go slow or even

normal test and load test.

sabotage it. This calls for courage

and maturity on the part of the MFI

as it has to take the staff along,

4.

Inadequate Articulation and

explaining the potential benefits of

Documentation of Requirement

automation while rectifying the

mistakes revealed and taking

Proper articulation is often very

corrective action.

difficult because requirement itself

is dynamic in nature, especially in

Useful Practices in Computerisation

the changing market economy.

Therefore, it is advisable to

articulate sub-system wise. This

1.

System Study and Analysis

means that different sub systems of

the operating systems need to be

A  systematic  approach  is

defined  systematically  and

important when initiating the

separately. The requirement should

process of automation. The first

be divided into two parts ­ main

step is to study the system and

and basic requirements and then

analyse it. This process needs to be

sub-system wise. In the second

done by the client so that the

round the detailed requirement

operating process is streamlined.

should be taken sub-system wise.

System analysis is carried out after

system study. The analysis is used

5.

Longevity of Manual Systems

to clearly define all the processes

­ i) ones that will remain manual

Any dilution in the

and ii) ones that are to be

Manual systems continue for a long

process has

automated.  Different people

time even after automation is

implications and

introduced because staff fear

follow different approaches. After

could lead to

the system study and analysis, one

making mistakes. The change to full

inaccuracies and

delay in

needs to prepare a process-flow

automation is a painful transition.

implementation

Organisations are often not ready

diagram with its use case, activity

and trigger (clearly marking the

and therefore care is required from

processes that will remain manual

both sides ­ vendor as well as

client.

and ones that will be automated).

It is very useful if the study is carried

out by a team drawn from both the

6.

Issues with Software

vendor and client. Any dilution in

the process has implications and

Every software requires patient

could lead to inaccuracies and

handling. There are bound to be

delay in implementation.

glitches of all sorts, which will only

be revealed once the MFI staff

2.

Outsourcing Project Management

starts using the software. The

vendor can solve and refine the

software only with the cooperation

Since MFIs do not have an

of the users. It is akin to a horse-hoe

understanding of system study and

computerisation, it is a good idea

­ painful when first fitted but once

broken in, enables the horse to

to

outsource

project

gallop with ease. Similarly, MFI staff

management. There are many

organisations which take on the

will face problems at the time of

adopting the software but once

job. People who have experience

comfortable with the technology,

in microfinance and software

development are better suited for

find that it eases the work pressure.

this. The role of a project manager

is to first understand the users'

7.

Issues  of  Transparency

and

requirement and identify a suitable

Accountability

vendor

and

software

for

implementation.  The  project