We believe in a transparent, controlled and predictable software development process. This is why we embraced Microsoft Solutions Framework (MSF) principles and best practices in our organization. We also believe in high performance and cost effective solutions, so we are always tailoring our processes depending on the complexity and dimension of a project.

The Essensys development process is also ISO 9001 certified and recognized by the International Certification Network (IQNet).

We consider that a very important success factor is customer involvement; this is why we are very transparent in our processes and procedures so you can really watch your solution growing day after day, and feel free to step in at any time.

What is MSF?

MSF stands for Microsoft Solutions Framework.

MSF is derived from the experience gained within Microsoft and from customers and vendors about large-scale software development and service operation projects, the experience of Microsoft’s consultants in conducting projects for enterprise customers, and the best knowledge from the worldwide Information Technology (IT) industry.

MSF provides a set of models, principles, and guidelines for designing and developing enterprise solutions in a way that ensures that all elements of a project, such as people, processes, and tools, can be successfully managed. MSF also provides proven practices for planning, designing, developing, and deploying successful enterprise solutions.

MSF Process Model is a phase-based, milestone driven and iterative model that combines the best principles of the waterfall model and spiral model. The Essensys process also uses an approach based on versioned delivery. Based on the complexity and size each project is split into multiple versions, each version ads new features over the previous version. This approach ensures that the development process is controlled and predictable and also improves visibility for the customer. 
 

During the development of one version five phases must be completed:

	Envisioning
	Planning
	Development
	Stabilizing
	Deployment

For each phase there are strict exit criteria and milestones that must be met before proceeding to the next phase. The following sections briefly describe the main deliverables and activities of each phase.

Back top

Phase 1 - Envisioning

During Envisioning Phase the main business requirements are gathered and the project scope is defined. At this stage a rough cost estimate and time frame for the project is defined. These estimates will be refined during the Planning Phase. Envisioning ends when all parts involved agree on the scope (defined in terms of functionality) of the project.

Activities:

Output:

Phase 2 - Planning

In the Planning Phase all the high level requirements determined in the Envisioning phase are refined and documented, the detailed project plans and technical design are developed. The Planning Phase ends when all plans and the technical design are completed and agreed with the customer.

Activities:

Output:

Phase 3 - Developing

During Development Phase we develop the technical solution according to the specified requirements. Frequent builds of the solution are developed; each build adds more features, until all the requirements are fulfilled. The advantage of frequent build is that you can participate in the development phase, and watch your solution growing. The development phase ends when all the requirements are covered by specific features and functions of the solution.

Activities:

Output:

Phase 4 - Stabilizing

During Stabilizing Phase we test the solution and eliminate any errors discovered. Typical test performed during this phase are: User Acceptance and Usability Testing, Performance Testing, Integration Testing, Security Testing, and many other tests that ensure a high quality solution. This phase ends when no errors are discovered and the solution is 100% bug free.

Activities:

Output:

Phase 5 - Deployment

Finally in the Deployment Phase the solution is installed in the production environment and the acceptance tests are rolled out. This phase ends with the acceptance sign-off and project review which ends the development of the current version, and we are ready for the next version. After the solution acceptance the project enters in the maintenance phase and all the knowledge is transferred to your staff or our operations, depending on your wish.

Activities:

Output:

Process Tools

For optimum results the Essensys development process is sustained by last generation software tools such as:

The process is also sustained by an adequate hardware and networking infrastructure with separate build servers, database servers, source control servers and also a powerful virtualization environment that sustains the testing and staging environments for each project.

Another important aspect of our development process is the presence of a secured collaboration portal dedicated to each of our projects. The portal can only be accessed by the customer team and the development team. The collaboration portals ensure a very good communication within the development team and with the customer. The portals also ensure visibility and control of each project since every project related issue is tracked on the portal.

Several important features of the portal are: