Skip to main content

Scrum Breakfast: Team Building and the Daily Scrum

Todays Scrum Breakfast set a new record for attendance both on site and on the webinar: 28 registered on site, 19 registered for the webinar and unfortunately some people who wanted to come had to consoled with the webinar, because there just wasn't enough room.

Was it because of the speaker, the interesting topic, or being anchored into the largest IT assocation in Switzerland? Surely a combination of all of the above!

Hans-Peter Korn led us through an interesting discussion about how teams form - under the right circumstances, they do it themselves, but you can't make them do it!

Most provocative was his proposal to modify the 3 questions of the daily Scrum:
  1. What did I finish since yesterday's meeting?
  2. What was particularly helpful?
  3. What will I finish by the next meeting?
  4. What do I need in addition or differently to accomplish that goal?
  5. When was that help available previously?
Question 2 reminds me of an appreciative retrospective and I can see how some daily stroking of the other team members could be a good thing. Question 4 is a much more open and positive formulation of the of the tradtional 'what's is getting the way' (impediment) question. I actually think this might get better answers. If I had to pick just one to try, that would be it.

Thank you Hans-Peter, for an interesting and provocative discussion.

Materials

A short version of the presentation is available for download. More information is available from www.korn.ch. Pictures are available on flickr (Thank you Marcello for finding a camera and taking the pics!)

Next Event - Mark you calendars!

Dana Stoll, former IT Manager at web.de will talk about Agile Methods and  Crisis Management in IT. Wednesday, March 4, 8.00 to 10.00 (with Lean Agile Scrum meeting from 10.30 to 12.00). Mark your calendars - as soon as the event is online at SwissICT, I will publish the announcement.

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 …