gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update index.md (#32160)

Browse Source 
Addes more details about  pigs and chickens
This commit is contained in:
angel13
2018-12-07 02:31:40 -07:00
committed by Manish Giri
parent 646a17bb96
commit e01505573e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
guide/english/agile/chickens-versus-pigs/index.md
View File

@ -8,14 +8,14 @@ The pig refuses, because while the chicken just needs to lay eggs, the pig has m
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.
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 lower stakes 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.
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:
<!-- Please add any articles you think might be helpful to read before writing the article -->