Scrum is simple, as you must already know, but each aspect of Scrum application could be dissected into small but essential pieces, without understanding of which you can’t progress in your Scrum journey. Therefore, I decided to inspect a bit deeper some specifics of Scrum routines in article series ‘Granular Scrum’. This is a first one.
So, my friend, you got your electronic Scrum board as everyone around you, but somehow just having it doesn’t help much. …
I've seen many teams, which are doing their retro by the book. Or by the Scrum guide. Or as they have been told at Scrum Master training. Year after year there are the same three questions:
These are good questions when a team start with the retro, but after some level of maturity, I think, people in the team should look a bit beyond. May be there should be the questions like:
Today topic is about some technical debt your product might have. One of the most frequent responses I got, when suggesting to eliminate the tech debt, was:
But we are fine, we’re doing like this for couple of years already!
In other words, it is more comforting for all involved parties to accept technical debt like we accept some bad weather than fight it like we fight some clutter on a workplace. …
Things to look after before you start scaling:
Conference is fun, but!
Although a conference definitely should be a lot of fun, on the other hand it requires plenty of effort from every attendee, so I’d like to share my vision what kind of effort that could be.
First, going to a conference, please, keep in mind that it’s a place where exchange of ideas is happening. And you need to be prepared to get these ideas; hence often ideas need a soil to grow from a small seed into something useful. …
I am always wondering how Scrum Masters are evaluating their success or a failure. How they are attributing a success of their team — as their own success on mentoring and coaching the team, or as a victory of all allied forces starting from fancy pants in Product Department and ending at some DevOps guy fingertips?
I found for myself three Scrum Master success indicators: happy team, happy customers (and the Product Owner as their representative) and a working , nicely crafted software. Exclude one, and the problems will follow: