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

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…