Ask A Professional Scrum Trainer – Martijn van Asseldonk – Answering Your Most Pressing Scrum Questions

In this episode of Ask a Professional Scrum Trainer, PST Martijn van Asseldonk answered the pressing Scrum questions from the audience. Some of these questions included.

  • How does Scrum work with virtual teams?
  • How did you become an agile coach?
  • How do you help leadership adopt the agile mindset?
  • How do you measure teams?
  • What’s the best way to do estimation?

Asking the right questions; how to help a Scrum Team switch from a technical to a functional Backlog

One of the biggest challenges for a Scrum Team is to switch from a technical to a functional perspective on their work. Christiaan Verwijs has developed a set of helpful questions that often trigger teams into a functional frame of mind.

  • Why is it important that we implement this?
  • What problem of stakeholders and/or end-users do we solve by doing this?
  • What personas benefit from this, and why? (given that you have personas)
  • How would sales explain the benefits of this to customers and/or users
  • What reasons would an end-user have to want this?
  • How would you explain this to a colleague who is not part of this project?
  • How would you explain this to your spouse, at home, after a hard of work?
  • What would you show during the review to demonstrate that this is working?
  • If you are a user, how would you test if this works?
  • What changes would a user notice after implementing this?
  • What stakeholders benefit from this, and why?
  • If we wouldn’t do this, what would end-users and or customers miss or be unable to do?
  • What compliment would a happy user of customer give after delivering this?
  • How would you explain this to a potential end-user?
  • What steps would you go through in the application to test if this works?
  • If we’d put this in release notes that will be read by end-users, how would we announce it?

Read the original article here: https://medium.com/the-liberators/asking-the-right-questions-how-to-help-a-scrum-team-switch-from-a-technical-to-a-functional-bee6c1598487

Six Agile Product Development Myths – Busted

In this article Mike Cohn busts six agile product development myths:

  • Myth #1: Isn’t Agile Just for Software Development?
  • Myth #2: Is It True That Managers Have No Role in Agile?
  • Myth #3: Can’t Stakeholders Introduce Change Whenever They Want?
  • Myth #4: Doesn’t Everyone Need to Be a Generalist on an Agile Team?
  • Myth #5: I’ve Heard that Agile Teams Don’t (or Can’t) Plan.
  • Myth #6: Don’t Agile Teams Create Products with No Architectural Plan?

Find the complete article here: https://www.mountaingoatsoftware.com/blog/six-agile-product-development-myths-busted

Nine Questions Scrum Masters and Product Owners Should Be Asking

In the following article Mike Cohn shares his favorite questions to ask: https://www.mountaingoatsoftware.com/blog/nine-questions-scrum-masters-and-product-owners-should-be-asking

Two Questions about Estimates

  • I’m not looking for an estimate. But if I asked for an estimate, what unit pops into your minds: Hours, days, weeks, months, or years?
  • How confident are you in that estimate?

Three Questions About Team Decisions

  • What are three other options you considered before making this decisions?
  • What’s the worst thing that could happen if we pursue this direction?
  • What has to go right for this to be the best decision?

Two Questions about Meetings

  • Do we need everyone who is here now?
  • Should anyone else be here?

One Question to Ask When Wandering Around

  • Does anyone else need to know about this?

One Question to Ask During Daily Standups

  • What do you know that I don’t know?

The Agile response to “How much will it cost, and when will it be done?”

Reading time: 3 minutes

The right answer to the question about scope, budget, and deadline is not to go along with the line of thinking that’s behind it. Instead, offer management a better way to manage the risks of a project. Offer them a visible and transparent process like Scrum that allows for frequent change and makes the progress of teams visible on a transparent backlog. Scrum will not magically make your project succeed, nor will it prevent mistakes and failures, but it will make them less costly because you can detect them more frequently as part of the iterative nature.

Read the complete article here: https://medium.com/the-liberators/the-agile-response-to-how-much-will-it-cost-and-when-will-it-be-done-86d907573871