Close Collaboration
We like to keep in close contact with our clients throughout the development process. This keeps on tracks and lets us know as early as possible what feature of details you might want changed. The earlier, the better.
You or your staff do not need training to work with us. You or your staff will, however, need to devote time to review our progress by providing frequent feedback on our work. Your committment also consists of formally participating in Acceptance tests for each feature to ensure it does just what you need and is easy to use.
Our side of the collaboration is our team which comes together from complementary talent areas. The core of the team is the project manager or software architect, or as we fondly call him or her, the commanding officer (CO). Supporting him or her are several leiutenants depending on your needs, some which may be filled by the same person:
- Programmer
- Html markup expert
- Copywriter / Editor
- Database administrator
- Server administrator
- Network engineer
Clients can freely communicate with each team member, not just the project manager. As veterans, we're good enough to let our commander, err, our project manager know what you need done. And, we're good enough as technologists to know who on the team has the best talents to succesfully handle that need.
Smart Process
Lisantra smartly organizes its work process with Agile development. We also just can't get security out of our systems; our old security clearances have simply shaped us for the better, it seems. We segment our implementation into features and take five steps to focused on the feature at hand:
- Discover Your Needs
- Design the Feature
- Write Feature's Code
- Test the Feature
- Deploy the Feature
Measured Pace
We pace our work and our billing to keep everyone happy and sustain the project for the long haul without burning anyone out. Our pacing standard is the feature's iteration. Each iteration lasts several weeks, usually from two to four. We set up a convenient schedule to periodically review the progress of each feature's iteration. After we complete one feature, we start immediately on the next.
We bill frequently, usually with half the project's estimated cost up front with increments paid upon the completed iteration of each feature. The feature's cost may change if its requirements change. The project is considered finished when the application does what it was meant to do and it does it well.
