The fable of the Chicken and the Pig is used to illustrate the differing levels of project stakeholders involved in a project. The basic fable runs：
A Pig and a Chicken are walking down the road.
The Chicken says: “Hey Pig, I was thinking we should open a restaurant!”
Pig replies: “Hm, maybe, what would we call it?”
The Chicken responds: “How about ‘ham-n-eggs’?”
The Pig thinks for a moment and says: “No thanks. I’d be committed, but you’d only be involved.”
Sometimes, the story is presented as a riddle:
Question: In a bacon-and-egg breakfast, what’s the difference between the Chicken and the Pig?
Answer: The Chicken is involved, but the Pig is committed!
Recently，The CEO has hired a external expert to improve products and project development process。 Not long before,the PMs has feedback to me that the expert too aggressive,the PO have almost no effect on the product, Experts say going south, PO dare not go north. And always evaluate the R & D team’s estimated time of mission completely. the expert often said : your products is too rubbish,your project plans are rubbish.
After a while ,the expert left, leaving a group confused people and the rubbish producted by expert.Maybe，it will be a real story…
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. This analogy is based upon the pig being able to provide bacon (a sacrificial offering, for which the pig must die in order to provide) versus a chicken which provides eggs (non-sacrificial).
For a Scrum project the Development Team, Product Owners & Scrum Masters are considered as people who are committed to the project while stakeholders, customers and executive management are considered as involved but not committed to the project.
As of 2011, the fable has been removed from the official Scrum process.