Skip to main content

Lean Agile Scrum Conference in Zurich - Open for Registration

Registration is now open for the third annual Lean Agile Scrum Conference in Zurich!

As a community event organized by the SwissICT Special Interest Group "Lean, Agile & Scrum" and supported by our Sponsors, the conference offers an interesting Program of hands on Workshops and Talks to encourage the exchange of information among all members of the community: C-Suite Managers, Project Leaders and Managers, Business Analysts, Developers and Testers.

The Conference begins at 08.30 am with a free entrance event: Keynote Speaker Steve Denning on 'Making the entire organization agile'. The paid admission part of the conference starts at 10.00 Uhr with a choice of 90 minute Tutorials on Scrum in and around the enterprise.

The afternoon starts with a keynote by David J. Anderson, on Kanban, "A Counter-intuitive Approach to Creating a Lean Technology Organization" Eight Sessions (45 Minuten) in four parallel Tracks round out the afternoon. We close the Program with a reception and quality networking time.

BTW - the program is bilingual English/German. The Keynotes are in English and there at least one English-language talk for each time-slot.

We look forward to seeing you in Zurich!
Date  14. September 2011
Time  08.30am to 5:00pm, with a reception afterwards
Location  ETH, Zürich
Registration https://www.swissict.ch/veranstaltungen/anmelden/id=396

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 …