After several posts around the topic of estimation and considering that estimations are often time consuming it is worth it to have a look at the alternative of not estimating at all. Therefore it is useful to become aware of why estimation is done or needed in first place. With that awareness you can asses whether these reason for estimating could be covered without the time invest for estimations. Reasons for estimations Planning right amount of work corresponding to a team’s capacity Decision making based on effort/cost versus value/benefit Prioritization based on estimated effort and uncertainty Cost calculation and budgeting of projects and initiatives Forecasting for customers and stakeholder management Release planning Get an idea on uncertainty or “readiness” of a …

#NoEstimates Read more »

Recently I’ve written a post about The Ball Point Game and about variations of the game, a game that simulates Scrum with all the sprint ceremonies, such as planning, sprint, review and retrospective. This post emphasizes the learning from a Scrum Master perspective.

Recently I’ve written a post about The Ball Point Game, a game that simulates Scrum with all the sprint ceremonies, such as planning, sprint, review and retrospective. Here is an addition to that post which offers interesting variations to the game.

When coaching scrum teams it is alway a good idea to combine theoretical teachings with some exercises that simulate what you’re teaching in a short time. When thinking of which exercises I could use to simulated the methodology, “The Ball Point Game” I’ve done in a training class by Boris Gloger many years ago came to my mind. The game had a prompt impact on me in regards of Scrum. The game simulates all the sprint ceremonies, such as planning, sprint, review and retrospective.

What is the first thing to do when working as a Scrum Master with a new team? Whether the team is experienced in agile software development or not, it is important to create a basis that all future collaboration is build upon. This is the key to avoid misunderstandings based on assumptions or a lack of clarification which will affect all future collaboration and in worst case might damage trust. Therefore I believe a simple session or exercise should be the first step whenever start working with a team: Set expectation and boundaries! This post focuses on expectations as the basis for collaboration as Scrum Master with your team. Make use of your Scrum Master toolbox in order to keep …

The First Thing To Do As Scrum Master With Your Team Read more »