We typically approach projects in a formal manner to ensure that the client clearly understands what he can expect from the project and that we can deliver to that expectation.

We have experience of working with different models including the traditional waterfall approach and agile methodologies. If a client has a standard way of working we will adapt to that; if not then we will agree with the client the optimum approach for the specific project.

A typical waterfall project structure is:

Project Initiation

The Project Initiation stage sets up the project. A project steering committee is appointed and a project initiation workshop is held to confirm scope, roles, responsibilities, project approach and plan. A project initiation workshop with the sponsor and other stakeholders is the best way to launch the project.

Technical Analysis and Design

The focus of the Technical Analysis and Design stage is on validating and refining the business-based aspects of the computer system and deriving from them the appropriate technical architecture. Workshop techniques are used to validate the business layer models. The same techniques are used to add detail to the logical layer, sufficient to produce the physical models.

Development

The Development stage is where the computer system is engineered to a sufficiently high standard to be safely placed in the hands of the users. The application system is completed within a pre-defined number of iterations. Every developer works with a part of the prioritised requirements list, develops and unit-tests the functionality following the order of priorities. When the development time-box has reached its end, the developers walk through the changes with the end users.

System Testing

The Systems Testing stage is an integrated approach to testing the quality of all elements of the application system. It includes both functionally-oriented module testing and business-oriented module integration, system, systems integration and acceptance testing. Non-functional requirements testing is also carried out utilising specialised load-testing and performance analysis tools.

Implementation

The Implementation stage covers the cut-over from the development environment to the operational environment. During this stage the new application system is accepted by Client, whereas Crimsonwing delivers training to the new users and ensures the client is well prepared for the new system. A detailed implementation plan is prepared as part of the deployment and cut-over process specifying transition and back out strategies. The solution is hence put into production. Minor upgrades may be developed and released thereafter.

Support/Hand-over

The Support/Hand-over stage includes assistance, bug fixing, removal of irritants and review of the live system.

Project Closure (End-of-Phase Review)

At the conclusion of the project / phase, a final review is held in order to evaluate the effectiveness of the development life-cycle and processes, procedures and practices adopted. Responses on the delivered application system are collected from all interested parties, and a feedback session is held and recommendations for improvement are made.