Chapter 2 Scrum roles
11. Program
A program is a group of related projects, with the objective to deliver business outcomes as defined in the Program Vision Statement. The Prioritized Program Backlog incorporates the Prioritized Product Backlogs for all the projects in the program.
1. Collaboration Plan
Collaboration is an extremely important element in Scrum and the Collaboration Plan outlines how the various decision makers, stakeholders and team members engage and collaborate with each other.
Which of the following is NOT an essential characteristic of a Scrum Team?
Colocated teams
2. Colocation
Colocation is having all Scrum Core Team members located in the same work place leveraging the advantages of better coordination, problem-solving, knowledge sharing, and learning.
3. Core Role(s)
Core Roles are those roles which are mandatorily required for producing the product of the project, are committed to the project, and ultimately are responsible for the success of each Sprint within the project and of the project as a whole.
All the following are part of the Scrum principles EXCEPT:
Defined process control
Prioritized delivery in Scrum means which of the following -
Features that provide maximum business value will be completed first.
4. Forming Stage
Forming Stage is the first stage of team formation, often considered a fun stage because everything is new and the team has not yet encountered any difficulties with the project.
Which of the following is a drawback of small team size?
Impact by the loss of a team member is more.
Empirical process control is a Scrum principle that -
Is employed in situations in which the processes generate unpredictable and unrepeatable outputs.
Which of the following are important selection criteria while choosing a Scrum Master?
Leadership style, problem-solving, availability, commitment
5. Non-core role
Non-core roles are those roles which are not mandatorily required for the Scrum project. They may include team members who are interested in the project, who have no formal role on the project team, may interface with the team, but may not be responsible for the success of the project.
Which of the following is the most effective method of maintaining coordination between multiple Scrum Teams working in parallel?
Scrum of Scrums Meetings.
17. Servant Leader
Servant leaders employ listening, empathy, commitment, and insight while sharing power and authority with team members. Servant leaders are stewards who achieve results by focusing on the needs of the team. This style is the embodiment of the Scrum Master role.
19. Stakeholder(s)
Stakeholder(s) is a collective term that includes customers, users, and sponsor who frequently interface with the Product Owner, Scrum Master and Scrum Team to provide inputs and facilitate creation of the project's product, service, or other results.
A Scrum Team of 8 members has been formed for a project. It has been seen that there is some unpleasantness among team members, and their individual ideas often give rise to conflicts. According to Tuckman's Model of Group Dynamics, the team is in which stage of team development?
Storming
8. Portfolio Product Owner
The Portfolio Product Owner defines the strategic objectives and priorities for the portfolio.
9. Portfolio Scrum Master
The Portfolio Scrum Master solves problems, removes impediments, facilitates, and conducts meetings for the portfolio.
10. Product Owner
The Product Owner is the person responsible for maximizing business value for the project. He or she is responsible for articulating customer requirements and maintaining business justification for the project.
12. Program Product Owner
The Program Product Owner defines the strategic objectives and priorities for the program.
13. Program Scrum Master
The Program Scrum Master solves problems, removes impediments, facilitates, and conducts meetings for the program.
14. Scrum Guidance Body
The Scrum Guidance Body (SGB) is an optional role. It generally consists of a group of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters.
15. Scrum Master
The Scrum Master is one of the Scrum Core Team roles. He or she facilitates creation of the project's deliverables, manages risks, changes, and impediments during the Conduct Daily Standup, Retrospect Sprint, and other Scrum processes.
16. Scrum Team
The Scrum Team is one the Scrum Core Team roles. The Scrum Team works on creating the deliverables of the project and contributes to realizing business value for all stakeholders and the project.
23. Voice of the Customer (VOC)
The Voice of the Customer (VOC) can be referred to as the explicit and implicit requirements of the customer, which must be understood prior to the designing of a product or service. The Product Owner represents the Voice of the Customer.
7. Performing stage
The final stage of team formation when the team becomes its most cohesive and operates at its highest level in terms of performance. The members have evolved into an efficient team of peer professionals who are consistently productive.
20. Storming stage
The second stage of team formation where the team begins trying to accomplish the work. However, power struggles may occur and there is often chaos or confusion among team members.
18. Sponsor
The sponsor is the individual or the organization that provides resources and support for the project. The sponsor is also the stakeholder to whom everyone is accountable in the end.
6. Norming stage
The third stage of team formation when the team begins to mature, sort out their internal differences, and find solutions to work together. It is considered a period of adjustment.
21. User
Users are the individuals or the organization that directly uses the project's product, service, or other results. Like customers, for any organization, there can be both internal and external users. In some cases, customers and users may be the same.
22. Vendor
Vendors include external individuals or organizations that provide products and services that are not within the core competencies of the project organization.