Difference between revisions of "Bun owner"
Jump to navigation
Jump to search
(Sources += Crisp » Henrik Kniberg » The Bun Protocol) |
(Added decision rules.) |
||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=timely and responsibly handle requests shared by a distributed group of people | |goal=timely and responsibly handle requests shared by a distributed group of people | ||
|context=a distributed {{p|squad}} or {{p|tribe}} who receive a lot of requests for specific services. | |||
|wish=A timely and proper response to the requestor shows respect, manages expectations properly, and secures clear communication. | |||
|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. | |||
|background=Game rules: | |||
#As receiver of a bun you are responsible until it is eaten by you, taken by someone else, or thrown away. | |||
#A bun should not get more than 1-2 days old without being eaten by somebody, thrown away, or reheated (by talking to the customer/sender). | |||
#The bun is yours until someone else explicitly takes it with your {{p|consent}}—for example, by saying “I will ll take the bun”). You can recommend or try to convince someone else to take it from you. This goes both ways—if someone offers you a bun, you don’t have to respond if you aren’t interested. You can’t push a bun onto someone else. | |||
#When in doubt: | |||
#*Broadcast an email 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. | |||
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. | |||
}} | }} | ||
==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 12:17, 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.
Game rules:
- As receiver of a bun you are responsible until it is eaten by you, taken by someone else, or thrown away.
- A bun should not get more than 1-2 days old without being eaten by somebody, thrown away, or reheated (by talking to the customer/sender).
- The bun is yours until someone else explicitly takes it with your consent—for example, by saying “I will ll take the bun”). You can recommend or try to convince someone else to take it from you. This goes both ways—if someone offers you a bun, you don’t have to respond if you aren’t interested. You can’t push a bun onto someone else.
- When in doubt:
- Broadcast an email 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 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.
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.
✣ ✣ ✣
✣ ✣ ✣