CircleSource Systems follows several well known and documented development methodologies. Depending upon the project requirements, scope, time constraints and size, we choose one of the following methods –

Agile
Agile processes harness change for the customer's competitive advantage, even late in development. CircleSource’s agile implementation is as follows.

Team Structure
The team comprises of developers, iteration manager and quality engineer. The iteration manager is primarily responsible for iteration and release plans. The development team is solely responsible for coding new functionality in a given iteration. The QA engineer is responsible for daily regression testing, determining what story cards will be delivered at the end of each iteration and preparing release notes for each delivery.

Planning
The release plan is never the same as the requirement from the customer keeps changing and also what the developer can do. Each release plan has bundle of story cards and functionality. The release plan may be shifting but it is an essential tool. It gives us a view of what may be achievable, evaluating options, and accessing the effect of events.

Analysis
Before the next iteration begins, the domain experts meet and discuss the upcoming functionality. After reaching consensus on the detail of how the functionality should work, they divide the responsibility of incorporating that functionality in the product. Relevant test scenarios are laid out and they are expanded to the final tests to necessarily and sufficiently test the functionality of the story card.

Development
The developers are responsible for adding the iteration's new functionality. Throughout they work closely with the domain experts and with each other and complete the development task assigned to them during the planning meeting.

Quality Assurance
Through the iteration, the QA runs regressions tests regularly to ensure the quality of functionality delivered in previous iterations.

Success
Success is a part of this project from the first iteration. Communication within the team and the client is improved, the planning meeting gets everyone on the same page and clearly states the iteration goals to both the team and the client. Every iteration goes through significant improvement and the whole team initiates these improvements.


V-Model
CircleSource uses the V-Model of development and quality assurance which comprises both the development and the quality assurance processes to run in parallel right from the beginning of the project to its end.

Software Development Life Cycle
The Software development life cycle followed at CircleSource consists of the following steps:
	Requirement Analysis BPR (Business Process Report) or Workflow Analysis Compare Competition - Competitive Analysis Concept Development JRS - Joint Review Sessions System Architecture and Interfaces with other system Proof of Concept - Working Demo User Navigation / Interface Custom Code Development and Test Case Generation Testing - Alpha and Beta CRP - Conference Room Pilot Implementation on production system Post Implementation Testing and Tuning Training, Documentation and Release