Have you ever done work around the house or built a new one? Construction is probably one of the best examples of how bad the estimates can go. And it goes hand in hand with the weather forecast. Apparently, we are much better at relative estimation.
Following up on the video “Don’t sweat estimations”, let’s learn how to estimate in story points, unlearn estimations in hours. And play some Planning Poker.
Today I want to write about some problems with overthinking and overdoing estimations. However, I’m not going to talk about what relative estimation is and why we tend not to estimate in hours. That gives for a whole new article and I will probably write it soon.
In my Scrum Master work, I am frequently asked questions like: should the team update the estimates during the Sprint when more is known? What about the stories half done by the end of the Sprint? Should we re-estimate them before adding them to the next Sprint? …
After joining my last company during the pandemic, I learned the power of creating a connection with the team members. I joined three teams as a Scrum Master at a time when everyone worked fully from home. I remember feeling very bizarre on my first day, no Daily Scrums, no meeting the teams, it seemed like the whole company was made up of two people who guided me through the onboarding. I slowly got incorporated into the team events and scheduled some rather random, as I think of it now, one-on-one meetings. Soon I…
I wanted to start this year’s edition of my Agile State of Mind articles and videos with the topic of remote work. Will this be a really remote-friendly year? After 2020 we could assume so. Yet many companies still struggle trying to survive the remote until they can go back to the office. Hence the company policies are not really remote-friendly, we just do what we used to do in the office only remotely.
What’s the biggest pain while working from home? The meetings, of course. Scrum has always been accused of…
The new Scrum Guide landed in November and now what? I decided to make a series of short videos and posts about the key changes and what they mean for us the Scrum practitioners in our daily work.
Talking about daily work, I decided to start with the Daily Scrum. It’s one of my favorite subjects. I can’t help it, I deal with it daily. And I consider it the key event for the team collaboration towards their goal. I want to take a look at it today from a different angle. A Lean angle.
Are you as excited as I am about the new Scrum Guide update?
I hope so!
To give you a preview:
Intriguing, isn’t it?
The release of the new Scrum Guide took place on November 18th, 2020. And at the same time, its creators celebrated 25 years of Scrum. The last update took place three years ago, in 2017.
Today I will walk you through 8 key changes that got my attention.
How to organize discussion during a meeting? And not just any meeting but a remote one! In remote times, we need to get especially organized when it comes to discussions on the video calls. For that, I will explain a popular facilitation technique called “Lean Coffee” and how to use it in the age of remote work.
Recently, two colleagues approached me with issues with the demo part of their Sprint Review. Both work completely remotely due to the pandemic and they identified a similar problem. The teams had so much to show that they could hardly fit it within…
To me, the Daily Scrum along with a Sprint Goal are fundamental Scrum practices. The Daily happens every single day of the Sprint. So we better make it worth our while.
Disclaimer: Scrum and Kanban don’t have to be enemies or frenemies. We don’t have to think about a “Scrum vs Kanban”. It’s time to move on and accept a “Scrum with Kanban” approach. The Kanban Guide for Scrum Teams explains how to do it. I like to enrich the Scrum framework with Kanban principles and practices to help teams optimize the flow of work. Let’s see some practical examples.
Scrum is everywhere. From software development to the space tech industry like SpaceX. It is an Agile framework that provides minimum game rules to organize and deliver complex work in changing conditions.
Scrum is one of the most popular frameworks to organize work followed by thousands of teams all over the world.
Complex work is when more is unknown than known. Unlike a classic assembly line, in software development, we cannot predict the outcome and we don’t have one simple recipe to follow.
That is why waterfall methodologies don’t go so well with software development. Before Scrum and the Manifesto…
What does failure mean?
Does it mean that something did not turn out the way you wanted it to? Is trying and failing a failure? What about not trying at all?
They say that to be innovative you need to actively celebrate risk-taking and failure. Laura Garnett explains in INC “Why failing can be a critical stepping stone to success” and describes the failures of Elon Musk. It is inspiring indeed!
Could it be that every experience, failed or succeeded, is actually a success?