How does Scrum works? (I)

We must organize ourselves first

That is why we need to understand the roles:

Scrum Roles

Core Roles (PIG Roles): Product Owner , Scrum Master, Scrum Team.

Non-Core Roles (chicken roles): the rest of the people.

The restaurant:

There was a hen and a pig, who were friends. One day the hen called the pig and said: "hey dear pig, I just had a great idea, we must found a restaurant, it's an excellent business, I've already seen the site and it will really be a success", the pig replied, "The idea is interesting, and what would be the name of the restaurant", to which the hen replied "well I've been thinking for some time and I think the best name should be Eggs with bacon, also could be called eggs with ham" when the pig heard that name, surprised responded to the hen " Well, I think the business would be partially good, because while I will be committed, you only will participate, so I think in my best interest i will not going ahead with this idea "

PIG Roles

The Product Owner

is responsible for achieving maximum business value for the project.

He responsible for articulating client requirements and maintaining business justification for the project.

The Product Owner represents the voice of the customer (voice of the customer-VOC)

Helps identify Stakeholders (s) for the project.

Facilitates the selection of the Scrum Team.

Facilitates the creation of the Collaboration Plan and the Team Building Plan.

Works with the Scrum Master in the creation of the Prioritized Product Backlog and in the definition of Done Criteria.

And More.

Scrum Master

Is a facilitator ensures that the Scrum Team has an enabling environment to successfully complete the project.

The Scrum Master guides, facilitates and teaches Scrum practices to all involved in the project;

It eliminates the impediments that the equipment finds and it ensures that the Scrum processes are being followed, assist the Scrum Team in creating User Stories and their Acceptance Criteria, Facilitates Scrum Team meetings to estimate and Create User Stories, Facilitates the Scrum Team in creating the Task List for the next Sprint, Assist the Scrum Team in estimating the effort required to complete the tasks agreed for the Sprint, Assist the Scrum Team in the development of the Sprint Backlog and the Sprint Burndown Chart, Supports the Scrum Team in the creation of the Deliverables (Agreed) for the Sprint, Help update the Scrumboard and Impediment Log, Ensures Scrumboard and Impediment Log stay current, Facilitates Prioritized Product Backlog Review Meetings.

And More.

Scrum Team:

The Scrum Team is the group or team of people responsible for understanding the requirements specified by the Product Owner and the creation of the Deliverables.

Mainly the team Estimate user stories approved by the product owner, Assign user stories that are made in a Sprint, Develop the task list based on already agreed user stories and dependencies, Calculate the effort for the identified tasks and, if necessary, update the task list; Develop the sprint pending list (sprint Backlog) and pending work table of the sprint, Create deliverables, Identify risks and execute risk mitigation actions, if any; Update the impediments log and dependencies; Update pending work table, Scrum board, and impediments log, Discuss problems facing Each member and seek solutions to motivate the team, Identify risks, if any, Submit change requests, if required, Participate in review meetings of the prioritized product backlog.

And More.

Chicken Roles

Stakeholders:

Yes, they are very important, however typically they do not have enough time to stay involved in the project permanently and in a constant way.

Therefore, they only participate, through the Product Owner.

Customers:

As stakeholders they are very important, however typically they do not have enough time to remain involved in the project permanently and in a constant manner.

Therefore, they only participate, through the Product Owner.

Vendors:

They have very good ideas, very good products and excellent technology, however, they also have other interests, so they must relate to the project through the Product Owner.

Otherwise, your interests are likely to end up affecting the team's concentration.