|
 METHODOLOGY
» Fineese has adopted certain Business and production Models to be successful in production . Those are
1. Project Appraisal
IBN Seniors spends enough time to understand the Project in
terms of functionality, Risk involved in the Project( Customer side,
Client side, Companys side) , Technology involved , domain expertise
required, Proof of concept( Have we done any similar projects),
HR allocation, Delivery Model, Grounds of acceptance of the Project,etc.
2. Customer Verification at every moment
Making things easy and simpler for the Customer to verify . For
e.g Every User Interface is approved by the customer giving him
a real time effect. Every prototypes, Every Constraint specifically
written in negative language gives Customers an clear idea of what
is possible in the software and what is not possible in the software
thereby building the boudaries of requirement.
3. Changes in customer Requirement
Every survey reveals that not more than 1 out of 1000 projects
are completed without change in requirement . We support Easy change
of requirement by giving a prototype delivery at early stage of
development which gives client a chance to think over, work over
and come upon changes in requirement in early stage. Basic reasoning
of Changes in Requirement is due to Client Mis Interpretation of
Our Understanding, Our misinterpretation of Clients REquirement.
Both the cases can be rectified by putting edges to each other understanding.
in terms of GUI , Declaration of What is POSSIBLE in the SOFTWARE
and WHAT is not possible in the Software. Software design is planned
with proper packages and interfaces to support the last minute changing
requirement of the customer.
4. Risk Mitigation
In order to mitigate Risk , We identify the Complex areas of application
, important functionality in the project which can start early ROI
5. Delivery Model
Maximum percentage of Onsite development are successful software.
In order to mitigate risk in Offshore development , IBN has
emphasizes on the Teams working at both ends for larger project
in which Requirement, GUIs, Implementation, PreImplementation test
and POSt Implementation test, and maintenance is done at the clients
premise. This calls for BLEND MODEL.
6. Priotizing
This is another important area which most of the software industry
does not take into consideration. Software is always thought of
modules beginning with masters reaching the transaction and gradually
reaching the MIS. It may not be true always because there can be
some models in which you write the script to import all the legacy
data, builds on the MIS and Analytical Software and then retrogate
towards the data Entry screens. All that takes to get Clients Early
ROI and mitigate Risk should be priotized. The Factors which calls
for maximum change in the Requirement at early stage or gives maximum
visibility of the software are taken at the highest priority. «
|