Posts

Posted on

Facilitation Canvas

Anthony Boobier created the Facilitation Canvas as a tool to help facilitators prepare to run a session. He uses it as part of their ICAgile team facilitator course. The canvas is made up of 8 boxes, each with an associated set of prompt questions that I have found work well as a guide when filling it out.

Read all about it here: https://medium.com/path-pattern/the-retrospective-a-known-recipe-for-improvement-with-my-own-spice-da534c6628cc

facilitation-canvasDownload
Posted on

Road to PSMIII

Sjoerd Nijland has written a nice series of blogposts about his road to PSMIII:

Definition of Scrum
https://medium.com/serious-scrum/definition-of-scrum-2d1f224256c

Empiricism: Transparency
https://medium.com/serious-scrum/empiricism-transparency-33adad8fbba2

Empiricism: Inspection, Part One
https://medium.com/serious-scrum/empiricism-inspection-part-one-cc4cd8bf98a8

Empiricism: Inspection, Part Two
https://medium.com/serious-scrum/empiricism-inspection-part-two-fafb785bd0c0

Empiricism: Adaptation
https://medium.com/serious-scrum/empiricism-adaptation-975f044a09b2

Scrum Values
https://medium.com/serious-scrum/scrum-values-1203813e0220

The Scrum Team
https://medium.com/serious-scrum/the-scrum-team-75b8004a4bc2

The Scrum Master
https://medium.com/serious-scrum/the-scrum-master-729e223f4b64

The Scrum Master’s responsibilities
https://medium.com/serious-scrum/the-scrum-masters-responsibilities-7ee05cae707e

The Product Owner
https://medium.com/serious-scrum/the-product-owner-6b7a63fef8fe

The Development Team
https://medium.com/serious-scrum/the-development-team-575d69054a9b

The Sprint
https://medium.com/serious-scrum/the-sprint-40d0ccc895f9

Sprint Cancellation
https://medium.com/serious-scrum/sprint-cancellation-c9a9c66e8c99

Scrum’s Artifacts
https://medium.com/serious-scrum/scrums-artifacts-6f07abfab11

The Product Backlog
https://medium.com/serious-scrum/the-product-backlog-7aec7daf844f

Estimation
https://medium.com/serious-scrum/estimation-103de626551e

Posted on

The Dark Side of the Scrum Guide

Sjoerd Nijland has written a great blogpost about his journey to PSMIII and the nuances in words from the Scrum Guide. Such as:

  • Framework, Methodology, Process, Techniques
  • Event, Meeting
  • Development
  • Done, “Done”, Ready, Shippable, Releasable
  • Self-organising
  • Facilitate, Serve
  • Visible, Open, Transparent, Accessible
  • Titles vs Roles and Multi-disciplinary vs Cross-functional.
  • When is a Sprint Backlog created? And is it considered output of a Sprint Backlog?
  • When does the Sprint Planning take place?

Read the complete post here: https://medium.com/serious-scrum/the-dark-side-of-the-scrum-guide-835b298f8140

Posted on

Three reasons to stop talking about time and deadlines in Agile environments

Timelines and deadlines have always been tricky for software development. With the advent of Agile software development and Scrum, the may feel even trickier. In this post, Ziryan Salayi explores how you can move the conversation from time and deadlines to something that matters: delivering value to your customers faster.

Read the complete article here: https://medium.com/the-liberators/timelines-and-deadlines-how-to-handle-them-in-an-agile-environment-79f5946072ee

Posted on

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?
Posted on

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