A detailed proposal is then
made with contributions from our senior technical staff after analysing and addressing
your requirement. The proposal would cover an executive summary, the project development
plan (covering technical solution, software/hardware components and proposed architecture)
the implementation plan and schedules, efforts and costs. This would give you a clear idea
of what to expect as deliverables and by when.
Clarity in understanding the requirements and effective project management are the two key
areas in a remote development model. Once the project is initiated, key techno-commercial
managers will visit your offices to discuss, understand and capture your requirements.
Meanwhile, the team would be built in Bangalore. This team will be subjected to relevant
training and orientation, if needed. On their return, the team that visited your site
conducts a functional workshop for the rest of the team at Bangalore to disseminate the
requirements. Architecture definition and prototyping, if necessary, is done. This is
followed by design, implementation and testing phases at Bangalore. Another visit for
integration and system testing at your site makes up the last phase. Each phase involves a
series of reviews ; internal and external. Reviews at critical phases will sometimes
involve you either on-site or off-shore. Detailed documents are generated at each stage
which help in subsequent phases and also in maintenance and support.
A typical structure of a project would be :
Account Manager (non-technical, client satisfaction and relationship
Project Manager (planning, monitoring/tracking, reviews and overall
Project Leader (technical solutions and co-ordination)
development team (implementation) and a host of other support people
including documentation specialists, QA engineers, build and configuration librarians and
what we have done. . .