Difference between revisions of "Agreement-based culture"

From Pearl Language
Jump to navigation Jump to search
m (See agreement for its definition.)
(Sources++)
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
*{{web|url=http://www.infoq.com/interviews/culture-engine|site=InfoQ|person=Steve Peha|title=Agreements-Based Culture}}
*{{web|url=http://www.infoq.com/interviews/culture-engine|site=InfoQ|person=Steve Peha|title=Agreements-Based Culture}}
**so that we can trust each other a little bit more about what’s going to get done and who is going to do it and when it is going to happen
**so that we can trust each other a little bit more about what’s going to get done and who is going to do it and when it is going to happen
**to be more intentional about culture—'''intentional culture''', together with the {{p|agile dojo}} becomes '''instant culture''', or '''instant agile culture''' (or lean if that is your flavor); intentional culture of agreement
**to be more intentional about culture—'''intentional culture''', together with the {{p|agile dojo}} becomes '''instant culture''', or '''instant agile culture''' (or lean if that is your flavor); intentional culture of [[agreement]]
**explicit agreements between team members give a high sense of trust and an easy way to know that get the work will get done
**explicit [[agreement]]s between team members give a high sense of trust and an easy way to know that get the work will get done
**agreements (and thus {{p|explicit policy}} are a natural fabric of our daily work
**[[agreement]]s (and thus {{p|explicit policy}} are a natural fabric of our daily work
**this culture tends do be confrontationally compassionate; confront doesn’t really mean anger or a cause of problem, confront just means meet someone face to face—and a very simple way and say, “Why don’t we do it this way? What do you think?”
**this culture tends do be confrontationally compassionate; confront doesn’t really mean anger or a cause of problem, confront just means meet someone face to face—and a very simple way and say, “Why don’t we do it this way? What do you think?”
**the interactions between individuals that we all care so much about in the Agile community, are really governed by agreements. And the more explicit and the larger number of these agreements, the greater the degree to which we keep them, the more the interactions become more fluid, easier.
**the interactions between individuals that we all care so much about in the Agile community, are really governed by [[agreement]]s. And the more explicit and the larger number of these agreements, the greater the degree to which we keep them, the more the interactions become more fluid, easier.
** know what to expect, you know what to expect and we become a higher functioning team, because we work together in a certain way that we have agreed on ahead of time—no haggling afterwards
** know what to expect, you know what to expect and we become a higher functioning team, because we work together in a certain way that we have [[agreement|agreed]] on ahead of time—no haggling afterwards
**the set of interactions between individuals can be governed by {{p|explicit policy}}—relates to system thinking: system is the product of the '''interactions''' between its subsystems
**the set of interactions between individuals can be governed by {{p|explicit policy}}—relates to system thinking: system is the product of the '''interactions''' between its subsystems
**agreements essentially give a form, a way of knowing what to do; it sets expectations; it's a kind of expectation management
**[[agreement]]s essentially give a form, a way of knowing what to do; it sets expectations; it's a kind of expectation management
**{{p|explicit policy}} shifts the nature of a culture, from one that is accidental, unintentional, drifting in all sorts of different ways, to one that brings us back into interaction, alignment, conversation and collaboration
**{{p|explicit policy}} shifts the nature of a culture, from one that is accidental, unintentional, drifting in all sorts of different ways, to one that brings us back into interaction, alignment, conversation and collaboration
**improve culture by making, keeping, confronting broken agreements and renegotiate and recommit to them
**improve culture by making, keeping, confronting broken [[agreement]]s and renegotiate and recommit to them
**see http://cultureengine.net
|therefore full=Evolve a web of {{p|explicit policy}}.
|therefore full=Set up a web of {{p|explicit policy}}.
}}
 
{{WebSourceListItem
|url=http://cultureengine.net
|site=The Culture Engine
|person=Steve Peha, Amr Elssamadisy
|title=Human-Powered Change for High Performance
}}
{{WebSourceListItem
|url=http://www.infoq.com/interviews/culture-engine
|site=InfoQ
|person=Steve Peha
|title=Agreements-Based Culture
}}
}}

Latest revision as of 10:52, 20 April 2014

…{{{context}}}

✣  ✣  ✣

{{{wish full}}}

See agreement for its definition.

  • InfoQ » Steve Peha » Agreements-Based Culture
    • so that we can trust each other a little bit more about what’s going to get done and who is going to do it and when it is going to happen
    • to be more intentional about culture—intentional culture, together with the agile dojo becomes instant culture, or instant agile culture (or lean if that is your flavor); intentional culture of agreement
    • explicit agreements between team members give a high sense of trust and an easy way to know that get the work will get done
    • agreements (and thus explicit policy are a natural fabric of our daily work
    • this culture tends do be confrontationally compassionate; confront doesn’t really mean anger or a cause of problem, confront just means meet someone face to face—and a very simple way and say, “Why don’t we do it this way? What do you think?”
    • the interactions between individuals that we all care so much about in the Agile community, are really governed by agreements. And the more explicit and the larger number of these agreements, the greater the degree to which we keep them, the more the interactions become more fluid, easier.
    • know what to expect, you know what to expect and we become a higher functioning team, because we work together in a certain way that we have agreed on ahead of time—no haggling afterwards
    • the set of interactions between individuals can be governed by explicit policy—relates to system thinking: system is the product of the interactions between its subsystems
    • agreements essentially give a form, a way of knowing what to do; it sets expectations; it's a kind of expectation management
    • explicit policy shifts the nature of a culture, from one that is accidental, unintentional, drifting in all sorts of different ways, to one that brings us back into interaction, alignment, conversation and collaboration
    • improve culture by making, keeping, confronting broken agreements and renegotiate and recommit to them

Therefore:

Evolve a web of explicit policy.

✣  ✣  ✣



✣  ✣  ✣