Zest emphasizes the value of utilizing industry proven methodologies and the importance of monitoring results when developing software. We base our process framework on open, published and supported standards. On larger projects and with larger software development teams we apply tailored versions of methodologies, while on smaller projects more often we use the most modern Agile Methodologies. The customer has the decisive say on the choice of the methodology for a particular project.
Waterfall Software Development Life Cycle model
The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing and Maintenance. Though, the model was criticized for a long time, it is useful on some midterm, well-defined and structured projects with clear project goals.
Software is developed in increments, where each increment adds some functional capability to a system until the full system is implemented. At each step extensions and design modifications can be made. At Zest such approach is used to develop short-term small-team projects where the customer wants to control progress of work, but does not participate in regular development activities.
When business conditions are rapidly changing and a software product must be developed in a short period of time, though the final functional and technical requirements can’t be estimated beforehand and a client isn’t sure that he will manage to cover costs for the whole project in time, a new alternative agile approach to software development becomes necessary.
Zest team has a substantial experience in Agile Software Development based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The company successfully uses such Agile methods as SCRUM (projects progress via a series of iterations called sprints. Each sprint is typically 2-4 weeks long. Scrum is ideally suited for projects with rapidly changing or highly emergent requirements.) and XP (Extreme Programming).
The other things that make Agile methods our strength are its correspondence to our Quality Management System and a permanent improvement of our stuff qualification by taking part in trainings and conferences dedicated to this topic.
We use various open source tools such as Bugzilla, Testopia, Jira, Basecamp etc.