askvity

What is a Chicken in Scrum?

Published in Agile Roles 3 mins read

In the context of agile project management, specifically related to the concepts sometimes used in discussions around Scrum roles, a Chicken refers to someone who is involved in a project but is not responsible for a specific outcome (such as a stakeholder or manager).

Understanding the distinction between "Chickens" and "Pigs" is a metaphor often used to clarify commitment levels within a project, though it's not a formal part of the official Scrum Guide. Based on the provided reference:

  • "Chicken": Involved but not responsible for deliverables.
  • "Pig": Committed and directly responsible for deliverables.

Think of the classic breakfast analogy: the pig is "committed" (sacrificed bacon), while the chicken is merely "involved" (laid an egg).

Roles Often Considered "Chickens"

Based on the definition provided, roles typically falling into the "Chicken" category are those who have an interest in the project's success but are not part of the core team directly building the product. These might include:

  • Stakeholders: Individuals or groups with an interest in the project's outcome, such as customers, end-users, or department heads.
  • Managers: Leaders who oversee the project or the people on the team but are not part of the self-organizing development team.
  • Interested Parties: Anyone else who attends meetings (like Sprint Reviews) to observe progress or provide feedback but doesn't have direct responsibility for creating increments of value.
Role Involvement Level Responsibility for Outcome Typical Interaction
Chicken Involved No Provide feedback, ask questions, observe progress
Pig Committed Yes Build the product, make decisions, responsible for delivery

The Role of Chickens in a Project

Although not directly responsible for the deliverables, Chickens play a vital role in providing context, feedback, and support to the project team. Their involvement ensures the project stays aligned with business goals and meets the needs of various stakeholders.

Key interactions for Chickens might include:

  • Attending Sprint Reviews to inspect the increment and provide feedback.
  • Collaborating with the Product Owner to help refine the Product Backlog.
  • Providing clarity on requirements and business value.
  • Offering insights from other parts of the organization.

It's crucial for project teams to understand the distinction (as defined by the "Chicken and Pig" analogy) to manage expectations regarding roles, responsibilities, and decision-making authority within the project framework. While Chickens offer valuable input, the direct responsibility for building and delivering the product lies with the "Pigs" – typically the Development Team and Product Owner in a Scrum context.

Related Articles