We go out of our way to provide complete access to the solution to be developed for you. Not only do we release a new version every two weeks for you to evaluate, but our automated tools immediately deploy your solution to a webpage for you to view any day. One example is our China customer http://www.teekit.com. (NOTE: The server is in China for Chinese consumers so there may be some delay in accessing the server if you are in the US). They have a private ip where they can see the changes made by developers the same day the developer makes the changes. This allows customers to intermittently check up on product progress and give comments early on in the process.

Since we use a predictive system that is based on statistics and data, we found we could eliminate the main problems in estimation. Every two weeks our systems re-predict three dates, a 90% probability date, a 50% probability date and a 10% probability date. We believe in this system so much, we currently have a product in development that our customers will be able to try out once complete.

Using our process, you will have the power to control the quality vs. speed paradigm. Sometimes. you may desire more speed and decide to reduce the quality temporarily to get the features out faster so they can be demoed. At other times, you may decide quality is of utmost importance and increase quality. We advise most customers to having GA type quality every iteration as the predictive process we use results in more accurate predictions. In this regard, we don't end up in long unknown System Test periods of an unknown number of weeks.

While one expert MAY do a good job at estimation, we use Poker Planning and do team estimation. After all, we all know more heads are better than one. The end result is the teams end up asking for more clarification on requirements and end up with better estimations of the project schedule.

This is the KEY to all of our processes and technologies. Every new technology we developed and every new process we introduced came from this one key thing. We are very very rigid about doing a 15 minute lessons learned every 2 weeks. This is what makes the teams adapt the process to your specific environment and needs and more importantly to your customers needs. Our number one goal is to make the customers of your software project 100% satisfied. Those customers may be internal or external customers depending on your project.