Tiago Palhoto

Tiago Palhoto is currently an Agile Coach and methodologist at the European Commission, Brussels. He started his “Agile adventure” in 2001, when came across RUP for the first time. Since then, as a Project Manager and Process engineer, he always tried to look not only for new and more efficient ways to get the work done but also to optimize teams performance. With almost 15 years of experience in Software development processes, the acquired experience as Project Manager, Business Analyst, Tester and System analyst, gives him the necessary tools to help teams and organizations to embrace agility, especially through the use of SCRUM. An Agilist by nature, a generalist by option, he values trust and commitment in everything that he does. He’s a leader and he always try to inspire people to give their best as individuals but also as a team. With 17 years of experience in IT, he’s passionate about the entire software development process. The final result ends with him trying to help anyone to understand the importance of being agile and to become an agilist

The four ways to successfully engage stakeholders!

–Synopsis
Come and see how a simple set of tools and techniques can help you boosting stakeholders productivity and have them FULLY involved and committed with the project!!

–Long synopsis
Throughout the years, I’ve realised that teams are becoming more and more aware of how important is to properly embrace any Agile framework. Using proper engineering techniques like continuous integration or automated testing, not disregarding the retrospectives or have effective planning meetings with the stakeholders, are some of the most frequent examples.

Despite all of this, there’s one aspect that I believe it hasn’t been properly tackled by most of the teams: An effective stakeholder’ engagement in the context of an Agile framework. In other words, teams seem to forget that having the stakeholders completely familiarised with the framework being used is the most powerful way of engaging them throughout the entire project.

With this presentation, I’ll describe the four simple techniques that I’ve been using since always in order to have stakeholders’ trust, involvement and commitment.

– Introducing the framework – Because introducing new concepts and a new approach to software development can turn the customer’s mission a bit more complex, I put a lot of effort making sure that the customer is familiarized with the foundations;

– Calendar of activities – Making sure sure that the customer understands how critical his role is in the following activities: Planning meeting, User stories workshops, backlog Grooming sessions, Backlog prioritization, Review meetings;

– Inputs during the sprint – Informal reviews of the system boost your stakeholders’ trust and commitment with the project;

– Define Stakeholders’ schedule – Set up your stakeholders’ agenda right from the beginning, so that they don’t have “excuses” not to comply.