Skip to main content

Scrum Breakfast im February: Agile Governance


Once again, we are fortunate to welcome an international speaker to Zurich for the Scrum Breakfast. Pierre NEIS is a Sr. Management Consultant who is active in the Finance industry in and around Luxembourg. His topic:

Adoption of an Agile Governance Model

As a corporate leader, program or business manager, or line manager, you want your IT and Development activities to be aligned with your business. As more and more companies are doing Scrum, you are thinking about the implications of Scrum on your organization. Scrum promises better business alignment, higher employee productivity and satisfaction, and ultimately better profitability, but seems chaotic and uncontrolled. How do you implement Scrum in your company? How do you keep things under control?

This talk is for corporate leaders contemplating Scrum and anyone who wants to talk to them about the how and why of Scrum in medium and large companies. Pierre E. Neis will discuss the challenges facing companies adopting Scrum and discuss solutions for ensuring business alignment, minimizing overhead of project organization, reducing the risks and costs of IT, and optimizing portfolio management.

Pierre is Director of Consulting at AgilePartner LLC, President of the Agile Interest Group, Member of the PMI as well as co-founder of the Agile User Group in Saar, Germany. The talk will be held in English.

Program


08:00
-
08:35
Registration, Coffee & Gipfeli
08:35
-
09:50
Presentation and Discussion
09:50
-
10:50
Networking, Coffee & informal Discussion
New: Free Coaching! Bring a problem or help with the solution! 3x 20 Minute Sessions in the coaching room.


Time, Location
  • Date: Wednesday, 3 February 2009, 8.00 to 11.00
  • Location: SwissICT, Vulkanstrasse 120, 8048 Zürich (in the same building as the Jeep Dealer. Entry on the left, 2nd floor)
  • Registration should be active in a day or two on the SwissICT Events page
  • Afterward the LAS Core Team will hold its regular meeting - Interested people are invited to attend
P.S. If you attend the Scrum Breakfasts, but are not yet a member, please join the SwissICT. The SwissICT makes the events possible with their support for the room, coffee, gipfeli and organization.

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…

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…

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 …