Skip to main content

Questions and Answers from last week's MasterClass Workshop

One of the improvements I made in my Scrum courses and workshops is I commit to answer or address all of the questions which come up. There are always a few questions left over, so I pick them up in my blog.  

After last week's MasterClass, there were a number of unaddressed tickets left on the subject board:
  • How to create interest in Scrum
  • Change management
  • How to address Senior Management and get them on board
  • Team Skills
  • Scrum of Scrums
Let's have a look at the issues, one at a time:

How to create interest in Scrum. A very difficult question to answer briefly. I would seek to create opportunities to learn about Scrum. I would seek to create an interest in improvement. "We are uncovering better ways of ... by doing it and help others to learn to do it." Many of the patterns in Fearless Change are helpful. Sending links to short videos (e.g. TED Talks) and interesting books can be helpful. I have some links in the two blog entries that may be useful. 

Change management. This could mean managing changes to a product or managing change in an organization. The Product Backlog is the instrument for doing the former and the Product Owner is responsible for deciding what changes are made to the product my managing the Product Backlog. I think "change management" to describe organization change in an oxymoron (kind of like "military intelligence" or "beatings in my interest.") I prefer to think of this as how to lead and inspire change. If you tell people what to do or what to change to, you risk provoking a grief response, and most people will fight the change.  I have found the basic storytelling approach of get people's attention, eliciting desire, giving them time and opportunity to digest and ask questions, then following up with facts and proposals to be a very effective approach. I touched on this in my recent PMI Webinar.

How to address Senior Management and get them on board: In my eyes, three books should give you the talking points you need to address Top Management: The Leaders Guide to Radical Management (Denning), Innovators Dilemma(Christensen), Lean Startup (Ries), The Ultimate Question (Reichheld) all address critical topics and should give you the talking points you need to argue convincingly for your Agile cause.

Team Skills. What I call 'Fearless Trust' is the basis for effective teams. Create an environment of Fearless Trust and the rest will be much easier. Dare I say it will take care of itself? No, but see The Five Dysfunctions of a Team, by Lencioni, and this will get you off to a great start!

Scrum of Scrums - Once upon a time, people thought ScrumMasters would coordinate across teams. The approach was called Scrum of Scrums and the meetings were usually held once per week. The ScrumMasters would answer 4 questions:

  1. What did you team accomplish last week? 
  2. What does your team plan to accomplish next week? 
  3. What impediments does your team have? 
  4. What impediments does your team expect to produce this week? 

People quickly discovered that there are many topics which need coordination for which other people are more qualified to address than the ScrumMaster. So today, one talks about Scrum of Scrum of ScrumMasters, SoS of Designers, SoS of DBAs, etc. Check out this case study from Spotify for an interesting insight on how to organize and scale teams to be truly successful.

I think that covers it for the latest MasterClass. I hope I covered everything -- of course I welcome questions and do my best to answer them! And you can look for other Q&A postings to see what came out of other workshops and courses....


Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …