Skip to main content

Call for Participation: Talks for the Scrum Breakfast

What is the Scrum Breakfast?

The Scrum Breakfast is a monthly exchange of information around Scrum. The breakfast offers discussion, information and hands-on experience to CIO's, executive and operational project managers. The program starts with a short presentation on an interesting topic around Scrum. Then follows a moderated discussion among the participants to encourage an exchange of know-how and experiences.

For 2010, I would like to re-emphasize the experiential & discussion aspects and limit formal presentations to about 30 minutes.

The Scrum Breakfast always needs speakers! Do you have an interesting topic related to Scrum (or Lean or Agile)? If so, please send me a proposal!

Getting People to Come

The secret to a a good turn out  -- a room filled with the right people -- is formulating the announcement so that it grabs peoples attention.

Put yourself in the head of your potential listeners and answer the following questions with complete sentences as your listeners would like to hear it:
  1. What is the Title of the Talk?
  2. Name of the Speaker:
    (Please include a picture to publish with the announcement.)

  3. Who am "I" (your audience), i.e who should come?
  4. What problems or challenges do "I" face?
  5. What do I want to achieve in solving this problem?
  6. How do "I" get from problem to solution? (call to action - this might be phrased as a question or an invitation to come to the event and find out about the solution you are presenting)
  7. What does the speaker do professionally?
If you answer these questions well (in about 100 words, total), the participants will beat a path to our door!

Your talk can be in English or German. Unless the talk is going to be in English, I would rather receive the proposal in German and English. I can polish the English quickly, but actual translation is work ;-)

You should plan the talk for about 30 minutes but expect it to morf into a discussion with the participants before you reach the end.


The Scrum Breakfast takes place the first Wednesday of each month. The doors open at 8am and the talk starts at 8.35 (so people coming by train can arrive at 8.30 and still catch the start of the talk). The presentations & discussion are usually in German.

I founded the event in October, 2008 and since December 2008, it is a monthly event of the Lean Agile Scrum Working Group of the SwissICT. Thanks to the integration into the SwissICT, the interest in the Scrum Breakfast in Zürich has exploded. We accept 30 registrations. There are also Breakfasts now in Bern and Basel.

Want to give a talk? Please drop me a line!


Anonymous said…
just realized you changed your rss fedd from full to headline only. why?

since there are no ads on your blog this does not really make sense to me. why not let readers stay in their rss reader?

i am unsubscribing now... sorry.
Peter said…
Hi Markus,

Sorry to lose you. I waited a bit to answer, because I wanted to see what impact the change had before doing so.

I take it as complement that you do not consider there to be advertising on this site. There is - for my coaching and training services, but I keep it subtle.

My experience with Adsense has been that it makes money for Google, but not for anyone else. So you won't see that kind of advertising on this site.

The big difference is that I see the traffic in my web stats. So I have a better understanding which articles work and which ones don't.

Once again, sorry to lose you. I hope you'll reconsider. And I hope you understand my motivations.


Peter said…
Hi Markus,

After receiving other feedback, I have changed the rss field back to full content.

Hope you see this and rejoin the group!



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…