How we work

We are willing to earn our clients' trust every single day. Partnership is a responsibility and it's one we don't take lightly. We believe it's important to have the right IT team in place and know that the team is always willing to go the extra mile. It doesn't matter if you have a small project or an annual engagement with us.

In short, our philosophies are:

Expertise and interactions over processes, tools and technologies.
Customer participation over contract negotiation
Responding to change over following a plan
Our approach involves close collaboration, learning business, and responding to the changing business needs.
Our robust development cycle ensures that budgets and timelines are managed and tracked properly. Non-value added activities are avoided.
We maintain the transparency and ensure that everyone stays in the loop and on the same model.

Our success lies in our development model called Agile Methodology. When we build your application solution, we do it incrementally and break the project into multiple development cycles. Our approach gives customers the opportunity to be hands on with incremental versions of the application being built. During each of iteration, we collect customer feedback and make adjustments and enhancements to the working model of the application. This approach eliminates the unwanted inconvenience that can happen when developers only build to spec and don’t involve the customer throughout the entire process. As a result, it reduces the risk of your project, eliminates surprises and accelerates the production of quality product.

We believe in quality, product compatibility and reusability. As our highest is to ensure that our solution will meet the expectation, we maintain the accountability and customer’s participation throughout the product development. We strictly follow Microsoft Solution Framework (MSF) guideline to ensure the product quality. MSF is the worldwide industry standard development guideline that has proven its competency.

MSF Principles

Microsoft Solutions Framework (MSF) for Agile Software Development is a scenario-driven, context-based agile software development process for building .NET and other object-oriented applications. MSF for Agile Software Development directly incorporates practices for handling quality of service requirements such as performance and security. It is also context-based and uses a context-driven approach to determine how to operate the project. This approach helps create an adaptive process that overcomes the boundary conditions of most agile software development processes while achieving the objectives set out in the vision of the project.

Partner with customers:

A customer focus throughout development means having team commitment to understand and solve the customer’s business problem. Once this business problem is understood, customer involvement must be maximized to the degree possible to ensure that the customer's expectations are met.

Work toward a shared vision:

Shared vision ensures that all team members agree on what they are accomplishing by building the product. A shared vision aligns the team around a common goal and sets the customer’s expectations.

Invest in quality:

In a successful team, every member feels responsible for the quality of the product. Responsibility for quality cannot be delegated from one team member to another team member or function.

Cycles and iterations:

The smooth integration of MSF for Agile Software Development supports rapid iterative development with continuous learning and refinement. Product definition, development, and testing occur in overlapping iterations resulting in incremental completion of the project.

Governance:

Governance concerns the control of time and money relative to the flow of value. MSF for Agile Software Development defines five governance checkpoints, each of which focuses on a specific question to answer.

Team roles to produce the right solution

In MSF for Agile software development, a team brought together that are involved with the production, use, and maintenance of the product. Each team member, or role, is accountable for representing the specific needs of its constituencies and none is more important than another. Together these views provide the necessary checks and balances to ensure that the team produces the right solution. We maintain the following roles in our teams.

Business analyst
Project Manager
Architect
Developer
Tester
Release Manager
Database Administrator and Developer