Skip to main content

Scrum Breakfast in Bern and Basel

Thanks to the effort and motivation of Mark Hediger, Joscha Jenni und Ralph Jocham and the support of their respective companies (Actionize, Mimacom and Zühlke), there are monthly meetups for the Scrum Communities in Bern and Basel. It is my honor to kick off the events with a talk, appropriately about getting started with Scrum.

Change Process: How do I bring Scrum (or any other idea) into my company? By Peter Stevens

As a developer, tester, project manager or manager, you are intrigued by Scrum. But you are having difficulties gaining support for your ideas. You would like to convince your management and colleagues, that you company or department should use Scrum, or at least should give it a try. How can you motivate or even mobilize your colleagues, so that the support your ideas?

Based on experiences in my own projects, we will discuss a number of possible approaches, which are helpful in bringing about change. An Introduction in Change-Processes and how to guide them effectively.

These talks will be given in German!




BernBasel
Wo:Zühlke Engineering AG
Aarbergergasse 29
3011 Bern
Lageplan
Newground AG im Unternehmen Mitte
Gerbergasse 30
4001 Basel
Lageplan
Wann:26. August 200916. September 2009
Info und Anmeldung:per Email an ZühlkeSwissICT
Programm:08.00 bis 08.35 -- Kaffee und Anmeldung
08.35 bis ca. 09.50 -- Vortrag und Diskussion
10.00 bis ca. 11.00 -- Networking und mehr Diskussion
A great Dankeschön an Zühlke und Actionize for sponsoring the Venue, Coffee and Gipfeli! I wish Ralph, Joscha and Mark the best of luck with new Scrum Breakfasts and hope that every Scrumist and Agilist will take the opportunity to meet and share interests with others from the same region at these breakfasts!

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 …