Khaja Mohiuddin reminds us that some organizations are just not ready to change

In this episode Khaja shares a story of a team that was only a team in name. Their setup was influenced by a manager that did not get Agile. How to handle such a situation? Khaja shares his recipe for handling such situations, and advises us to be careful as some organizations are just not ready to change.

About Khaja Mohiuddin
An accomplished and fluent communicator with strong investigation, problem-solving and decision-making skills. Managing the work from initial request through estimation, approval, requirements, build and implementation.

You can link with Khaja Mohiuddin on LinkedIn.

Peter Götz explains why sometimes, our intuition is our best friend

Intuition is said to be the symptom of knowledge meeting experience in a sudden burst of creativity (actually I just made that up ;). What is the role of intuition for us as Scrum Masters? Specifically, how can intuition help us understand the system that affects the teams we work with? Listen in for a trip to the 3rd dimension of being a Scrum Master. Oh, and happy friday! 🙂

About Peter Götz
Peter is working as a consultant, trainer and coach based in Munich. He started working as a Java software developer in 2001, changed to consulting in 2006 and has been working as software developer, software architect, technical project manager or team lead. He is a Professional Scrum Trainer at scrum.org and supports teams in adopting Scrum since 2008.

You can link with Peter Götz on LinkedIn and connect with Peter Götz on Twitter. And our listeners in Germany can find Peter Götz on Xing.

Peter Götz shares practices used by successful Scrum Masters

Peter has a specific perspective on the Scrum Master role that is influenced by his own role as an external consultant that comes in to help a client reach certain goals. In this episode he shares with us what he has learned from that experience as well as the practices he now takes into use when in such an assignment.

About Peter Götz
Peter is working as a consultant, trainer and coach based in Munich. He started working as a Java software developer in 2001, changed to consulting in 2006 and has been working as software developer, software architect, technical project manager or team lead. He is a Professional Scrum Trainer at scrum.org and supports teams in adopting Scrum since 2008.

You can link with Peter Götz on LinkedIn and connect with Peter Götz on Twitter. And our listeners in Germany can find Peter Götz on Xing.

Peter Götz shares patterns of successful change processes

Peter has gone through many change processes in his career, but in this episode he shares one specific process that helped him improve his own approach to change management. He shares some of the patterns implemented back then that are still used today by him in his work.

In this Episode we refer to the #NoEstimates movement and #NoEstimates book as well as the the book Non-Violent Communication by Marshall Rosenberg.

About Peter Götz
Peter is working as a consultant, trainer and coach based in Munich. He started working as a Java software developer in 2001, changed to consulting in 2006 and has been working as software developer, software architect, technical project manager or team lead. He is a Professional Scrum Trainer at scrum.org and supports teams in adopting Scrum since 2008.

You can link with Peter Götz on LinkedIn and connect with Peter Götz on Twitter. And our listeners in Germany can find Peter Götz on Xing.

Peter Götz from fixed project disaster to a great team

A pattern that we often see is that of the silo-thinking and lack of common, shared goals in the teams. Peter shares such a story as well as the steps he took to climb out of that whole and build a great team that is still in contact with him to this day.

About Peter Götz
Peter is working as a consultant, trainer and coach based in Munich. He started working as a Java software developer in 2001, changed to consulting in 2006 and has been working as software developer, software architect, technical project manager or team lead. He is a Professional Scrum Trainer at scrum.org and supports teams in adopting Scrum since 2008.

You can link with Peter Götz on LinkedIn and connect with Peter Götz on Twitter. And our listeners in Germany can find Peter Götz on Xing.

Peter Götz shares an important story about distributed software development

There are so many pitfalls in Distributed Software Development (DSD). Peter shares with us a true story of his own life as a “proxy” between local business and remote software team. He also shares with us what he learned from that experience that he tries to use when in similar settings today.

About Peter Götz
Peter is working as a consultant, trainer and coach based in Munich. He started working as a Java software developer in 2001, changed to consulting in 2006 and has been working as software developer, software architect, technical project manager or team lead. He is a Professional Scrum Trainer at scrum.org and supports teams in adopting Scrum since 2008.

You can link with Peter Götz on LinkedIn and connect with Peter Götz on Twitter. And our listeners in Germany can find Peter Götz on Xing.

Ruben Betancourt reminds us that when we are lost, we can ask for help

Mapping out the system conditions, or even understanding what is going on in the team is not an easy task. But without that, can we really help the team? Ruben reminds is that we can use peers to find the solutions that are illuding us. In the process, make sure that you listen to the team’s experience. After all, they are in a journey that goes beyond your involvement. Step into their shoes before you try to help them.

About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.

Ruben Betancourt measures these 2 things to check his personal contribution

Would you drive to a new location without knowing where it was, and without a map to help you get there? This is where many of us are regarding our own success and impact as a Scrum Master. Ruben shares his 2 most important metrics to measure his success and impact as a Scrum Master. Which ones do you measure?

About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.

Ruben Betancourt on how to avoid failing sprints

Sprints fail for many reasons, and in this episode we explore one specific Anti-Pattern: “the disengaged PO anti-pattern.” How do we bring the PO into the work of the team, to ensure that we are always progressing in the right direction, instead of finding at the end of the Sprint that we were missing some critical information.

About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.

Ruben Betancourt on how slicing Epics into smaller deliverables can increase your chance of success

It’s hard enough to deliver a small increment of a product, yet we often find ourselves and our teams in positions where they need to deliver a whole product, project or release in 1 go. No change for mistake. And you know what happens: when failure is not an option, failure is the only option!

About Ruben Betancourt
Ruben Betancourt is a computer systems engineer with experience in project management. Currently in love with agile software development methodologies.
You can link with Ruben Betancourt on LinkedIn and connect with Ruben Betancourt on Twitter.