Skip to main content

"Why Scrum?" event at the SAQ

Yesterday, Dani Tobler, Gregor Stöckli and I were invited to come to monthly meeting of the Swiss Association for Quality to talk about Scrum.

Usually in a situation like this, there would be one or two people would give a talk with more or less interesting Powerpoint slides. We tried something different. We treated the evening a Scrum Mini Project. We collected requriements (questions) from the audience. A Product Owner prioritized the questions. While the team thought about how to answer the questions, I gave a short talk about how Scrum works. Then the team answered the questions. Then a review of what we'd accomplished (and a retrospective as a feedback form). And finally a
traditional round of Q & A.

Especially considering it was the first time, it went very well. The presentation was only 15 minutes or so, everything else was interactive, which the participants really appreciated. The start was a little bumpy, with a brief dead zone as the team & P-O were discussing what to do. But after that, things started rolling and people really appreciated the 'live demo' and the spontaneity of the discussions. And brownies are always a good idea, especially after 6pm, when people are starting to get hungry.

I have posted the slides online. In particular, the links to the community, and the books and the sources of training are visible in the PDF (which they weren't in the screen presentation).

P.S. If anyone has some pictures, I would love to post one here!

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 …