Several roles are defined in Scrum; these are divided into two groups; pigs and chickens, based on a joke about a pig and a chicken.
A pig and a chicken are 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."
The Product Owner role is responsible for defining and prioritizing the product and release backlog. This includes setting the relative priorities of stories, explaining the intent and acceptance criteria of stories, and determining if the implementation of a story is acceptable. The Product Owner should have a strong voice in quick tactical decisions that need to be made during a sprint such as which stories to drop or add; how to slice a story in order to get it done, or whether or not a customer issue or cross-team dependency should supersede scheduled new development.
There are very few roles required in Scrum: Team, Scrum Master and Product Owner. In this section, we will provide detailed information about what makes an ideal team in Scrum, and define the two new roles (Scrum Master and Product Owner) introduced in Scrum that must be fully understood by organizations. Although people in organizations have actual job titles, these must be left at the door as soon as the Sprint process begins.
We specialize in the placement of agile professionals.
Scrum Masters or Agile Project Managers
Product Owners
Developers (web, mobile, data-warehouse, etc...)
Business Analysts
QA Engineers
User Interface (UI) or User Experience (UX) Designers
We service a targeted list of leading companies as our clientele. Industries we service include healthcare, financial, legal, advertising, publishing, accounting, retail, management, consulting, executive search and technology services.