Meet Alejandro Narmona, one of our Project Leaders, and discover how SCRUM can help you on your projects

Agile software development refers to engineering methods based on iterative and incremental software development. Scrum is a management strategy where regularly apply a set of practices to enhance collaborative work and obtain the best possible result in the management of a software project.

We did an interview with Alejandro Narmona TISA Project Leader in Software for the operation of Scrum.

We know that Scrum is an agile methodology that allows the customer approximated. What can you tell us about this, you think you can improve the relationship with the plaintiff?

It is an excellent approach, and that strongly involves the interaction with the customer during the development process, and this is a very important process for the column, as is seeing its progress throughout the software lifecycle.

Is this methodology used in TISA?

Yes, it has been used more than 3 years and in various projects

Do you think it improved the performance of the company using Scrum?

Yes, not only the operation of the company, as it promotes the generation of a proactive working group, and increases the internal and external communication of the group.

What are the sprints and why do they serve ?

The Sprint is a period of time in which to perform tasks defined in the group. It must have a fixed length of time, that is, must not change between each sprint. Must be between 2-4 weeks. The idea is to measure the speed of the computer, and to show progress quickly to the customer at the end of the sprint.

Based on that, what is the Sprint Backlog and what is it?

It contains all the requirements that the customer wants for a sprint. You must define priorities and tasks required for that can be carried out the next installment to the end. The tasks in the sprint backlog are never assigned, are made by team members.

Who are the people involved? Does the client may also interact?

Basically, it complies with the development team, which should be at least 3 people and a maximum of not more than 5 or 6 recommended, and the client or a person who interacts with him, called proxy. The client must interact strongly with the development team, it is not optional, it is a requirement of the methodology.

What are the key factors?

Continuous view of the customer throughout the development process, anticipated results, adaptation, and mitigation, alignment between client and team.

Alejandro Narmona - TISA Software Project Leader