Ricardo explains that if you do not have poising people in the team performance in his experience its always driven by the system.

By his experience every time a team was not performing the reasons were related with a poor system. Before we blame people we should look into how the organization is assembled.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Ricardo defines success of a Scrum Master as the capacity of helping the team to ship software fast and with quality

If a team is able to ship a product day after day, with increased quality and increased velocity this is a clear sign, at least for Ricardo that he is doing a good job as Scrum Master.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Ricardo Fiel explain us how important the job of Scrum Master is.

Ricardo tells us that a good Scrum Master is not the one that is there to solve all the problems but the one that help the team to solve their own problems. Being always there for the team will not help the team to become self organized.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Ricardo Fiel explains how a culture of blame leads teams to failure and self destruction

Ricardo tell us a story of a company where he worked where blame was part of their job. He explain us how that culture drove teams to self destroy.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Ricardo Fiel tells us the biggest learning comes from trying out new and not be afraid of failing

Ricardo explains how he failed with one of his previous teams, and how this failure led him to understand that trying out new approaches is a key factor for leaning and improvement.

About Ricardo Fiel

Ricardo has 12 years experience in software teams, He had multiple roles from developer to architect to CTO, working in both startups and global corporations. He led teams from 4 to 30 members. Currently, he leads product development (SaaS) teams at Rupeal. You can find Ricardo in linkedin or twitter.

Dennis Mansell talks how a semi destructive team is even worse than a complete destructive team

Dennis discusses that most of the times when we start to work as a team, we simply put people together expecting that everything will work. We even forget to ask if people do actually want to work together. In this episode he explains how that can go wrong.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dennis Mansell tells us how you can be fired for not spending all the project budget

Dennis explains us how most of his learnings came from failures. In his story he explains how he lost a project because he spent only 10% of the total budget. As an outcome, spending just this small part of the budget led Dennis to loose his job.

About Dennis Mansell

Dennis did not start his working life as a developer, but as a sailing yacht skipper and owner of a sailing school and he still trains yacht-racing teams. He always supplemented his sailing job with application maintenance, web development and project management. He has since settled down: based in Amsterdam with his wife and son. Now he works as a full-time Scrum Master and Agile Coach for companies ranging from start-ups to the Dutch governmental institutions. His linkedin and twitter: @dennmans.

Dmytro Orlyk talks how bringing more people to a project usually results in a disaster

Dmytro explains that one of the big reasons for team failures appears when a management put extra people into an ongoing project that is late. He mentions this approach was proven many years ago to not be the right approach, yet many teams suffer from this mistake.

About Dmytro Orlyk

Dmytro have an overall 4 years of experience in PM. His latest project has been shown to the Google company. He is an Agile Expert with a strong knowledge of Scrum, Kanban and XP. Few of the engineers that inspire me are Martin Fowler and Chris MacConnell. He can be found in linkedin.

Dmytro Orlyk talks how technical debt can cause the team to fail

Dmytro explains us how technical debt can be one of the reasons for teams to fail. One of the tips that he give us is to make sure the team has extra time during the sprint to tackle issues that were not planned in the beginning and will appear during the sprint.

About Dmytro Orlyk

Dmytro have an overall 4 years of experience in PM. His latest project has been shown to the Google company. He is an Agile Expert with a strong knowledge of Scrum, Kanban and XP. Few of the engineers that inspire me are Martin Fowler and Chris MacConnell. He can be found in linkedin.

Pedro Torres talks how Ego is one of the common problems that can cause teams to self destroy

Ego is one of the common problems that can cause teams to self destroy. If team dynamics are not well handled it´s quite easy to see brilliant developers becoming “prima-donas”; they feel they are like a god on the earth. At the end, it does not matter who does the work, what matters is a team´s outcome. When there are such “divas” on the team they feel that everyone should be thankful for having them on the team.

About Pedro Gustavo Torres

Pedro Gustavo Torres is an Agile Coach @ SONAE, in Porto, Portugal.
He started his agile quest in 2010. He’s a seasoned Scrum Master, Agile Coach and Trainer. He also has experience acting as a Scrum Product Owner. He’s passionate about scrum, agile and all the practices that can help teams deliver early value to their customers. He is also quite techie and a gadgets fan. You can find him in linkedin. He writes his learning’s on his blog. His twitter: @_pedro_torres