Behind every successful software delivery, there is a rigorous project implementation activity consisting of careful execution of stages, steps and tasks. ETESI has been following some of the best practices of project management and implementation methodologies. The methodologies are carefully chosen depending upon the context of the solution requirement, its complexity and scope.
Our core technical team has extensive exposure in diverse project environments and has successfully utilized different methodologies in their long stint in the industry, to satisfy customers’ requirements and deliver successful solutions.
The methodologies that we follow for project execution are described below:
Agile methodologies are based on iterative-incremental processes, with very short iteration cycles (days and weeks rather than months). Working Software is released at the end of each iteration and is the principle measure of progress. Agile methodologies also emphasize close communication with the stakeholders of the project i.e Business, Development and Operations teams.
This methodology gives customers greater control over the final solution because they can quickly change the direction of solution development and implementation from one sprint cycle to the next. This means that they are better placed to respond to their business needs as development of the solution progresses.
ETESI currently runs all projects using the DevOps framework. We have resources who are Certified by the DevOps Foundation.
Our agile processes, refined over several years of project execution, ensure customer satisfaction as their flexibility allows adjustments to meet expectations.
The features of our agile project management methodologies are:
- Adaptive software development approach
- Feature driven development
- Extreme programming and rapid development models
- Agile techniques including test driven design (TDD), agile modelling, agile change management, and database refactoring to improve productivity
- Continuous delivery of useful software
- Flexibility to adjust to late changes in requirements
- Automated development increasing productivity and putting less strain on the quality review process
- Continuous attention to technical excellence and good design
- Regular adaptation to changing circumstances
A waterfall model comprises of a sequence of processes, in which progress is assumed to be flowing steadily downwards (like a waterfall). But a classic waterfall model is only idealistic. It assumes that no modification or defect is introduced during any of the activities. In practice, changes and defects get introduced in almost every phase of the process. And once a modification or defect is detected, we need to revisit the analysis phase and redo some of the work done in subsequent phases. Only a timely feedback from the customer and its resolution makes a waterfall model perfect.
For smaller and medium projects with a defined scope of work, we usually adopt this model.