This website uses cookies.

Cookies are small text files held on your computer. They allow us to create the best browsing experience for you on our site. By using this website or closing this message, you are agreeing to our Cookies policy.

inqicon

START A CONVERSATION

Share your requirements and we'll get back to you with how we can help.

Thank you for submitting your request.
We will get back to you shortly.

Development

QBurst's software development methodology has evolved from our experience delivering 650+ projects. One thing we learnt over the years is that following a recipe will not ensure success.

Software development is a creative process and often involves trial and error. However, chances of failure can be minimized by following proven best practices such as code reviews, unit testing, and continuous integration.

We Love Agile Development

Our development methodology is based on agile principles and techniques where:

  • Business and development teams work together closely.
  • Product is developed incrementally in iterations.
  • Working software is produced early.
  • New features are frequently released.
  • Users get to try out while features are still being added.

Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

The default agile methodology we follow is Scrum; but based on project and client needs, we often come up with a custom process.

Project Initiation

  • Documentation of wish-list (set of features that business owner wants)
  • A high-level effort estimate is added to each use case/feature
  • The list of use cases is then prioritized for implementation
  • The prioritized list of use cases becomes the Product Backlog

Product Backlog

  • This is maintained and refined throughout the project life-cycle
  • New requirements are added as and when they are unearthed
  • Existing use cases may be broken down into finer-grained use cases
  • Estimates may change as new facts come to light
  • Priorities may also end-up changing

Sprints

  • A sprint is the basic unit of development in Scrum
  • It is "timeboxed" and the average duration is two weeks
  • A planning meeting is conducted prior to the start of a sprint
  • List of features to be completed (sprint backlog) is decided

At the end of a sprint, a working software increment is produced. A review meeting is conducted and completed work is presented to stakeholders.

Transparent Communication

During a sprint, daily scrum meetings or short project status meetings are held with product owner and developers. In these meetings, each developer shares what he had done on the previous day, what they plan to do for the current day, and impediments encountered, if any.

Locked Schedule/Tasks

A sprint deadline is never extended. If a requirement cannot be completed, it gets moved back to the product backlog. Also, during a sprint, requirements are never changed. Thus, developers are shielded from requirement changes allowing them to work uninterruptedly.

To summarize, our development methodology is based on working in close collaboration with customers, frequent releases of working software, and rapid iterations.