The Office

View Larger Map

The Team

We have the full range of Internet and systems technology development experience. We employ database administrators, application engineers and interface specialists. We are experienced in information architecture, usability, project management, graphic design and interface development for any software project.

Our Approach

We have found that the traditional software development and implementation methodologies are too rigid and do not work well with today's fast-paced, ever-changing world of internet technology.

Quite often the design phase uncovers requirements that are technically unfeasible or possibly too expensive to implement. Business requirements and priorities are also prone to change during the development cycle. These are just some of the reasons why it is impractical to follow a strict waterfall approach of requirement analysis, system design, development and testing cycle.

We therefore find it much more practical, efficient and beneficial to everyone to follow a model where requirements gathering and analysis is continued until a critical mass has been reached. At that point, the analysis, design, development, and test phases are compressed into a series of short, iterative development cycles.
 
This approach has a number of distinct advantages over the traditional waterfall development model. Iteration allows for effectiveness and self-correction. Studies have shown that human beings rarely perform a complex task correctly the first time. However, they are extremely good at making an adequate beginning and then making many small refinements and improvements. It is therefore much better to use this to your advantage rather than fight it.

Each iteration of the development cycle delivers a well-engineered, functional portion of the final system. Early iterations generally focus on a single thread, prototyping critical functionality to insure that the system will work. Early iterations also focus on risk detection and critical risk reduction/elimination. Further iterations continue to build upon this basis by adding functionality and further refining the foundation built during prior iterations.

This approach also has the advantage of providing visible results much earlier in the project, which is usually very welcomed by project sponsors and the business communities. Also, often times system requirements are not well defined and the iterative process is an excellent way of discovering those needs prior to the system being completely built. By working in an iterative fashion, all of the stakeholders can get involved in the development process, greatly facilitating communication across the team, and ultimately resulting in a better end-product.