|
 |
 |
|
 |
 |
|
 |
|
|
| |
|
|
|
|
|
|
|
| |
 |
Offshore Software Development |
 |
 |
|
 |
|
| |
|
|
| |
|
|
 |
Offshore Software Development |
 |
|
|
Mavin
Info Tech has always maintained a
focused approach toward offshore
development. We offer offshore
development as an alternative. That
alternative can help you to utilize
our exceptional skills on a
multitude of technologies.
We
foster a development environment
that is tailor-made to your
requirements. That
"tailor-made" environment
will help you increase your
"Return on Investment"
without the added concerns of a
significant upfront investment, the
infrastructure management and risks
associated with maintaining and
managing such infrastructure. Our
"technology lab on hire
concept" will provide you with
a dedicated team of individuals who
can service your specific needs.
That service covers every aspect of
technology and related
infrastructure.
Our
offshore development methodology
uses one of two commonly followed
approaches:
|
Offsite Offshore Model |
The
first tier includes a Project Services
Team that is based at client site and
which is the point-of-contact for the
customer. The Project Services Team
manages:
- Analysis
- Planning
- Technical
architecture
- High-level
design
- Delivery
- Coordination
of all communication between the
customer and offshore team
|
|
|
|
The
second-tier Project Execution Team
is stationed offshore in India . The
offshore center includes a
development team also headed by a
Project Manager. The Project
Execution team is involved in:
- Detailed
design
- Construction
- Testing
- Documentation
Offsite
Tasks: Project initiation, planning,
scope, risk, change & end-point
delivery management
Offshore
Tasks : Infrastructure, Resource,
configuration and execution
management
The
development partner is in the same
geographical location as the
customer. Therefore, the partner can
easily interact with the customer's
team on a daily basis. Interacting
teams from both ends can also meet
on a daily basis. The success of the
model depends on the proximity of a
customer to the development partner.
This
model works extremely well in case
of complex, distributed n-tier
applications where (1) there is a
constant need for change and (2) the
application development is highly
iterative and encompasses an
evolving model. The offsite team
does most of the design and
deployment while the offshore team
does development & testing.
|
Onsite Offshore Model |
|
Where
the nature of the project involves
intense collaboration or interaction
on a continual basis or there is a
customer specific requirement, an
onsite presence is maintained. The
onsite manager works from the
customer site and coordinates
project related aspects with the ODC
and the customer. This onsite
presence may involve a single
resource or an entire project
services team, depending on the
nature, size, and complexity of the
development initiative. The approach
requires an onsite coordinator or an
onsite project manager. The onsite
component may include one or more
resources depending upon the size
and complexity of the project. A
considerable amount of the work
effort can be transitioned to the
offshore facility. That transition
can result in a significant cost
benefit to the customer.
|
|
|
|
A
typical Offshore Development
Communication plan is as under:
|
Activity
|
Schedule |
Mode |
Comments |
|
Client
Status Meeting
|
Weekly,
Day and Time TBD |
Face
to Face |
Standard
status meeting with predefined
agenda. |
| Mavin
Infotech Status Update |
Every
Week, on Monday morning,
Describing the status of the
previous week
|
E-mail
|
Describes
the general progress of work
on the project by the Mavin
Info Tech Team. The update
will include both onshore and
offshore work.
|
|
Working
Sessions
|
As
needed
|
Internet
Messenger Meeting /
Teleconference with offshore
in mornings.
|
Should
be conducted in the mornings
if Offshore needs to be
involved
|
|
Project
Announcements
|
As
needed
|
Internet
Messenger Meeting /
Teleconference with offshore
in mornings.
|
Used
to inform development teams
about general information on
the project.
|
|
Project
Issues
|
As
needed
|
Internet
Messenger Meeting /
Teleconference with offshore
in mornings.
|
Used
to record and track project
issues on an ongoing basis.
|
|
|
Offshore
Software Development Methodology is of
prime importance in order to
successfully implement the Offshore
Outsourcing strategy and reap the
benefits of Offshore Software
Development in terms of cost
effectiveness and business
flexibility. The Offshore Software
Development process generally
commences at the customer's site. A
team of system and software analysts
led by a Project Manager carry out the
initial requirements definition and
analysis in consultation with the
customer. The design, development, and
testing phases are carried out at the
offshore development center say in
India ; and the acceptance testing and
implementation are done at the
customer's site.
The
general process of Offshore Software
Development can form the combination
of various below mentioned steps:
-
An
Individual is appointed as a
representative from both sides
for the decided project. This
needs to be project based
because the projects may vary in
fields of application
integration services, e-commerce
solutions, etc. and hence it
might not be practically
possible for a single person to
handle the same. Say for example
that the client appoints a
Project coordinator from his
side to handle the issues of the
project and the company
providing the development
facility, appoints a Project
Manager for the same.
-
The
initial practical phase might
start with the Project Manager
and his team of software
engineers visiting the client's
site for gathering the system
requirement specifications from
the Project coordinator. These
will very well specify the
required communication
protocols, the reporting
frequency and format, etc., so
that the Project Manager can
pass on the same information to
his development team sitting in
the offshore development center.
-
After
this, the Project Manager
formulates a detailed project
plan, which includes the
necessary resources for the
project, the duration mutually
agreed by the two parties and
the deliverables to be achieved.
This is to be done only after
the client's design approach,
development and testing
standards and norms for
acceptance, if any, are studied
thoroughly.
-
One
or more members of the same team
stay with the client for the
coordination process of the
project, while others move to
the offshore software
development center to proceed
ahead with the process of
preparing a project prototype,
architecture and detailed design
for the project. This is to be
done for the client's approval
that will be issued if the work
to be done is laid on the same
parameters as discussed
initially for the services
outsourced.
-
After
seeking the approval of the
client, the offshore software
development team starts with the
actual work. Regular reporting
and interaction between the
project manager and the project
coordinator helps quick
resolution and on-time
clarifications of any doubts on
either side. This also helps to
maintain the offshore
outsourcing quality standards
mutually agreed by both the
parties.
Upon
successful completion of the
project, it is handed over to the
client to carry out the
implementation and installation of
the same. In many cases, the various
steps mentioned above intersect,
squashing the total time. The
project as foreseen could include
onsite installation and
implementation support followed by
offshore maintenance. Onsite visits
are required initially for bringing
the project offsite and at the end
for delivering the software. The
actual sequence of steps could vary
depending on the specifications of a
given project.
|
|
|
|
|
 |
|
 |
|
| |
|
|
| |
|
|
|
|
|
|
|
 |
Email: info@mavininfotech.com, Contact #: +1 (203) 654 7777 |
 |
| Copyright
Mavin Info Tech 2004-2009 |
| |
|
|
|