Process

i-Proving is Intelliware’s approach to software development. It has been influenced by the principles of Lean Manufacturing, and incorporates many of the key ideas championed by the Agile software development community. It has evolved based on our project experience over the years, and as we’ve grown through challenges with different organizations and technologies. It is a “production hardened” approach to software development.

The core elements of Intelliware i-Proving process include:

  • Breaking requirements into incremental features called Stories that are implemented to production quality, one at a time.
  • Development of automated tests in parallel to features development.
  • Automated builds.
  • Team accountability for estimates, delivery, and code.
  • Regular, small production quality deliverables.
  • Ongoing customer participation and feedback.

For a more detailed description of our process, please refer to the resource materials available in the i-Proving section of our Knowledge Centre.

There are three key points to take away about Intelliware’s i-Proving process.

1. It is action oriented.
Stories, simple use-cases or features of a system, are the building blocks of our projects. Defining, prioritizing, and building them out can be done very quickly. If you know you need to get going, but are not sure how to get going, our approach can get you started very quickly.

2. It is adaptive to large environments.
If you like the idea of “Agile”, but don’t know how it will work in your large organization, don’t worry.  Intelliware has a great deal of experience on how to adapt i-Proving to large multi-national corporations. We work within large IT organizations with defined “Waterfall” processes every day. We can help speed things up, even within established bureaucracies.

3. You can adapt it to meet the needs of your organization.
Many of our clients have used us to establish Agile practices in their own environments. We can be used as an agent of change. By co-teaming and co-locating, we have successfully established beachheads of Agile practices in organizations with Waterfall bureaucracies, or no defined practices at all. The best way to implement change is through actually doing it – with a partner who knows how it is done.