Roles

In Scrum, the team of people who are going to be responsible for delivering a solution are sometimes referred to as 'Pigs'. This is perhaps a slightly offensive term but it relates back to a joke about a pig and a chicken walking down a road: The Chicken looks at the pig and says "Hey, why don't we open a restaurant?" The pig looks back at the chicken and says "Good idea, what do you want to call it?" The chicken thinks about it and says "Why don't we call it 'Ham and Eggs'?" "I don't think so" says the pig, "I'd be committed but you'd only be involved"

So we have the Team members, ScrumMaster and the Product Owner who are committed to building software regularly and frequently. Everyone else is interested in the project but really, irrelevant because if it fails they're not a pig, they weren't the ones that committed to doing it. So part of the Scrum process is certainly taking their [chickens] needs, their desires, their ideas and influences into account but not in any way letting it affect or distort or get in the way of the actual Scrum project. The 'chickens' can include stakeholders, users, systems architects and anyone who has an interest in the project and whose interest may get in the way of regular delivery of software.

One of the key features of an Agile approach is the practice of making the users, business and other stakeholders part of the process. It is vital that they are engaged and give their feedback on the output of the team through attendance of Sprint Reviews and testing of Product Increments.