Jeff Kosciejew – MobProgramming makes an appearance

The worst enemy of this particular team, according to Jeff Kosciejew, was the pattern of avoidance. Avoiding problems is one of the pitfalls that our teams deal with.
Jeff also refers to #MobProgramming, an innovative practice originally promoted by Woody Zuill.

About Jeff Kosciejew

scrum_master_toolbox_podcast_jeff_kosciejewJeff is a consummate generalist, with experience in a wide variety of industries in a wide variety of roles. Throughout all of his experience, Jeff has had enjoyed success through a single focus on enabling and empowering those he works with, even before being introduced to Agile and Scrum.
You can find Jeff Kosciejew on twitter, and reach Jeff on LinkedIn.

Jeff Kosciejew explains how organizations affect our success as Scrum Masters

On this Fail Monday episode, Jeff Kosciejew shares his ideas on how to look beyond the teams as the focus of our work as Scrum Masters. He also shares his very colorful and diverse history, and how being a Bank Manager helped him become a better Scrum Master.

About Jeff Kosciejew

scrum_master_toolbox_podcast_jeff_kosciejewJeff is a consummate generalist, with experience in a wide variety of industries in a wide variety of roles. Throughout all of his experience, Jeff has had enjoyed success through a single focus on enabling and empowering those he works with, even before being introduced to Agile and Scrum.
You can find Jeff Kosciejew on twitter, and reach Jeff on LinkedIn.

Peter Hilton on tips and tools to understand and change the system around Scrum teams

How do you change the system so that it enables the teams to perform?
Peter discusses how “variation” can affect negatively the team, and what benefits can come from acting on, and reducing variation.

Peter refers to the book where he first read about the effect of variation on work. This book was Freedom from Command and Control by John Seddon

Peter also shares a tip on how to get management to be aware of what is discussed by teams during the retrospective, in order to create trust between management and teams.

The books Peter referred to this week:

About Peter Hilton

Peter_Hilton_Scrum_Master_Toolbox_podcastPeter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.

Peter Hilton on what success looks like for ScrumMasters

Defining what success looks like for ScrumMasters

Peter shares his unusual idea on how measuring the use of the word Scrum can give you real insights to your success as a Scrum Master.

About Peter Hilton

Peter_Hilton_Scrum_Master_Toolbox_podcastPeter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.

Peter Hilton shares his tips for the right questions when hiring ScrumMasters

How to recruit great ScrumMasters

Peter tells us the story of a ScrumMaster that seemed like a good choice but was too shy to help the team grow. He explains how he views the role of the ScrumMaster, and especially what is needed to help them evolve.

About Peter Hilton

Peter_Hilton_Scrum_Master_Toolbox_podcastPeter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.

Peter Hilton describes one of the self-destructive habits of Scrum teams

The team’s self-destructive habit

Being a slave to the backlog, and just going through the motions without interacting with the other team members or stakeholders. This is further amplified in Death-march like projects.

About Peter Hilton

Peter_Hilton_Scrum_Master_Toolbox_podcastPeter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.

Peter Hilton shares his lessons learned from failure

The failure

Product Owners are often given that role because of what they know, but Scrum requires that Product Owners be available to the team. If they are not available that will create problems for the team.

Assigning a Business Analyst as a Product Owner may not be the right choice, especially if that Business Analyst is used to writing requirements “the old way”.

Listen to the podcast for Peter’s experience and insights on the problem.

About Peter Hilton

Peter_Hilton_Scrum_Master_Toolbox_podcastPeter is a software developer and technical project manager who has experienced every point on the agility spectrum, in the course of 18 years of development projects. Peter has performed several variations of the Scrum Master role, and learned what the books dont tell you: whats easy and whats hard.
You can reach Peter Hilton on twitter and read his blog at Hilton.org.uk.