#1 Interview with Pedro Paiva adopt An Agile Approach: Scrum Methodology

some test

Agile development methods are iterative, incremental and person-centered. Their application aims for a better customer satisfaction, as well as the realization of a software fully functional at every step of its manufacture.

Scrum was originally outlined in an article published by two Japanese researchers and was named after an analogy made with rugby.

It is the most used methodology among existing Agile methods. It favors the development of a product one can confront with the market as swiftly as possible.
Pedro, Microsoft developer and Scrum Master, explains how he implemented this methodology within Technology Partner.

Pedro, can you explain the basic principle of the Scrum methodology in a nutshell?

It is a dynamic and participative approach, the basic principle of which is to be always ready to redirect the project as it progresses.
This methodology favors the development of products corresponding to the actual demand of the customer which is undeniably an advantage in the management of a project.

It also allows everyone to participate in the evolution of the project instead of having the Project Manager alone define the evolution of the project and the group work.

Why participate in this agile transition (before, now and in the future)?

When I arrived, a more traditional project methodology was used. Its logic offered less flexibility to follow the evolution of the client needs. This can result in a discrepancy between the delivered product and the final need.

Thus, I worked hand in hand with the teams to fully apply the foundations of Agility, and Scrum more specifically. My goal is to ensure a close relationship with customers. This logic gives the project room to grow as well as the flexibility to adapt to the evolution of customer expectations. It also provides additional visibility on the progress of the project.

The agile methodologies used in IT since the early 2000s should be, in my opinion, a standard extended to every part of an organization.

What challenges did you encounter during the implementation of this methodology?

The Agile methodology is easy to understand but difficult to implement. Thus, we chose a step by step approach. We started with Daily Scrums, followed with the addition of Sprint Planning, progressively added Sprint Reviews, and then the Sprint Retrospective.

This process requires time, patience and involves an in-depth change of the exisiting management system. Collaborative, iterative and constructive work are my essential ingredients to develop strong trust with the protagonists and make a lasting and efficient change.

What are the benefits of this methodology?

Agility brings a well-defined role and well-assigned tasks to each employee which allows efficient organization and better satisfaction of customer expectations.

In addition, the team spirit is put forward! Indeed, the whole team must feel involved and motivated because it is directly integrated into the management and evolution of the project.

The budget of the project will be respected which is not necessarily the case when one adopts other methodologies requiring budget supplements on specification changes.

Finally, I would say that this approach gives priority to the tasks performed daily in each of our projects.

Can you come back on your career, until you arrived at Technology Partner?

I made my debut as a Software Developer in the logistic sector in Portugal. I had the opportunity to practice in this environment as part of the development of web and mobile applications.

Later on, I took a challenging position as a Strategic Account Manager in the banking field where I encountered the Scrum methodology for the first time.

I finally arrived in Luxembourg to build the architecture of new .NET projects, and joined Technology Partner, business unit of Linc SA as Scrum Master to help them implement the best practices.

What are your values and aspiration for the future?

In my job, I give a special place to customer satisfaction. “The concerns and successes of my clients are mine too.” I like to challenge a lot the projects I take part in to achieve the best result possible. Going all the way is essential for me and I care about building trust and transparency within the team.

In the future, I intend to take on a Scrum Master position in larger projects. Pedagogue and committed, I would like to, on a medium term, become an agile coach.