
|
The most important aspect of
our iBuild process is communication. Through online collaborative tools
and status reporting, we ensure your project stays on schedule and on
budget with no surprises.
Dan Albert
VP Engineering |
|
iBuild
Our implementation phase is built
on a unique development process. Our experience delivering
successful Internet solutions has shown us that expectations
can easily diverge at this stage when design— based on
lengthy descriptions of features and functionality—happens
in isolation.
Our online collaborative workspaces
provide a central location for all documents and information
about the product. Unlike a traditional project status report,
our eRoom centers provide a place for you to review and
interact directly with the development team.
The foundation of the iBuild
process is development of a clearly defined Statement of Work.
This document contains the specific details of the
implementation plan. The Statement of Work is then reviewed
and approved and becomes the measuring stick for the iBuild
Process. In order to minimize the impact of inevitable shifts
in requirements and specifications, our process based change
management system keeps the project ontrack and more
importantly keeps you informed.
Once we have defined the statement
of work, the iBuild process moves into the programming and
development phase, including…
- creation
of a functional model
- developing
the user interface
- online
prototypes
- implementation
into the operational environment
- third
party testing/debugging
- interactive
training for your users
Once
your initiative is launched your development team provides
continuity through our iManage services.
|