Towards an agile methodology

Nowadays projects are defined from the beginning with a tentative time for delivery, time in which the client / stakeholder in it only reports the result months after its preparation and delivery; In this fact, there is a tendency to fall into “adjustments” that involve taking a time greater or equal to the development in the worst case and shows a high expectation of the client.

All these factors lead to a product at the end of its development cycle ending up with different expectations from the client and it is in this case where it becomes clear what was really expected of it; Having said this, there is a more “dynamic” way where the client is showing the evolution of their product and where doubts are cleared during the development cycle: using a methodology such as Scrum.

Customer and team activity planning diagram comparing development deliverables and customer reception

Why Agile Methodology?

An agile methodology comprises a more dynamic and evolutionary development comprised in iterations or what is called partial delivery of the product before finalization. An iteration or cycle is also called a Sprint.

“By using an agile methodology such as Scrum, the client interacts with the deliveries and shows partial results of the final product”

This means that in a Sprint the product is developed, once it is finished it is delivered to the customer; When Sprint 1 starts, the product is delivered to the customer while in the same Sprint, work is carried out in parallel on the development of the next delivery.

By using an agile methodology such as Scrum, the client interacts with the deliveries and evidences partial results of the final product, thus, in case of requesting an adjustment, it is not necessary to wait until the final delivery but it can be added to a Sprint to be developed and later see what is expected.

This is how the agile methodologies SCRUM presents a paradigm shift in terms of customer expectations and this generates a better result and direction of the vision of the same.

Natalia Mera

Software Project Management Specialist @Natalia Mera

Related articles