Our Philosophy

We believe there is a better way to build software.

Intelliware’s tagline is Delivery matters.TM We believe that creating solutions that hold up to the high standards of quality and performance are critical to our clients’ success.

We believe in staying at the forefront of applying new technologies to solve business problems for clients. We also believe in setting new standards for the way software is built. The combination of these principles positions us as trusted technology advisers and change agents for our clients.

It’s about using technology in the most appropriate way to drive business value. It’s not about doing the fanciest or most clever thing. It is about knowing these technologies well and figuring out the simplest way to apply them to give our clients the greatest return on their investment.

Break big problems into small pieces. Do the risky parts first. Test constantly.

Intelliware is a delivery organization – this anchors our methods, our attitudes, and our approach to the work we do for our clients.

We have been delivering Agile software projects for 10 years, and custom software projects for over 20. As much as our process is key to our success, it’s our ability to interface and adapt our process to our clients’ needs that ensures mutual success. Intelliware’s core development philosophy has been strongly influenced by Taiichi Ohno’s Lean Manufacturing principles.

These principles are fundamental to a number of different approaches to software development, with core values that are widely shared by the broader Agile software development community. Intelliware’s extensive history with the Agile community began when the core concepts were framed by Kent Beck[2] in the late 1990’s and to this day we remain front-runners in Agile software development.

Agile. Iterative. Collaborative. Agile methodology simply defined.

Agile development is a process built on a number of core values that define the way software development should be done. The key tenets include:

  • Individuals and interactions over processes and tools
  • Working software over comprehension documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

1 Adapted from Liker, J. 2004. “The 14 Principles of the Toyota Way: An Executive Summary of the Culture Behind TPS”, p. 37. Ann Arbor, Michigan: University of Michigan.

2 Beck, K. 1999. “Extreme Programming Explained: Embrace Change”, Addison-Wesley Professional

7 Lean Manufacturing Principles

by Taiichi Ohno of Toyota[1]

Step 1

Create a continuous process flow to bring problems to the surface.

Step 2

Use “pull” systems to avoid overproduction.

Step 3

Level out the workload.

Step 4

Build a culture of stopping to fix problems, to get quality right the first time.

Step 5

Push responsibility to those adding value.

Step 6

Provide visual feedback to ensure no problems are hidden.

Step 7

Use reliable, thoroughly tested technology.