Our Process

TechO2 adopted Agile software development methodology. By adopting agile processes, TechO2 has institutionalized disciplined project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development cycles with customer needs and company goals.

We are uncovering better ways of developing software by implementing agile development models and Scrum based project management style. Through this work we have come to value:

• Individuals and interactions over processes and tools
• Quality software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change swiftly over rigid project plans

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

• Customer satisfaction by rapid, continuous delivery of tangible software
• Working software is delivered frequently (weeks rather than months)
• Working software is the principal measure of progress
• Even late changes in requirements are welcomed as it’s viewed as evolving solutions to complex business needs
• coherent and frequent cooperation between business stakeholders and development teams
• Projects are built around motivated individuals, who should be trusted
• Continuous attention to technical excellence and good design Simplicity
• Self-organizing teams
• Regular adaptation to changing circumstances

The TechO2 process allows the client to monitor progress much more frequently, which allows them to spot misunderstandings more quickly and provide early feedback into the solution. Furthermore a partially developed system can also educate the customer, for often there's a difference between what's asked for and what's needed - and usually that's not apparent until there's some working software.

Having regular integrated builds allows our clients to pull down last night's work and try it out. While this isn't quite as immediate as co-location, it still allows the customer to correct any misunderstandings quickly; as well as allowing them to refine their own understanding of the requirements.

We have dedicated Quality Assurance team which makes sure the bugs are not passed to the client. Our philosophy of QA is another value-add to our clients. We don’t believe QA comes in at the end of the development cycle to test the end product. In stead, our QA analysts participate and contribute in every phase of the solution development, refining use cases, developing test cases, work as functional experts to bridge the gap between technology implementation and clients functional needs.

Emphasis on collaboration also manifests in how TechO2 teams operate internally. Daily scrums, Project Wikis, Issue tracking tools, are some of the key collaboration tools and processes that are the norm for the teams functioning.