I was browsing through Wikipedia and stumbled into this….
The Chicken and the Pig
The fable of The Chicken and the Pig is about commitment to a project or cause.
There are several variants as to how the Chicken and the Pig meet and the level of the relationship between the two.
However, in every variant, the Chicken suggests that the two involve themselves in a scheme involving ham (or bacon) and eggs (some suggest a breakfast, others suggest a restaurant). In reply, the Pig always notes that, for the Chicken, only a contribution is required (as a chicken can simply lay an egg and then resume normal activities), while for the Pig a “total commitment” (or total sacrifice) is needed (as in order to make ham or bacon, the pig must be slaughtered).
Interpretation and lessons
This fable is commonly referenced in the Agile software development community to illustrate two types of project members: pigs, who are totally committed to the project and accountable for its outcome, and chickens, who consult on the project and are informed of its progress. By extension, a rooster can be defined as a person who struts around offering uninformed, unhelpful opinions.
A successful project needs both chickens and pigs (roosters are seen as unproductive). However, given the sacrifice required of being a pig — forswearing other projects and opportunities – they can be difficult to collect. Thus, the construction of a successful project-team must ensure that the project has sufficient “pigs” – and ensure that they are empowered to drive the project in return for committing to and taking accountability for it.