Interested in becoming a Certified ScrumMaster? Come to my next workshop!
Welcome to the inaugural cartoon on www.implementingscrum.com.
Since the original publication of this cartoon series (starting September 11, 2006) I have made a few updates to the content of this page.Nothing has materially changed since we started the series; if anything, I hope it adds clarification to the overall content! This story is the first in an ongoing series to help explain what Scrum “is.”
And.
What Scrum “is not.”
Will we get it correct all the time?
Probably not. And that is OK. The plan is for all of us to learn.
Your comments are always welcome.
So, why are we using a Chicken and Pig? The story depicted above, as weird as it is, helps me — and others — explain two of the main types of people in Scrum.
I am amazed that the Human Resource Departments of many companies I consult with have not shut down this example; it is probably only a matter of time. This is still the best example I know of to explain the roles, and this is what our cartoon series reflects.
The basic premise of the Chicken and the Pig can be seen from the cartoon example above.
Here is an easy definition of the Chickens versus Pigs.
A Pig is someone who has skin in the game. Mike Cohn aptly refers to the people in that role as, “Having their Bacon on the line.”
Pig roles are considered core team members. Performers. People who “do” work.
Get it?
I would consider the roles of both Product Owner and the ScrumMaster to be pigs on a team.
A Chicken is someone who has something to gain by the Pigs performing, but in the end, really do not contribute day to day to “getting things done.” Their “eggs” are a renewable resource, and many get laid (eggs that is).
I get asked the following question by many people when starting to use Scrum:
“Can I be a Pig and Chicken at the same time?”
No.
You cannot be a Pig and a Chicken at the same time.
This is something I work with middle managers who struggle with this on a daily basis. The concept takes coaching, and constant [gentle] reminders that they cannot be a Pig/Chicken. I call this a Pigkin… and it is something you do not want to see in any organization!
A video commentary of this cartoon can be viewed here (it was posted February 16, 2008):
Meet the rest of our cast in this series!
We will examine this and other issues in this series, as this is fun to see happen (sometimes sad WHILE it is happening, but funny to imagine).
I do hope the simplicity of the cartoon above gets the point across. Remember it. It will serve us well in the journey ahead.
Please send comments, questions, criticisms, ideas, or whatever here. You can also enter The Scrum Community to discuss this cartoon and other Scrum topics.
Thank you!
Originally Published:
September 11, 2006
Updated:
May 1, 200
October 23, 2007
February 16, 2008 (with Video)
More:
November 29, 2006
11 Comments! to “The Classic Story of the Pig and Chicken”
Leave a Reply
Comment moderation in full effect!
All comments at Implementing Scrum are moderated to help cut back on spam.
This only happens once (more if you are using multiple computers). Once you are in the system, everything is good to go after that.
November 7th, 2007 at 11:23 am
[...] ? ???? ??????? ?? ???????? ? ???????? ?????, ??? ? ?????? ????????? ???? ????????????? ????? ?? ??????? ?????? ????? ?? ?????????? ?? ??????? ??????? ? Scrum ???????. ????????? ???????? ?? ??????? ? ?????????, ????? ??????? ?? ???????? ?????? ??????. ????????? ???????? ?? ??????? ????????? ? ? ???? ?? ???????? ????? ? ???? (???????????? ham’n eggs). ?? ????? ??????? ???????? : “No thanks, I will be commited. But you’d only be involved!” [...]
November 19th, 2007 at 11:12 pm
[...] This week the comic depicts what a lot of Chickens struggle with. [...]
November 26th, 2007 at 8:02 pm
[...] If you are new here… or need a “refresher” on the Chicken and Pig story… go here (http://www.implementingscrum.com/blog/2006/09/11/the-classic-story-of-the-pig-and-chicken/) [...]
November 27th, 2007 at 3:34 pm
[...] [...]
December 12th, 2007 at 2:58 pm
[...] Step one is to break the team into “managers” (chickens) and “workers” (pigs). [...]
March 10th, 2008 at 11:53 pm
[...] [...]
July 3rd, 2008 at 11:11 am
[...] Mehr zur Herkunft des Titels “Chicken” könnt Ihr im Blog “Implementing Scrum” finden… [...]
July 25th, 2008 at 4:54 pm
[...] So in Scrum we talk about a number of terms and roles, the ones I’m talking about today are the Product Owner, chickens and pigs. Chickens and Pigs: If you don’t understand what Chicken and Pigs are within Scrum check out this great cartoon over on Implementing Scrum.com [...]
July 29th, 2008 at 11:40 pm
[...] “Uh, well tell me a story from the user’s perspective. We’ll collaborate on design and further detail the feature during the sprint period. And remember, you’re a pig and that guy over there’s a chicken.” [...]
September 18th, 2008 at 4:55 pm
[...] we struggled with various ways to maintain transparency so that we could satisfy our higher-ups (or the chickens in Scrum parlance) desire to know the status of our sprints and when we would be ready to deploy, [...]
October 31st, 2008 at 2:46 am
[...] First, some overdue credits: the good folks at Berteig Consulting has sent over a list of readings for the CSM course. Most of the information will be based from these materials. The cubic pig and chicken from the title graphic is the fine work of VladZ. As to why the pig and chicken are featured, see here. [...]