 Hello, welcome to the session on Scrum Team roles and responsibilities of Scrum Master and the Product Owner. Let us see the learning outcome. At the end of this session, students will be able to describe Scrum Team roles and responsibilities. The Scrum Team consists of three roles, the Scrum Master, the Product Owner and the Development Team. Even outside the core team does not have any direct influence over the team. Each of these roles in the Scrum Team has a very clear set of responsibilities. Under this section, we will discuss in detail about the Product Owner roles and responsibilities. Another very crucial role that we are going to discuss in this tutorial is the Product Owner. Product Owner is the vice of the customer or stakeholders and hence is responsible for bridging the gap between the development team and the stakeholders. Product Owner manages the gap in such a way which would maximize the value of the product being built. Product Owner is said to be involved throughout the sprint activities and the development efforts and plays a very crucial role in the success of the project. In the success of a product. At the name suggests, a Product Owner should own the product on behalf of the company. The individual is responsible for ensuring that a product creates value for its customers and users as well as the company providing it. You can think of the Product Owner as the person who champions the product, who facilitates the product decision and who has the final say about the product. To fulfill this responsibility, a Product Owner has to connect with the users, collaborate with the development team and understand how the company works. As the Product Owner, you should directly interact with the customers and the users. The development team and other key stakeholders as the picture shows. I have circled the Scrum team, the unit consisting of Product Owner, Scrum Master and the development team in the picture above to indicate that the Product Owner should have close and trustful relationship with other Scrum team members. Scrum views the Product Owner as a part of the wider Scrum team. This makes sense as a great product emerges when the Product Owner takes a market and business knowledge and collaborate with the development team. Let us see the roles and responsibilities of a Product Owner. The first one is bridging the gap. Product Owner works closely with the internal and external stakeholders to gather the inputs and synthesize a vision to place the product features in the product backlog. It is the Product Owner's responsibility to understand the requirements and preference of the stakeholders or customers' community as he is the one who is acting as their representative and shoulders the responsibility of building the right solution. At the same time, Product Owner ensures that the development team understands what needs to be built and when. He collaborates with the team on a daily basis. Product Owner's engagement with the team increases the feedback, frequency and response time when which is as a result boosts the value of product being built. Absence or less collaboration of a Product Owner can lead to a disastrous result and ultimately the Scrum failure. The next role is to manage the product backlog. As an outcome to the above point, the Product Owner is responsible for creating and managing the product backlogs, ordering the items in the product backlog to best achieve the stakeholders' requirement i.e. pre-orderization of product backlog items and finally he should always be available to answer or give the clarification to the development team's query. Overall, he is responsible to groom the product backlog in order to improve the delivered values. Anyone who wants to add or remove the item in the product backlog or needs to change the priority of the item should be directed to the Product Owner. Next roles and responsibility is certifying a product. His another responsibility is to certify the features being built. In this process, he defines the acceptance criteria for each of the product backlog items. The Product Owner might also create the acceptance test representing the acceptance criteria defined by him or might take an assistance from the software management experts or the development team in creating them. Now he is the one who ensures that the acceptance criteria are met by executing the acceptance test. He may choose to execute these acceptance tests on his own or can ask the expert to do so to ensure that the functional and quality aspects are fulfilled and expectations are met. The activity is usually done throughout the sprint as and when the items are completed so that the mistakes could be uncovered and can be fixed before the actual sprint review meeting. The next role is participation as Product Owner is a key participant in the sprint related activities. He works closely with the development team in explaining the items, the scopes and the value it holds. He also acts as an enabler for the development team to be able to pick up the product backlog items that they are supposed to deliver by the end of the sprint. Besides the sprint activities, Product Owner also works on the product releases activity. During the product release activities, the Product Owner engages with the stakeholders to discuss the item of the next release. One of the key success factors for a team to flourish is that the entire team should respect the Product Owner and his decisions. No one other than the Product Owner should tell the team what items to work on. It is recommended to have a single full-time Product Owner for a single product. However, there can be an arrangement where the Product Owner is a part-time role. Product Owner is a person enrolled by the Product Owner himself who can take over all his responsibilities, his absence and support him. Layable and accountable for all the responsibilities that he has been delegated to but the responsibility of work being done eventually still lies with the actual Product Owner. Remember to make the necessary decisions on behalf of actual Product Owner. So in order to succeed, Product Owners require the right skill set. Product Owner is a scrum team member, good communicator, he bridges the gap between stakeholders and the development team and holds the accountability, is available and committed, except the responsibility of a product has business and domain proficiency. Let us pause the video for a while and answer the question. Why can't the scrum master and the Product Owner be the same person? As we discussed in the previous tutorial, the scrum master roles and responsibility. So why can't the scrum master and the Product Owner be the same person? Yes, the answer is Product Owner represents the customer, scrum master represents the team. While a Product Owner is in meeting with the client discussing additional requirements, the scrum master will be facilitating the scrum meetings and helping to remove the impediments. So how could these two scenarios be possible performing by the same person? So the both should be a different scrum master and the Product Owner should be a different. These are the following references I referred. Thank you.