Difference between revisions of "Bun owner"

From Pearl Language
Jump to navigation Jump to search
m (Reorder game rules.)
(Background++)
Line 5: Line 5:
|so=Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.
|so=Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.
|wish full=A timely and proper response to the requestor keeps everyone happy.
|wish full=A timely and proper response to the requestor keeps everyone happy.
|background=Game rules:
|background=The Bun protocol (‘Bullprotokollet’ in Swedish) is a lightweight, decentralized request routing protocol. It is designed to be the simplest possible way to handle requests that are shared by a distributed group of people.
#A bun must be eaten, thrown away, or reheated within two days.
 
#*'''Eaten'''—the request is taken care of to the satisfaction of the requestor.
===Metaphor===
#*'''Thrown away'''—the request is rejected and the requestor is notified.
When a bun (= issue or request) comes in, it is warm, juicy, and soft. If it sits around for a day it will get cold. If it sits around several days it will become dry and hard. You can warm up an old bun in the microwave oven as long as it hasn’t become too dry.
#*'''Reheated'''—keep the bun warm by talking to the requestor, e.g. to say that you are searching for someone who can help.
 
#As receiver of a bun you are responsible until it is eaten by you, taken by someone else, or thrown away.
So, a bun should be eaten fairly quickly or thrown away. No use stuffing it in a box. If you can’t eat it yourself, offer it to someone else—before it gets cold, dry and hard!
#The bun is yours until someone else explicitly takes it with your {{p|consent}}—for example, by explicitly saying “I will take the bun.”
 
#*You can find a ''volunteer'' to take it from you—that is, you cannot push a bun onto someone else.
===Examples===
*You get an email, saying, “Hi, we want a TDD course at company X. What will it cost and when can you come?”. Now you have a bun!
*You meet someone at conference who says, “I want to join your company!” Now you have a bun!
 
So, a bun:
*Is born when someone asks you for something and you decide that, “Hey, this is a bun.” Often, buns arrive in your e-mail box and appear when someone calls or approaches you directly. This is the only moment that a bun is ‘pushed’ on you. Still, you decide if something is a bun. You always can {{p|just say no}}.
*Always has an {{p|bun owner}}—the person who received the bun. Or. more specifically, the person responsible for the communication channel through which the bun appeared.
*Must be taken care of it before it gets too dry! That is, a bun is best on the same day, and already loses taste on the second.
 
Therefore, the {{p|bun owner}} implements the bun protocol:
#Within two days a bun must be:
#*'''eaten'''—the request is taken care of to the satisfaction of the requestor;
#*'''discarded'''—the request is rejected and the requestor is notified; or
#*'''reheated'''—keep the bun warm by talking to the requestor, e.g. to say that you are searching for someone who can help.
#A bun has exactly one {{p|bun owner}}, responsible for:
#*its timely procession; or
#*finding a {{p|volunteer}} {{p|bun owner}} who takes the bun over by explicitly saying “I will take the bun.” Note that a bun transfer is always a pull action and never a push action.
#When in doubt:
#When in doubt:
#*Broadcast an email to everybody who might be interested in, affected by or involved in this bun.
#*Broadcast the bun to everybody who might be interested in, affected by, or involved in this bun.
#*Send the bun to the next level up, or to a central person such as CEO or sales lead, based on {{p|risk carrier decides}}. For example if a bun seems to be strategic and might lead to something larger, get in touch with somebody who’s job is to see the big picture.
#*Find a {{p|bun owner}} at the next level up—for example, you manager or the sales lead—if it is a strategic bun, based on {{p|risk carrier decides}}.


It is sometimes tough to succeed in following these rules, especially the 1–2 day age limit. However, really try your best, and at least be aware of when you fail and learn from it.
It is sometimes tough to succeed in following these rules, especially the 1–2 day age limit. However, really try your best, and at least be aware of when you fail and learn from it.
|therefore full=Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.
|therefore full=Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.
|new=Related:
*{{p|just say no}}
*{{p|decision spectrum}}
*{{p|consent}}
}}
}}
==Sources==
==Sources==
*{{web|url=http://blog.crisp.se/2011/01/09/henrikkniberg/1294584120000|site=Crisp|person=Henrik Kniberg|title=The Bun Protocol}}
*{{web|url=http://blog.crisp.se/2011/01/09/henrikkniberg/1294584120000|site=Crisp|person=Henrik Kniberg|title=The Bun Protocol}}

Revision as of 13:39, 23 February 2014

…a distributed squad or tribe who receive a lot of requests for specific services.

✣  ✣  ✣

A timely and proper response to the requestor keeps everyone happy.

The Bun protocol (‘Bullprotokollet’ in Swedish) is a lightweight, decentralized request routing protocol. It is designed to be the simplest possible way to handle requests that are shared by a distributed group of people.

Metaphor

When a bun (= issue or request) comes in, it is warm, juicy, and soft. If it sits around for a day it will get cold. If it sits around several days it will become dry and hard. You can warm up an old bun in the microwave oven as long as it hasn’t become too dry.

So, a bun should be eaten fairly quickly or thrown away. No use stuffing it in a box. If you can’t eat it yourself, offer it to someone else—before it gets cold, dry and hard!

Examples

  • You get an email, saying, “Hi, we want a TDD course at company X. What will it cost and when can you come?”. Now you have a bun!
  • You meet someone at conference who says, “I want to join your company!” Now you have a bun!

So, a bun:

  • Is born when someone asks you for something and you decide that, “Hey, this is a bun.” Often, buns arrive in your e-mail box and appear when someone calls or approaches you directly. This is the only moment that a bun is ‘pushed’ on you. Still, you decide if something is a bun. You always can just say no.
  • Always has an bun owner—the person who received the bun. Or. more specifically, the person responsible for the communication channel through which the bun appeared.
  • Must be taken care of it before it gets too dry! That is, a bun is best on the same day, and already loses taste on the second.

Therefore, the bun owner implements the bun protocol:

  1. Within two days a bun must be:
    • eaten—the request is taken care of to the satisfaction of the requestor;
    • discarded—the request is rejected and the requestor is notified; or
    • reheated—keep the bun warm by talking to the requestor, e.g. to say that you are searching for someone who can help.
  2. A bun has exactly one bun owner, responsible for:
    • its timely procession; or
    • finding a volunteer bun owner who takes the bun over by explicitly saying “I will take the bun.” Note that a bun transfer is always a pull action and never a push action.
  3. When in doubt:
    • Broadcast the bun to everybody who might be interested in, affected by, or involved in this bun.
    • Find a bun owner at the next level up—for example, you manager or the sales lead—if it is a strategic bun, based on risk carrier decides.

It is sometimes tough to succeed in following these rules, especially the 1–2 day age limit. However, really try your best, and at least be aware of when you fail and learn from it.

Therefore:

Secure an owner of the request at all times. Allow others to pull the request with the owners consent. Follow-up within two days.

✣  ✣  ✣

Related:


✣  ✣  ✣

Sources

Retrieved from "http://pearllanguage.org/index.php?title=Bun_owner&oldid=1435"