Jon Eversett discusses what is and why we need a Definition of Ready

Definition of Ready is a term that has emerged recently in the Scrum / Agile community. In this episode we discuss why that concept is important, and how it can help teams improve their performance. We also discuss why planning a little bit in the Sprint is better than trying to plan the whole sprint up front.

About Jon Eversett

scrum_master_toolbox_podcast_Andy_Deighton Former Business Analyst, Product Owner wannabe, currently a Scrum Master. Jon works with teams with different maturity levels and some relatively new Product Owners. You can find Jon Eversett on LinkedIn, or interact with Jon Eversett on Twitter. You can read Jon Eversett’s blog to find out more about his ideas on the role of the scrum master and all things agile.

Neil Killick how important it is to ask questions and how easy it is to forget that

We don’t ask questions often enough, and in this episode Neil explains why that is so important. Neil tells us a story of a project that started well, continued well, everything seemed to work well, until…
He discusses how one small detail derailed the whole project, and how to avoid that in the future.

About Neil Killick

scrum_master_toolbox_podcast_Andy_Deighton Neil has been a software professional for over 18 years, mostly as a developer, before moving to management. He spent the last 5 years being a passionate Agile, Lean and Scrum coach, trainer and practitioner. Neil cares deeply about creating enjoyable, authentic workplaces in which human potential can thrive.
You can connect with Neil Killick on twitter. Neil Killick’s blog.

Stephen Thomas shares his recipe to help the organization adopt scrum and engage with the scrum team

How do we help organizations to recognize the value that scrum teams can bring, and the obstacles they face in the process? Stephen Thomas shares his recipe and describes a few ideas of how the retrospectives can be an effective practice to help organizations evolve and get better.
Stephen’s recipe for organization improvement:

  1. Help the teams understand their progress with a physical (as opposed to digital) and visual burndown (colorful if possible).
  2. Write the principles on the wall and make sure people see them regularly. Point to them when needed.
  3. Have lots of wall space for teams to use and create their shared view of their work.
  4. Help start and facilitate organization-level retrospectives, because improving one team is not enough for lasting change.
  5. Make the team independent

Before implementing all of this, make sure that the organization has the necessary knowledge to work in an agile manner, helping organize training if needed, and working with stakeholders regularly.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.

Stephen Thomas defines success for Scrum Masters and how he came up with the definition

Defining success for scrum masters is not easy, but it is necessary for us to achieve it. Does it have to do with reaching the sprint goal? Or a regular daily goal? Can a scrum master be successful when the team does not release software regularly? And how about the customer’s view? How can the customer help us define and assess success as Scrum Masters?
Stephen shares how he struggled to define success for him as Scrum Master, and why that was hard.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.

Stephen Thomas on why the recruiting interview is not a good idea

What should we do to help choose the best people for our teams and organizations? Especially if we already believe the recruiting interview is not the best possible, or even most effective method to bring out the best in people. Stephen has a few ideas on how to prepare for the recruiting process, and how to setup a way to watch the candidates in action before finalizing the recruitment process.

About Stephen Thomas

Stephen Thomas Scrum Master toolbox podcast Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.

Mario Lucero explains how taking ownership can make the difference for agile teams

Scrum masters help teams when they create an environment where teams can, and are willing to take ownership and responsibility for what they deliver. Teams that take ownership are then ready to start solving their problems.

About Mario Lucero

Scrum_master_toolbox_podcast_mario_lucero
Mario Lucero is an Agile evangelist who wants to help people adopting agile (Kanban or Scrum). He’s worked with Agile since 2010 in a distributed software development environment.You can find Mario Lucero on Twitter. Mario Lucero in LinkedIn. Mario also writes a blog at: mariolucero.cl.

Mario Lucero shares some symptoms of problems in team dynamics

Team dynamics are affected by many factors, including certain individual behaviors. Teams that exhibit some of the symptoms referred by Mario may be in trouble. We need to learn about those symptoms and have strategies to deal with those.

About Mario Lucero

Scrum_master_toolbox_podcast_mario_lucero
Mario Lucero is an Agile evangelist who wants to help people adopting agile (Kanban or Scrum). He’s worked with Agile since 2010 in a distributed software development environment.You can find Mario Lucero on Twitter. Mario Lucero in LinkedIn. Mario also writes a blog at: mariolucero.cl.

Mario Lucero shares lessons learned about distributed agile development

This story starts with an US based company acquiring a Latin American software development organization. Mario shares what happened after that, and what he learned from the experience, where distributed agile development was the main method of development.

Books mentioned in this interview:

Mario also talks about videos that are worth watching, here are some:

About Mario Lucero

Scrum_master_toolbox_podcast_mario_lucero
Mario Lucero is an Agile evangelist who wants to help people adopting agile (Kanban or Scrum). He’s worked with Agile since 2010 in a distributed software development environment.You can find Mario Lucero on Twitter. Mario Lucero in LinkedIn. Mario also writes a blog at: mariolucero.cl.

Jeff Kosciejew on retrospectives as the core practice for self-improvement

Jeff Kosciejew discusses the three key questions for defining success and shares how his experience as a musician informed the definition of success as a Scrum Master. A very inspiring story of how Scrum Masters can fundamentally affect their team’s performance and each of the team member’s well-being.

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.

In case you are interested in Agile Retrospectives we are at the moment preparing a 10 DAYS FREE AGILE RETROSPECTIVES PROGRAM. This is a complete self-study program where you will learn anything that you need to become a great Agile Retrospectives facilitator.

Jeff Kosciejew and recipe for recruiting success: trust your gut and list your skills

Jeff Kosciejew shares his own, hard-earned, experience on how to hire great people. Including how to know in advance what skills you need, using conversation as a way to filter out candidates that are a bad fit and the Agile Coaching Competency framework. His most important question in recruiting interviews is one he asks himself: “will this Scrum Master fit our culture?”

Agile Coaching Competency Framework

Lysa Adkins from the Agile Coaching Institute has been developing an Agile Coaching Competency framework. Read more about it at the Agile Coaching Institute site.

Using NPS to evaluate your work as an Agile Coach

Jeff, also refers to Jason Little’s personal Agile Coach NPS, a way to evaluate your own impact in the team and organization you work for.

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.