Ruben Sadoyan on how fixing symptoms can prevent you from actually helping the team

What is the problem we are actually trying to fix? This is not an easy question. We are programmed to jump to conclusions. Many of us are biased towards action but forget to check if our actions are working. All of this leads us sometimes to focus on symptoms. Ruben tells us such a story and how he finally tracked down the real problem that needed fixing.

About Ruben Sadoyan

Ruben has played many different roles in his career. Agile Coach, Team Engineer, Scrum Master with IT Project Management and Software Development background are just some of those. He’s also been an Account executive with software/web development roots and business development, experienced in team and client relationship management.
He’s also launched a startup named Internet Company and has more than 15 years experience in IT. He describes himself as Focused on constant improvement and self-education. Result driven, able to lead in a Lean way, identify root causes and gradually improve teams to make results happen.

Dennis Wagner defines success for Scrum Masters with the help of 2 key tools

To define success for us as Scrum Masters we need to define also what it means not to succeed. Dennis defines what is failure, and uses 2 concrete tools to check the situation all the time. The tools are 5 Why’s and a simple powerful question: “how are we succeeding?”
Each of these tools tackles a different purpose that Dennis explains in this episode.

About Dennis Wagner

Dennis is an Agile Coach with a lot of experience in the technical side of software development. Dennis has worked with teams in different industries, is thinking of writing a book about continuous delivery (bug him if you want to know more), and he loves, really loves his work.
You can connect with Dennis Wagner on LinkedIn and XING, and you can connect with Dennis Wagner on Twitter.

Matthias Seul on why metrics and the questions we ask are our best friends

When trying to understand the system that affects our performance we can’t stay at the surface level. We need to dig deeper to find the real causes for performance problems. Matthias suggest that we measure our system to find what questions we should ask, and then ask “Why?” to help us understand that system.

About Matthias Seul

Matthias worked 10+ years as software developer and gravitated towards coaching in recent years. He is a tech enthusiast, board gamer, inventor and wild duck. Matthias believes in intrinsic motivation – thus he believes in Agile. He says that “together we can make projects a more fulfilling and successful work environment for all involved”.
You can link up with Matthias Seul on LinkedIn, and reach Matthias Seul on twitter. Matthias is interested in your questions and feedback, and you can reach him via email as well.