freeCodeCamp/guide/english/agile/chickens-versus-pigs/index.md

1.6 KiB

title
Chickens Versus Pigs

Chickens Versus Pigs

"Chickens versus Pigs" refers to a story about a chicken and a pig, in which the chicken proposes they open a restaurant called "Ham-n-Eggs." The pig refuses because, while the chicken just needs to lay eggs, the pig has more at stake.

In an Agile software development project, the software developer is the pig. If you fail to complete the job, or fail to do it well, you have a lot at stake. This could be your reputation, or maybe even your position. Other team members might also be considered pigs, depending on how much they have at stake. Pigs work together to complete the job.

On the other hand, many team members are chickens. For example, the client or a high-level project manager would not really be impacted by the failure of the project. They are interested in its success, and might make contributions, but have less at stake and thus have significantly less commitment to the project.

You should strive to be a pig rather than a chicken. You can benefit from (but should not rely on) the chickens in order to minimize risk and guarantee the project is delivered as efficiently as possible. Chickens often provide guidance to assure that right job is being done and that the copmpleted job will provide value.

More Information:

Agile Jedi: The Story of the Chicken and Pig
Wikipedia: The Chicken and the Pig