|
1.
|
We listen* to you describe your needs (problem).
|
|
2.
|
We try to describe it back to you in a written document called the problem domain
document.
|
|
3.
|
When you agree we understand what you want, then we come up with an idea of how
the project should flow.
|
|
4.
|
For smaller projects we can usually provide a cost/ estimate at this stage, once
we have agreement on that we can move on to implementation (see phase 7).
|
|
5.
|
For larger projects that aren't well defined we usually provide an estimate for
an initial stage that will help all of us to fill in the undefined areas.
We try to keep this stage short and inexpensive but it depends on the scope of the
project.
|
|
6.
|
At the end of the project definition stage we define how the project should proceed
and what the expected costs of the stages are. The customer gets a detailed
estimate and documentation describing the project and the expected stages.
|
|
7.
|
We frequently provide a mock-up or prototype of the system really early in the implementation.
That way you get to see something early, and change things before they get expensive
to change. It is a great communication tool.
|
|
8.
|
As the project progresses we try to deliver progress documents and samples to you
every two weeks to a month so you can see hands on progress and critique our work.
|
|
9.
|
When the final product is delivered we typically provide full support and fixes
for a month after acceptance as part of the project schedule.
|
|
|
Our goal is that you are completely satisfied with the product.
|
|
|
* We are realy good at listening and taking the time to understand your needs.
|