Mazarin Delivery Process

Mazarin Deliver Process is formulated by streamlining the information and experience gained over the years of project deliveries and combining the industry best practices.

The process is primarily driven by Agile Methodology and SCRUM project management discipline. The primary objectives of the process are to be lightweight, flexible/agile and customer focused. The process is not by it self to be considered a standards and each project team depending on the project size, duration, complexity and customer preferences take out non-value adding parts of the process for that specific project. Yet in doing so the project should not compromise the quality of the software or the code base.

As a learning organization the process is open for continuous improvement and each Mazarin employee is expected to contribute their criticisms and suggestions to improve the process continually.

Mazarin Delivery Process

The Process

The diagram below summarizes the entire process, while specific components of interest are separately explained in the following sections.

Types of Work

The work that comes to Mazarin can be divided into four categories. Depending on the category, the process components used differ.

  • Projects: All customer requirements that have definite time line to develop, a turn-key solution and where majority of the delivery cycle and management are done by Mazarin fall to this category. Generally projects are once off but a project after successful completion can convert to a product.
  • Products: All customer requirements that are repeatedly sold with different versions and modifications fall to this category. The first implementation would be handled as a project but moved onto a product process after first delivery.
  • Technology Migrations: All customer requirements that involve moving currently existing software to a new and improved design and technology.
  • Consultancy: All outsourcing of one or many software engineers to work with the customer team fall into this category.

One should remember that a client's need would not clearly fall to one of these categories all the time, and would be a combination of several categories together in which case the project team has to tailor the process to suite the situation.


  • Business Development: All activities done to get a new project fall under this stage.
  • Incubation: This is the stage where Mazarin formally kicks off the project. Low level of resources will be used in this stage, ideally only two resources, one being the project lead and other being software engineer. This stage will focus on getting the requirements finalized at least for the first few releases; setup the project environment, project source code, communication needs and testing environment for the full team to come in at a later stage. This stage is detailed explained later due to its importance.
  • Development: Primary stage for developing the project/product. The project must strive for a bi weekly release or at least a monthly release. For turn key projects, all versions before version 1.0 will be in this stage. For other projects any major development of the software will fall within this stage.
  • Implementation: Here the software is released for customer to be implemented in the production environment. Data migration, setup of production environment, testing the production environment and fixing requirement mismaches are key activities of this stage.
  • Maintenance: Optional stage. Maintenance stage depends on the agreement between the customer and the company. During this stage, minor fixes, improvements and development of few new features would be done but keeping the delivered system by and large as it is.

After a first delivery a project can have difference modules at different stages.

Related Topics

| Share