75% lower incident costs Locate your Scrum Master with your team

So for the scrum master to be a success , they need to not only run the standard ritual and walk through the processes, they need to share time with the team where open unofficial conversations take place, where team members feel free to share concerns that may not be so easy to do formally.  Most scrum masters will quickly start to pickup themes and trends in issues and be ablPicture2e to either address or escalate them before they are are problem. Typically prevention, cost and delay, disruption and management overhead is at least 75% cheaper than cure.  So have your scrum master on site, get them searching and removing issues before they trigger, save that time, remove that wastes effort on fixing preventable issues.

This is a big part of a good Scrum Masters job  I call SMBWA (Scrum Mastering by Walking Around) like GEMBA in Lean or others call it  “go see for yourself”. The difference here is in lean its about looking atthe problem, going in seeing it in SMBWA its about hunting down isses and killing them before they catch fire. An issue once it catches first  severely reduces effectiveness of the team and often  damages the product and the team moral. It better have some one looking for and resolving issues before they get expensive, that’s the role of the scrum master.

This is why the Scrum Master needs to be with the team, to walk the floor as they do there normal role, listing to background conversations, talking to people in coffee areas, taking the temperature. Many problem that can delay or derail project and programs exist in those grey areas for days or even weeks before they ignite and raise to the leadership level.  Yes if they are doing their job well you will save very significant amounts of time and money as the prevent incidents from ever happening and make sure they get resolved quickly.

Today I need Courage- How Committed is your team

courageIn SAFe and Scrum at every PI planning and at every sprint planning I always ask the team about there  commitment to the delivery, I ask them if they are willing to make a promise to the  Sponsors, Product Manager and the Product Owner, and most importantly of all promise to each other that they will do everything within our power to get this done. Its important they think about this decision, one of the many benefits of the fist of 5 (widely used in in SAFe) is a  give them a pause for thought. What the vote, assuming its a free vote will tell you what they really think. Tell you what the probability of success is.

Steve Jobs a Constructive Irritant

I am tired of people worshiping blindly at the alter of Steve Jobs. I am sure he would not see it as a good thing. He was without doubt a benevolent dictator, the truth is that there is as much to learn good and bad.

He was the great visionary, but also the great tyrant. There is no question what he achieved is great, and everyone needs to take a close look at how he worked, how he did things. He may not hamake-them-better-steve-jobs-picture-quoteve been following the philosophy of being a Constructive Irritant but its clear he felt that a degree of conflict , lets say irritation was a healthy thing to have in the work place. We should emulate the good but there is little point if its out of context, thus we must learn the bad also.  Assuming we don’t wish to repeat the mistakes.   Its the good and the bad that shows us the reality.

How Steve Jobs Broke All of Richard Branson’s Rules