--------------------------DE-TOUR--------------------------
Very little information is found in Scrum about people outside the Scrum Team. This chapter provides some clarity.
--------------------------DE-TOUR--------------------------
Organization and Senior Management
This is not a Scrum role. This is an entity external to the Scrum Team, who sets the larger strategies of organizational change.
• The organization should have guidelines about how to structure the Scrum Development Teams, so it will empower these teams to organize and manage their work.
• If the organization does not yet understand the Scrum concept, it is the responsibility of the Scrum Master to coach the organization as well the Development Teams.
• The organization can expect the Scrum Master to coach the employees about Scrum and empirical product development, plan Scrum implementations, collaborate with other Scrum Masters for organization-wide Scrum adoption, and increase the productivity of Scrum Teams.
• The organization should understand the vital role played by the Product Owner and hence respect their decisions, so that the Product Owner can succeed in their role. The organization should provide the Product Owner with information that will help them increase the value of the product and capabilities.
-------------------Question- 24--------------------------
The support of the organization or senior management
a) Is not needed for Scrum implementations.
b) Is not needed because there is no scope for management in Scrum.
c) Is needed to support the Product Owner to maximize the product value and the Scrum Master to coach and implement Scrum.
-------Answer-------
Correct answer is ‘c.’
-------------------Question- 24--------------------------
Stakeholder
Scrum has a specific meaning for the term ‘stakeholder,’ which refers to people such as customers, users, and all those who have the commonality of having a specific interest and knowledge in a product. The stakeholder is not a Scrum role. However, they influence the product development direction when invited by the Product Owner to participate in the Sprint Review.
Before starting the Sprints, it is highly useful to identify the stakeholders with whom the Scrum Team needs to work. There is no formal artifact to record such information. The stakeholder’s information can be publicly displayed in the workplace of the Team.
• At any point in time, stakeholders have access to the information about the Scrum Team's progress towards a goal.
• During the Sprint Review, they collaborate with the Scrum Team on the next steps.
• They can influence the Product Owner to cancel a Sprint.
• They can approach the Scrum Master to understand Scrum and empirical product development.
How are the external people involved with Scrum Teams?
-------------------Question- 25--------------------------
Who must participate in the Sprint Review?
a) Scrum Team
b) Audit Team
c) Technical and domain experts
d) Stakeholders
-------Answer-------
Apart from the Scrum Team, stakeholders must participate only if they are invited by the Product Owner. Technical and domain experts are not stakeholders. If one of the options is 'invited stakeholders', it is a correct answer and needs to be selected along with 'Scrum Team.' Correct answer is ‘a.’
-------------------Question- 25--------------------------
What can they expect from Scrum Teams?
-------------------Question- 26--------------------------
Select all that apply. Who performs inspections in Scrum events?
a) Product Owner
b) Corporate Audit Group
c) Development Team
d) Senior Management
e) Technical Domain Experts
f) Invited Stakeholders
-------Answer-------
In Scrum, inspections are performed by those doing the work and those who have knowledge of the product. In addition to the Development Team, the Product Owner and invited stakeholders inspect the product Increment during the Sprint Review. Correct answers are ‘a,’ ‘c,’ and ‘f.’
-------------------Question- 26--------------------------
Summary
This chapter is too short to review. Reread, if necessary.
