the underlying reason for global to have a podcentric view comes from this idea of putting the org chart upside down so the pole is at the center of lowent and how everybody is at the service of the body globe and pods maturity framework ensures that every board is aligned to the client needs from the first activity which is the pod constitution where the bot defines its purpose the principles and the roles of each member the pod constitution helps team members understand how their work connects with the business this leads to a sense of empowerment and
belonging for the team which results in better delivery and commitment having a talented people all together with different profiles with enough empowerment and autonomy really help us impact on the end user and have a meaningful you know products and engagement with with those final customers the pods framework empowers the team through a sense of belonging that eventually leads to better delivery and commitment the maturity framework provides a set of tools and ceremonies for the paths to foster their autonomy by allowing them to set their goals experiments on approaches and measure their results it's not that
it's different from other agile methodologies it's just that it has been adapted to our context in order to transmit what we want to do and how we want to help our clients as a company in larger accounts we see that it's crucial the understanding that it gathers from its ecosystem it's only joining a portfolio that has already some knowledge in terms of business goals and what's happening in the environment this is going to help the bot learn um continuously in terms of what is happening around it and what needs to be improved we collected a
lot of tools and best practices and the framework put all together to help bring consistency across you know all the pots all the accounts all the projects it's robust enough that it it works for everybody and it's flexible enough so we can adapt it to different situations and different natures of projects in each monthly review the portfolio team will collaboratively evaluate results not only in terms of software delivery metrics but also in terms of business goals in this stage we think of what are better ways to partner what is the stakeholders relationship all of that
built into the status with this information each bot will have a way to assess their status and find what needs to change and what needs to be adjusted so from the get go the idea of the pod is to grow and to have constant contact with the client they feel that they are close to their parts for us as a company and working with globent and leveraging experience was to embrace modern agile practices it was a new approach a new methodology and it does go to the culture right it changes the culture of your company
to be able to infuse that excitement about agile the processes was very good for our culture to evolve as a software company we like to say that glowant is always in beta and this applies also to the framework we are constantly reviewing the framework and and also experimenting with new types or new practices or new areas of focus where our teams need to be looking into as a next step in our maturity framework roadmap we are building applications that will help getting that feedback from the clients in an easy and seamless way and for the
pot to be able to experiment and to adapt to it as soon as possible ethically and for excellence have fun constantly innovate be a team player think big all our values are embedded in our pod [Music] framework
