Our
development efforts are responsive, solutions-oriented
and iterative processes that integrate the client
into the development effort (to any extent desired).
Our goal is to do it right the first time, on-time,
and we do so by keeping the communication paths
with the client very open and inclusive.
In fact, communication is also the key to our internal
(international) collaborative success as well. We
rely extensively on text chat, group email, document
sharing, and remote server control. |
 |
We
begin by studying project requirements and scope.
Detailed technical specifications are developed
by creating "work specs" for specifically identifiable
sub-tasks. The specifications are a "living document".
It is important that we maintain the flexibility
to alter and better define work specs as a project
matures.
Developer comments, text chat sessions, email notes,
etc. are stored in private folders for access by
all team members.
|
|
We
place considerable emphasis on project status tracking
and reporting. Periodic written reports are composed,
in conjunction with the sub-task tracking entry
to electronic project planning software. This also
is made available collaboratively.
These procedures apply to time-and-materials as
well as fixed-bid projects. For fixed-bid work,
our usual procedure is to take a project in phases,
with the first phase being comprised primarily of
the technical specification and analysis effort.
|
.jpg)
