Difference between revisions of "Reciprocal altruism"

From Pearl Language
Jump to navigation Jump to search
m ({{p|real options}})
m (Typo.)
Line 8: Line 8:
|therefore=Collect the core interests of both parties and turn them into mutually agreed principles or ‘rights’.  Ensure they resonate with each party's values.
|therefore=Collect the core interests of both parties and turn them into mutually agreed principles or ‘rights’.  Ensure they resonate with each party's values.
}}
}}
For instance, in {{p|scrum}}, a {{p|product owner}} and the {{p|development team}} or {{p|vendor}} are on either side of the interface. Based on the {{p|agile manifesto}} and {{p|principles behid the agile manifesto}}, both parties may agree on the following ‘rights’ up front:
For instance, in {{p|scrum}}, a {{p|product owner}} and the {{p|development team}} or {{p|vendor}} are on either side of the interface. Based on the {{p|agile manifesto}} and {{p|principles behid the agile manifesto}}, both parties may agree on the following ‘rights’ up front.
 
As {{p|product owner}}, you want to:
As {{p|product owner}}, you want to:
*Plan on a large scale with investments and {{p|real options}}.  
*Plan on a large scale with investments and {{p|real options}}.  

Revision as of 19:44, 3 September 2012

…two autonomous parties needing each other.

✣  ✣  ✣

{{{wish full}}}


Therefore:

{{{therefore full}}}

✣  ✣  ✣



✣  ✣  ✣

For instance, in scrum, a product owner and the development team or vendor are on either side of the interface. Based on the agile manifesto and principles behid the agile manifesto, both parties may agree on the following ‘rights’ up front.

As product owner, you want to:

  • Plan on a large scale with investments and real options.
  • Change your mind without paying exorbitant costs and set priorities at any time.
  • See progress in the form of a working system at the end of the first iteration, and to see a little more functionality every iteration thereafter.
  • Have updates of the schedule, good or bad, as soon as the information is available.
  • Stop the effort at any time and still own a usable system on par with the investments made up to date.

As a development team, you want to:

  • Always know what needs to be produced with clear requirements, and crystal clear acceptance criteria.
  • Estimate work and have those estimates respected by all stakeholders.
  • Honestly report progress with impunity.
  • Produce high-quality work at all times.
  • Know what is most important to work on next.
  • Ask business-oriented questions whenever they arise, even if they are uncomfortable ones.
  • Facilitate a self-selecting team.
  • Engage in joyful, exciting, challenging an productive work.