Skip to main content

What would a Teal contract look like?

As I started the Scrum Breakfast Club, I quickly realized that the SBC should be a Teal organization. Two reasons: First, we have an overriding vision to help people transform their worlds through Scrum and related practices, frameworks and mindsets. 2) The SBC should create value for all its participants, i.e. members, chapter hosts and yes, yours truly as founder of the club.

The SBC is at its essence a franchise model. Independent Chapter hosts organize workshops in their regions under the banner of the SBC. But it should be a Teal franchise not an Orange franchise. How is that different?

I discovered one aspect where things must be different: Contracts (or should I call them "Agreements"?) The first thing I created were simple terms and conditions for regular members. Then I needed an agreement between the chapter hosts and the club. Then, as the club grew, I discovered the needs to expand the members agreement.

The most challenging was the Chapter Hosts agreement, because it was very complex and well, money was involved. I used as a model another franchising agreement that I am familiar with. Unfortunately the language of this contract (probably like most contracts) is the language of Orange, which among other things means the language of command and control. This produced quite a dissonance between my goal and purpose of creating a collaborative organization and the language of control present in the contract.

My second iteration on the member terms and conditions went better. I realized the purpose of the T&C was to answer questions about the relationship between the members and the breakfast club. Why not phrase the T&C as and FAQ? So I used that as a format. And I think it produced a much friendlier agreement. (You can see the SBC Terms and Conditions here). Following the advice principle, I published it as a draft on our forum. I received some minor feedback as was able to publish it without further discussion.

We are no rolling out a bit more formalism on the Members Agreement - we now keep better track of when people accept it. One small innovation, if you don't accept the T&C, you can give us direct feedback about why not, with the T&C directly visible on the screen. While one still needs to accept the T&C to get access, we see the agreement as a dialogue.

What are my learnings so far? I believe:
  1. Teal organizations need Tealish agreements
  2. Contract language needs to be reinvented. And FAQ might be a suitable form. 
  3. Participants of Teal organizations need dialogue. With many to one relationships there are some challenges here, but I believe the first step is enabling a bi-directional communication.
What are your experiences with Teal and agreements? 

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…

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…