![]() |
Agile software development methodology is a set of software development methodologies based on iterative and incremental development. As part of our experience in software development and the use of different methodologies, we have developed our own Agile Stigasoft Process Framework, which covers all the aspects in the development of a successful solution. The key characteristics and benefits are:
The key to the Agile process is its flexibility. At Stigasoft, we recognize that a solution may only be a vision in the customers mind and that all requirements cannot always be thought out and planned at the outset. The process therefore requires constant interaction between Stigasoft and the customer, to provide feedback from both sides about how the project is going.
The Process
The main phases of a project are Planning, Project Incremental Development, Incremental Deployment and Project Closing. The Incremental Development stage is organized into consecutive Sprints or iterations where different tasks are carried out to implement a set of requirements.
Agile Stigasoft Process Framework

Project Planning
As the project starts, the team is formed and planning activities take place to organize the work, this is called Iteration Zero. The Release planning includes the requirement gathering and fully understanding of the expectation of the customer. A product backlog is created, with the list of product requirements. The technical vision is documented and a high level system architecture and design are established.
The following project criteria are established in this stage:
Project Incremental Development
At Stigasoft our development teams work according to a well-defined methodology which manage and control software and product development using iterative, incremental practices. This process significantly increases productivity and reduces time to benefits while facilitating adaptive, empirical systems development. The Stigasoft development methodology is designed to be flexible throughout the project. It provides a control mechanism for planning a product release and then managing variables as the project progresses. Development is planned and executed in short cycles called Sprints or iterations.
Creation of a task backlog
The work is organized into a living backlog: the list of requirements or user stories. The backlog is prioritized by the Product Owner according to business needs. The goal is to deliver first what it is the most valuable to the Client, to get the best ROI.
Sprints
Review
By the end of a sprint, the team demonstrates the increment to the Product Owner and Stakeholders. Feedback is gathered as to make the necessary improvements to the product and the process.
Retrospective
A brief lessons learned meeting takes place, at which all team members review the sprint and plan short term actions to perform better.
Release Iteration
A release cycle includes many iterations (typically 4 to 6). For every release to a production environment one more iteration is planned to do thorough testing, bug fixing and final tuning. During the release iteration, no new features are developed.
Distributed Agile
We use collaboration tools to make offshore and onsite teams work together in an efficient way. Agile teams are typically of 5 to 10 members. Projects that require larger teams are organized using many small teams, probably at different locations. In such scenario, scrum masters meet together in a "scrum of scrums" meeting to coordinate teams.
Some of the tools used to make this integration possible are:
Support Processes
During the execution of the project, different support activities are carried out:
Agile takes is edge over conventional waterfall model by focusing more on:
As a result, it delivers following advantages in product development:
