Hey hey hey. What's good this week awesome people? I hope you had a great week. As for me I had the opportunity to learn the complexity of being a Product Owner from two experts in product development, Kai Stevens and Sjoerd Kranendonk this week.

In an agile context, we use metrics to set performance goals, measure current conditions, define small improvement experiments and measure the effectiveness of the experiments in order to inspect and adapt goals and determine the next steps.

Me ha pasado varias veces cuando una organización me ha llamado para comentarme cómo conectar la estrategia con la entrega.

Given the complexity and urgency of the world's many social, economic and environmental challenges, we need to redefine the meaning of agility.

On today’s episode of YOUR DAILY SCRUM: Planned vs Actual is a TERRIBLE Metric for Scrum Teams!

TL; DR: The Developers Code Fallacy — They Should Talk to Customers, Too, Though There are plenty of failure possibilities with Scrum.

People in organizations are often afraid of running experiments. I have observed that approximately 70% of people responsible and accountable for products are reluctant to validate their assumptions by experimenting. There are several reasons for this hesitancy. The most common is misunderstanding what exactly the Agile experiment means. The second one is the negative result of the experiment. I always answer that this is fine that we have such a result! It means that there is no need to develop a solution that no one wants or does not fulfill users' expectations.

On today’s episode of YOUR DAILY SCRUM: What is the Real Cost of Context Switching for a Scrum Team? Today's question explores the real cost of context switching for a Scrum Team.

How to become a Scrum Master – 5 Simple Steps! So you read the blog about What is a Scrum Master and you’re ready to start your journey! Great job!

“Thanks for the feedback!” “I’ll put it on the backlog.” Or, the dreaded: “Let’s talk about that offline.”

While many misinterpretations and misunderstandings have spread on the “what” and “how” of Agile, it is perhaps the “why” - the purpose of being Agile - that has become most lost.

One of my customers is asking me about the accountabilities of a Product Owner and how they break down.

Fake Scrum is around us everywhere we go. It's unavoidable. Just look on the internet lookup fake Scrum right now and you're going to find all kinds of interesting articles that describe Scrum in very weird ways. There are at least five ways you can tell if you've got fake Scrum going on.

We spend a big part of our workday either participating in or facilitating workshops. In this blog post we will dive into a practice you can use to kick off workshops. A practice to set the tone, to spark impulse, to invite for change and forward momentum: Using videos to kick-start a crucial conversation.

Three Wide-Spread Stakeholder Failures There are plenty of Scrum stakeholder failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.

One of my customers is hiring for the Scrum Master Role and asked if I had a handy-dandy Scrum Master Job Spec that they could use....

This vlog talks about how stake holders can empower the PO.

On today’s episode of YOUR DAILY SCRUM: When does UAT happen in Scrum? Today's question is all about User Acceptance Testing (UAT). UAT is an anti-pattern in Scrum.

Join me and explore the reasons and the consequences of this Sprint anti-pattern in 109 seconds.

Are agile and Scrum the same thing? Learn about the difference from the team at www.FractalSystems.co.uk

Want to be ready for that tough Scrum Master interview? Here are 52 questions from the team at www.FractalSystems.co.uk that will help you really ace the upcoming interview and give you confidence during your Scrum Master interview.

Contrary to popular belief, the Scrum Master success principles are tangible, when we guide the analysis with an outside perspective.

So in this week's vlog we will continue our discussion from last week's vlog and also about a subtle change in Scrum Guide which I think is quite powerful when done right in our organisation.

Does an organization live in the present or in the past? The answer seems obvious: of course in the present! But what if organizations are living in the past? How that night be the case and what can bring the organization back to the present? Let's dive deeper into this questions.

To put it simply, workplace politics centers on differences within employees at the workplace, differences in views and opinions, conflicts on various interests and perspectives, etc. Everything boils down to communications and relations in-between humans.

This vlog with Robert Pieper talks about the importance of Sprint Goals.

In this blog post, Dave West describes professionalism in Scrum and why it is so important in this crazy, ever-changing world.

Join me and explore the reasons and the consequences of this Sprint Retrospective anti-pattern in 83 seconds...

Der 5. Mai 2021 ist der deutsche Erdüberlastungstag, an dem wir in unseren Anteil an ökologischen Ressourcen für dieses Jahr verbraucht haben. Für den Rest des Jahres nehmen wir beim Ökosystem Erde einen Kredit auf.

May 5, 2021 is German Overshoot Day, the day where we have used up our share of ecological resources that our planet can renew this year. We are now living and doing business on a deficit.

Lately, the scope of the Scrum Master has touched the heights, and every other person wants to land their hands on this. No doubt the Scrum Master role is in the spotlight and has also been named one of the top 10 most promising careers.

At a recent Scrum.org Professional Scrum Master II class, I asked the group to write down some learnings from the class that may help other Scrum Masters. One statement that came up has stuck in my mind ever since: “Don’t be a comfortable Scrum Master.” – Unknown Scrum.org Professional Scrum Master II Attendee.

Most people ask me a question: Hey Venkatesh, can you tell me that whether a person can simultaneously handle the responsibilities of a Scrum Master and a Product Owner at the same time?

Agile frameworks such as Scrum have continued to gain traction because of their ability to vastly improve business outcomes and employee engagement. Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

TL; DR: Three Wide-Spread Product Owner Failures There are plenty of Product Owner failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.

The Scrum Master is probably one of the most famous Agile roles. And rightly so, because the Scrum Master pays a pivotal role in helping the team with the efficient and effective use of Scrum. Learn more from the team at www.FractalSystems.co.uk

Después de llevar más de 10 años acompañando a organizaciones, tanto startups como empresas tradicionales, que quieren adoptar la agilidad a su manera de trabajar, hemos visto una gran variedad de enfoques a la hora de abordar la iniciativa y de contextos iniciales.

The readers going through this piece more or less know the definition of a Scrum Master. Co-Creators Ken & Jeff, in their Scrum Guide 2020, having introduced exclusively the framework for Scrum, have put it as: “Scrum Masters are true leaders who serve the Scrum Team and the larger organisation.” The article’s objective is introducing the shift in the mindset or attitude. This is a requisite to become a genuine leader, as far as my experience goes. 

Since this question keeps on coming up and seeing how Product Owner is misunderstood as a new name for business analysts, in this video I elaborate on three things that Product Owners must own to succeed in fulfilling his or her accountability.

The Professional Scrum Master I from Scrum.org is a challenging online assessment where you’ll answer 80 multiple choice questions within an hour.

Scrum Teams do it all the time. It happens in Sprint Review, after Daily Scrum, in Sprint Planning, and as part of development. They discuss the upcoming work to gain a shared understanding...

On today’s episode of YOUR DAILY SCRUM: How Does a Scrum Team Handle Carryover Work? Today's question is all about carryover work. You know, the work that didn't quite get to DONE by the end of the Sprint.

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. Turning the Sprint Review into a Sprint acceptance gate where stakeholders sign off features is unfortunately prominent and defies the idea of self-management.

On today’s episode of YOUR DAILY SCRUM:  Our Scrum Team is late! Should we add more people? Today's question asks whether or not a team running behind should add more people to try to get things completed faster.

Les équipes et organisations qui utilisent le cadre agile Scrum espèrent toutes que les efforts porteront leurs fruits, et qu’elles seront bientôt sorties de tous leurs problèmes grâce à la magie de l’agilité. La première étape consiste généralement à appliquer un cadre de travail avec plus ou moins de rigueur. Mais cette étape est souvent vu comme un objectif à part entière et non un simple premier pas. Nous allons explorer comment sortir d’une application mécanique de Scrum pour progresser vers une utilisation performante de Scrum, en particulier par l'utilisation disciplinée d'une "Definition of Done" stricte.

In their book Agile Retrospectives, Esther Derby and Diana Larsen popularized the idea that a Sprint Retrospect comprises five stages. The second stage refers to gathering data so that the Scrum Team can have data-informed Retrospectives.

Why the distinction between teacher and preacher matters, how you can recognize a Scrum preacher, and what we recommend instead

Las organizaciones que he visitado estaban en un estado de waterfall estructural también conocido como manera de trabajar en cascada rígida. Están lejos de la mejor implementación de Agile.