Option Matrix has been working over last 2 years for an IT solutions firm in Denmark that provides portal solutions to sports clubs
We believe that business is about doing great work and everything else automatically falls in place. We never compromise on the quality standards even if it takes more time to finish a task. We give extreme importance to user interface and audit both engineering as well as functional quality in every deliverable we produce. Our benchmark for quality is this – Can I wholeheartedly refer Option Matrix for a project to a close friend or family member? We strive towards the highest standards on daily basis so that the answer to this question is a consistent “yes” in the mind of every associate and client.
The company is responsible to ensure consistent client satisfaction on all projects done by the company. Work must be delivered as per the commitment made to client in the proposal and payments must be collected from client when specific project milestones are achieved. Client must get value for money and repeat business is the key index of performance for the company. This is the most important function and is the nucleus of the business. The central purpose and reason for success / progress of the business is the ability to consistently do good work for customers. Success of this activity is central to the success and progress of the business. The programmers are strictly advised to work as per guidelines of engineering group and any new function must first be researched by engineering group and then implemented by programmers. The company views the sales activity as an integral upfront component of the software development lifecycle. Option Matrix believes that it is critical to correctly understand and manage client expectations during the process of making the project proposal so that the commitments made are realistic and feasible. Hence the sales activity is always done only by an experienced Project Manager and not by junior executives. After the project is awarded, the Project Manager leads the entire process to design and implement the complete architecture of the project. The mandatory steps for all Custom Application Development projects at Option Matrix are listed on the next page. There may be some difference in the methodology for product development or migration or maintenance projects but the basic underlying principles stay the same.
Option Matrix proactively seeks client feedback after submitting the proposal by e-mail and requests for a briefing session to explain the proposal to the client, so that the scope is confirmed and the boundaries are clear.
The test plan is a document that describes the steps required to test the features for each module and expectations in terms of output for specified inputs. Option Matrix prepares the test plan document as a series of sections describing how each feature will be test with examples of test data that will be used.
The programming phase is an implementation of the design signed off with the client and is done module by module. The number of modules may vary between 2 to 6 based on the size of the project. Code certification, testing and client validation is done at the end of each module.
The features included in the module are implemented as per the validated programming conventions. The programming must be done for each release / module as per the guidelines in code structure. Lead Software Engineer allocates work to Software Engineers, who submit the codes to Lead Software Engineer on completion and unit testing of their allocated work.
Every Software Engineer must test own work comprehensively before submitting for integration to Lead Software Engineer. Work must be done in spirit of zero defect tolerance. Lead Software Engineer makes an excel sheet based on UNIT testing of the current module / release, highlighting the defects and the Software Engineer responsible for those defects. The Issue log (Integration Testing Log for the module) must be tracked to completion.
The Project Manager does a code certification for work done by Software Engineers against the agreed programming conventions and Software Engineers may need to make certain revisions and resubmit their work. This step ensures the right engineering quality and high performance construction of the application.
After the Lead Software Engineer approves the module based on integration testing, the QA Analyst makes an excel sheet based in black box testing of the current module / release, highlighting the defects and the Software Engineer responsible for those defects is identified based on discussion with Lead Software Engineer. The Issue log (Feature Testing Log for the module) must be tracked to completion.
After the QA Analyst approves the module based on black box testing, the Business Analyst makes a demo / presentation to client or submits the module to client for review. The client issues are recorded in an Excel sheet and the Software Engineer responsible for each of those defects is identified based on discussion with Lead Software Engineer. The Issue log (CAT Log for the module) must be tracked to completion.
QA Analyst does functional and stress testing at end of project. The bugs are logged and tracked to closure. Business Analyst may also identify residual errors by conducting a demo of the completed application to the client coordinator.
The system tested application is transferred to live or production server provided by client. Client creates several login accounts for users and reports any issues or bugs which the allocated programmer must resolve to satisfaction of client while maintaining the scope boundaries of the project.