Skip to main content

Inspect and Adapt

As another year comes draws to a close, we all start thinking about that annual ritual, the 'New Year's Resolution.' Inspect and Adapt. The core of Scrum is deeply rooted in our culture. And yet, how many of us really implement our Resolutions? We Inspect, but we don't Adapt.

I recently realized that I had been collecting feedback from my course participants for years but I hardly ever really acted on what people wrote. I inspected without adapting. This fall, in the face of lukewarm Net Promoter Scores, I resolved to implement at least one of the suggestions from each round of participant feedback by the next course (see Managing by the Numbers in the 21st Century).

Now, after each course, I go through all the feedback forms, summarize them, and send that summary as a follow-up feedback to the participants. In the summary, I tell the participants what improvement I intend to make in the next course based on their feedback. I always implement one item, and usually several.

Some examples of small changes: 1) including Q&A and case studies as backlog items in the course. I always did case studies and answered questions, but as line items, people knew they were getting them. 2) Ensure that everybody gets a chance to role play a leadership role in the simulations. 3) Answering open questions after the course. (see for instance Questions and Answers from last week's MasterClass Workshop

The biggest change was to restructure the course flow, but I think the small changes have had the most impact on customer satisfaction.

The results were tremendous! Within 3 courses, I was able to raise my Net Promoter Score (the % of participants who would surely recommend me, less the number of those who would probably steer people away from me) from a lukewarm +11% to a delighted +90%! Inspect and adapt really works. Delight the customer really works! And it amazing how quick the turn around can be! (see: Eight Questions for a Product Owner)

My new years resolution - I just have one - to keep inspecting and adapting, based on feedback from my customers.

Imagine -- how would your life or work change if you consequently inspected and adapted. What would next December's year end reflection be like?



Comments

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 …