Jeremy Jarrell on how Scrum is a method to understand how the system behaves

To understand how the system behaves we must “poke” it, and Scrum is just the perfect method for that. Every sprint is an experiment that helps the team and the Scrum Master understand how the system behaves and reacts to the different experiments that we run every sprint. Jeremy has a collection of metrics he follows-up regularly to keep in aware of how the system behaves, and enable him to actual test new approaches every sprint.

About Jeremy Jarrell

Jeremy Jarrell is an agile coach and author who helps teams get better at doing what they love. He is heavily involved in the technology community, both as a highly rated speaker as well as a syndicated author whose articles and videos have appeared on numerous popular websites.
You can connect with Jeremy Jarrell on twitter, and link with Jeremy Jarrell on LinkedIn. Jeremy’s web-site is at www.jeremyjarrell.com.
Jeremy’s latest video course, Agile Release Planning, is available now from FrontRowAgile.com.

Wayde Stallmann shares how he accepts mistakes as gifts

Mistakes are part of the process of learning, we all know that. But Wayde goes further and challenges us to accept them as gifts, not just part of the process. Listen how Wayde tackles mistakes when they happen to help the team accept, and build on those mistakes rather than try to recover. This mental shift can have a huge impact on team’s performance.

About Wayde Stallmann

Wayde is an Agile coach with TeamFirstDevelopment.com. He is interested in helping teams improve using the same techniques that Improv theater teams use to develop Great Team Players.
You can connect with Wayde Stallmann on twitter, or link with Wayde Stallmann on LinkedIn. Or email Wayde Stallmann at wayde@wayde.com.

Antti Tevanlinna is successful by increasing the speed of feedback

What defines a successful Scrum Master is how much they can help the organization increase the speed of feedback. As Antti says: “we often don’t really know what the customer wants!” So, measure your success by measuring the speed of feedback. Is it increasing?

About Antti Tevanlinna

scrum_master_toolbox_podcast_Andy_Deighton Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.

Andy Deighton on how to help Scrum Masters grow

Andy discusses how hard it is to hire, and how we must constantly help Scrum Masters grow in their practice. Even if the Scrum Master is doing a good job (and also because of it), the teams will evolve. The style of the Scrum Master must then match that team evolution.

About Andy Deighton

scrum_master_toolbox_podcast_Andy_Deighton Andy has over 20 years of development experience in Smalltalk and Java, and is now a Scrum Master at Bright Interactive, based in Brighton on the south coast of the UK. He’s a former professional photographer and budding songwriter. You can find Andy Deighton on twitter. Connect with Andy Deighton in LinkedIn.

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 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.