I welcome such long overdue discussion, for several reasons.
1) It obviously demonstrates that even the founders feel that modification is necessary, and thus Scrum is imperfect and in need of improvement
2) Moving towards more standard terminology is not only more professional, but allows one to clearly see how Scrum is a modification of, and similar to, traditional management, and not something completely different.
Here are my thoughts on how to refactor the Scrum Lexicon
1) Pig == > Developer/Team Member
Calling someone a pig is extremely unprofessional. In some languages, this is an incredibly hurtful insult. “Pigs” are developers or team members. Let’s call them that. The pedantic joke in the Scrum Guide is no reason to inflict this hurtful misnomer on a professional workforce.
2) Chicken == >Stakeholder
3) Daily Scrum ==> Daily Status, Daily Conversation, Standup Meeting
The fact that the “Daily Scrum” is a “Daily Meeting” cannot be denied. The fact that it is designed to facilitate status updates also cannot be denied. Therefore let us be honest about it. It takes up space, people, and time just like all other meetings. This cost is not zero. Pretending it is some holy part of the process and therefore deserve neologisms to hide that fact is disingenuous. This is a methodology that runs on ad hoc communication and the daily status is part of that. Let’s be honest about it shall we?
4) Scrum Master ==> Team Leader, Team Advocate
There is no more stupid term in the world of IT than “Scrum Master.” Derived from Dungeons and Dragons, and wildly misleading, this term has no use in a professional IT situation. Team Leader or Team Advocate is a much more appropriate title.
5) Sprint ==> Iteration, Phase
Sprint has many negative connotations. One cannot sprint through a marathon. Sustainable pace and sprint are mutually exclusive. Sprint implies a rush to get somewhere good, regardless of cost. This is nonsense. It is a phase or Iteration and should be discussed as such.
6) Backlog ==> Todo list, feature list
There is nothing special about the sprint backlog. It is a todo list, like everyone else has. Let’s be honest about it and call it what it is.
7) Commitment ==> Best effort, Projection
Often one cannot know how long something will take until one undertakes it. Noone should be blamed for this. Best effort or Reasonable Projection should be useful in this case.
I look forward to your thoughts on the matter; feel free to share them!
PS It has come to my attention that this post http://www.scrumology.net/2010/07/05/our-divisive-scrum-terminology-needs-to-be-deprecated/ is similar in nature to my post and my prove interesting reading as well.