Why we use this model?

Ocom has a complete commitment to quality. At Ocom we are continuously improving our processes to deliver better quality and better service. We have chosen the current model based on our experience and search for best practice.

Many software companies follow a Waterfall Model, or worst Cowboy Coding in which they try and ascertain all the requirements for the software in a short period of time then they fix price the development. A number of false assumptions are made here.

1. The Analyst has a complete understanding of the software which matches the Clients expectations.
2. Based on the first assumption they can correctly fix the time and cost of the development.

1. New features and "wouldn't it be nice" features cannot be added without extra (usually large) expense to the Client because all three sides of the project need to expand.
2. The Scope is fixed. Unless there has been a thorough analysis of the requirements neither the Client nor the Developers have a 100% clear view of the software. The Client has certain expectations which may not be in the requirements. To increase the scope you also need to increase the other three side or reduce the quality.
3. The Cost is fixed. The Developer asses the Cost of the project based on his understanding of the requirements. When the scope changes and therefore the time changes the cost is usually passed on to the customer.
4. The Quality is sacrificed when any of the other criteria change. The only thing that can be sacrificed is quality. Usually to meet the same fixed resources and time constraints, short cuts are taken which will lead to more bugs and lower quality software.

We value quality in our software which is why Ocom software uses a Scrum Development model. Scrum Development uses an iterative approach to software development which means we can deliver high quality software without restricting the cost or the scope.

How Scrum Works for You

The Scrum approach allows you to fix the cost if you desire, however the scope and time may not be fixed. You can change the scope as the project goes along and the quality will still be at the level you expect from Ocom Software. It also gives you the flexibility to adjust the scope of the project with out costing more money.

The Scrum Process in a nutshell

The first step in the Scrum Process is to get an overview of the requirements of the software. Together we compile a set of Stories. These form the basis on which the software will be written.

We then go into an Iteration which is a short period of time for development. It could be 1 week to 1 month, depending on the size of the project.

An Iteration starts with the Customer and the development team looking at all the stories and discussing them. Together they find the Stories to be implemented in the agreed time of the iteration.

The developers then go away and implement the discussed stories. Asking the Customer for assistance when they need further clarification.

At the end of the iteration the customer has running software which implements the stories agreed upon. They then revisit the remaining stories and start another iteration. Iterations continue until either the scope, time or money are exhausted.

When the requirements change the customer can add a new story to be implemented in the next iteration. Other stories may be removed to make room for the new story or the story is placed into another iteration at a later time.