Our Process

IT field is the most advance and dynamic field. To keep our clients ahead in IT we keep researching on what is the new technology that is relevant for our work environment. Looking to the benefits of Scrum methodology we have started adopting it for our application development project planning.

For any application to develop we first gather requirement from the customer site. We talk to all the stack holders who can provide information about existing system and the problems they are facing. Our intention is to understand the system from shop floor worker to the high level management. After gathering all necessary detail we draft basic requirement. We have our own method to strategise the work. At the initial level we visualize full system. This part is so important as on the bases of this we provide project commercial detail to the customer.

With scrum being so focused on productivity of the developers it is easy to forget the requirements phase. Just because we’ve (finally) found a great way to get developers productive doesn’t mean that we can ignore the requirements. After receiving the confirm order for the project we convert the requirement into the story. We believe in storytelling as it is easy to understand and easy to remember. So our aim is to visualise the solution into the story. Then we classify the system into subsystem for development to start work as per the scrum process.

For each project we list down our objectives and the detail about what problems this solution will resolve. Before the problem statement can be crafted, the problem must be defined. It is human nature to want to begin working on a solution as soon as possible and neglecting the definition of the true problem to be solved. However, a poorly defined problem increases the risk of implementing a solution that does not fully meet the expected results. A problem cannot be solved if it is not completely understood.