|
|
|
|
|
|
 |
| '" You people are doing a great job
and I am most appreciative. After this project
is successful, i intend to use you on a monthly
basis for continuous maintenance and will
definitely recommend you to my
friends..." |
|
| | |
|
|
|
| |
|
| |
 |
|
|
| Services / Development Philosophy |
We believe the following to be
the key success factors when serving our
customers:
- Creating visible customer value quickly
- Built-in change-tolerance
- Developing only necessary functionality
- Being aggressive in setting and meeting
goals
Ground Rules:
- Satisfy the customer as the highest
priority; not fulfill a plan, fill a document,
placate a boss, or build some technically cool
gadgets.
- Provide best value for the money. Value is
the difference between cost (to build, to buy,
and to use — after compensating for defects) and
value (the business value of the capabilities
the system gives).
- Active customer participation as a real
function of the development in that the customer
representative is really committed in the
decision making on the project and the
consequences of those decisions.
- Team effort in all aspects of development,
including planning.
- Accept change as being part of the business,
anticipate what might occur (where cost
effective), expect that it will occur, and deal
with it when it does occur.
- Develop domain solutions (again with the
value provision) rather than on-off solutions.
- Practical solution today rather than perfect
solution tomorrow.
- Need determines technology rather than using
technology for its own sake. Pick a workable
technology and use it rather than cycling trying
to find the "best."
- Growth is determined by more features, not
more code. The size may be irrelevant. What is
relevant is what (valued) capabilities the
system provides.
Use process and
tools that work best in the given
scenario.
| | |
|
|