Not_SAFe

Yes. As the name of the post suggests, we at Practical Agile have chosen not to be involved in SAFe adoptions.

Some may ask: But you are practical Agile and your subtitle is “Agile in your context” isn't this kind of statement in conflict with your own brand? We think not, and this post will try to explain why.

Add a comment

manage_product_backlog

Disclaimer: If you haven't read my “Managing the product backlog for 8 teams“ post - I highly recommend you read it before continuing to read this blog

First thing is first: What the hell were you thinking when you decided that you need 50 teams for your product?! I hope you had a really good reason for it. 9 out of 10 times you have made a bad decision…

 

But here we are, having a product that has 50 teams, which means dealing with ~600 fine grained Product Backlog items at any given moment, i think we can all agree that this is definitely too much for one person to deal with (Disagree with that? Please do not stay silent and comment). So how would we go about and deal with such a big PBL?

Add a comment

Self_Organizing_Birds_Flock

Here's a quick exercise to quickly demonstrate the beauty of self organization. 

All you need is a team of people. Any number between 5-30 people works very well with this exercise.

Purpose: The purpose of this exercise is to highlight the power of self organization, compared to managing people; demonstrate that the most important knowledge is within individuals, and mostly hidden from the eye.

Instructions:

Add a comment

The scrum master has multiple responsibilities. Here are two of them: 

  1. Coach the team, the PO and the organization with scrum.
  2. Facilitate effective ceremonies. 

When you facilitate a great retrospective meeting does it mean you coach the team with scrum? The answer is no. Facilitating and coaching are two different things.

Coaching and facilitating are both widely-used term with various meanings. In this blog post I am focusing on those terms in a work related context. 

Add a comment

Scrum_Master_Superhero

About two weeks ago I published a blogpost on facilitating better daily standups. I called the blog post “Who’s Responsible for the Daily Standup”, and got the following response from Jim Coplien, the person who inspired inventors of Scrum to have the daily standup in the first place:

The ScrumMaster owns the process. The Daily Scrum is part of the process. if the Development Team is not holding the Daily Scrum the ScrumMaster should intervene and challenge the team to do so. Whether or not the ScrumMaster does so, if the team persists in not holding the daily standup, the ScrumMaster should be fired.

— Jim Coplien (by whom the Daily Scrum came into Scrum)

So to help you choose Scrum Masters that should not be fired, here are my ten tips for your next recruit:

Add a comment