Scrum has evolved over the course of 25 years, which is expected. It is a great testament to the meta inspection and adaption that it...

Daily cafes are an engaging and effective way for keeping the team connected and their work synchronized

How many story points should your team be delivering? That's the sort of questions I heard more than enough when helping new teams. I see...

First you need to understand Scrum. Then you need to understand you role as Scrum Master. Here are a few tips on

5 values of Scrum: Courage, Focus, Respect,Commitment and Openness still hold solid and invaluable, they are what help you to stay true to

Introducing a model I have been using to up-skill Scrum Masters with 100% of success, based on mentoring. It elevates the role and is align

a highly interactive mentoring program covering each of the 8 stances through activities that allow the scrum masters to dig deeper

I view a retrospective as a shared event of a team looking back or forward and investigating the deepest causes of success, failure and ever

A postmortem, however, is not a retrospective. Here are some ways in which they greatly differ.

Commonly we use metrics to know how well we are performing. We define a target and we need to check against this target. It is this simple.

Should a Scrum Master hold one-on-ones with team members? I'd say yes! But there are a few hints to make sure this practice stays on the pos

A fun and interesting way to engage parties into taking care of technical debt as early as possible. It is called the Dice of Debt game and

Story points do not talk about how long does it take for a feature to be completed. It does not translate in time. It is not the same for al

Scrum is pretty simple in its essence. So simple that one must pay attention not to get lost on accessory tools that the community built aro