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 the systems that put pressure on software developers will not enable high quality deliveries.

In this episode Dmytro describes how the system impacts the teams and the software deliveries. He explains that in order for the teams to deliver a great quality they must be part of a system, which allows them to experiment and develop features without the daily pressure.

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 being part of a team that is improving can be used as tool to measure Scrum Master success

Dmytro explains that being part of a successful team is part of a Scrum Master success. After all, it is his job to create successful teams. Dmytro also gives us some good tips: in order for Scrum Masters to continue improving, they should develop themselves in areas where they feel they are not so strong. They could take some time to analyze their weakness and take some training to tackle those areas.

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 the Scrum Master should be a leader in order to be a successful change agent.

Dmytro explains how Scrum Masters should be leaders in order to be good change managers. Their work should not be limited to the job: a good scrum master and a good leader is involved in many other activities within the community.

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 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 Agile Retrospectives can be used to understand the company system

Agile Retrospectives, in Pedro´s opinion, are a great way to help teams to understand how they interact with the company system. They are a great tool to identify dependencies, interactions and even politics.

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

Pedro Torres talks how Scrum Master role contains many things that do not allow success to be measured

“Not everything that counts can be counted, and not everything that can be counted counts”, Albert Einstein says. The Scrum Master role contains many things that do not allow success to be measured… For Pedro a success is to watch himself at the mirror and see himself smiling. When he reaches a daily meeting and he sees that the team is smiling, happy and having fun on a positive, that is the success!

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

Pedro Torres talks how every Scrum Master should be a change agent

Every Scrum Master should be a change agent… Unfortunately, many companies see the Scrum Master as a secretary or a team organiser. The Scrum Master as a change agent can help the organisation, especially the senior management, with the mindset transition. Roadmaps in Agile do not make so much sense; Agile Portfolio Management is a better approach in order to help the company to be more successful and that is a huge mindset change that can be initiated by Scrum Masters.

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