Agile Development Methodology Scrum
Every project or idea, regardless of its nature, brings new challenges and involves new perspectives, which “forces” each team to create or adapt to new ways of working…
At Wigilabs, we adopt an agile Scrum methodology, creating the right environment for the development of each project, along with a simple system for monitoring and continuous support.
Each practice is based on fundamental agile development principles:
- Evolutionary management of progress.
- Working by basing the quality of the result on the tacit knowledge of people, rather than the explicit knowledge of processes and the technology used.
- Incremental development strategy through iterations (sprints) and reviews.
- Step-by-step development: from the client’s overall vision to product construction through phases of speculation, exploration, and review (sprints).
The framework generated around this methodology allows for the creation of quality products in short periods of time, requiring continuous effort from all team members.
How does this management work?
- Iteration Review: functional review at the end of each sprint.
- Incremental Development: at the end of each iteration, we obtain an operational part of the product that can be used, inspected, and evaluated, as a working technique to facilitate evolution without degrading the quality of the architecture and allowing it to evolve during development.
- Self-organization: based on predictive management and our methodology, teams are self-organized, gaining the ability to make timely decisions.
- Collaboration: All team members collaborate openly with others, according to their skills and not their role or position.
Common Purpose
As part of our work philosophy, the team shares a common purpose: to achieve the greatest possible value for the client’s vision. And to ensure this is fulfilled, each member involved in every idea or project keeps the following in mind:
- Everyone knows and understands the product owner's vision.
- They contribute to and collaborate with the product owner in the development process.
- They jointly share the objective of each sprint and the responsibility for achieving it.
- All members participate in decision-making.
- Everyone’s opinions and contributions are respected.
- Everyone is familiar with the work model.