Community Blog

The more ambiguous the requirement, the more difficult it is to calculate how long something will take. But teams still need to estimate their work to forecast releases. Relative sizing provides a realistic method for estimating. Ultimately, your team will find their own value scale and their own language that is meaningful to them. Until then, these Practical Fibonacci tips will help kick-start your relative sizing.

The pandemic has stimulated me to teach Scrum outside my home in the United States. I have been fortunate to collaborate with many diverse cultures worldwide.  I am also grateful to facilitate a team of very talented high-school students in my area. They implemented Scrum to build a real-world mobile application called "The Edge".

First of all, I'd like to note that models and terms I am using and discuss are not mine. They come from training and coaching sessions belonging to Vroemen from Teamchange. The connection I make to Scrum is my interpretation. 

Le Daily Scrum n’est-il pas l’événement où l’on vient vérifier que l’équipe de développement avance comme prévu ?

In this article, we shall investigate why the learning and development of multi-functional specialists in Scrum is the core of organizational Agility and value optimization. Many Development Teams are not collaborating as real teams, but as a collection of narrow specialists focused on "their" tasks (QA, Backend, iOS, Android).

What are the most common mistakes with Scrum that lead to dysfunctional Scrum? This time we take the perspective of the Scrum Development Team.

Technical debt seems like a topic that resides completely in the domain of a Development Team. They are responsible for delivering a potentially releasable Increment after all. But might there be more to it for a Product Owner?