Skip to main content

DasScrumTeam is on the starting blocks!

Peter Stevens, Andreas Schliep, Peter Beck
DasScrumTeam

One year ago, Peter Beck, Andreas Schliep and I decided to form a marketing partnership called DasScrumTeam (The Scrum Team).  Our goal was to leverage each others strengths, pool resources when appropriate and share information and experience to guarantee and continually improve the quality of our coaching and courses, and have a common platform for delivering international projects.

It quickly became apparent that DST was a good idea, but we needed to work even more closely together. So this summer, we formed our GmbH in Zurich, got a bank account and VAT number and we are slowly but surely getting ready to start operations. Starting January 1, 2011, we will be doing business as DasScrumTeam GmbH.

What does this mean for you, our customers and partners? On one level, not much. We will continue to offer top quality Training and Coaching in Germany, Switzerland and Austria. Administratively, we have new accounts for payments and a new VAT number, and of course, new email addresses.

Most importantly, we have more depth. A team is stronger than the individual contributors. Our experience complements each other, so we can support your Lean and Agile Transformations at the Management, Team and Engineering levels even better than before.

Got a question? You can check us out at DasScrumTeam.com or drop me a email.


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 …