1. Scrum Master II: Scaling (EN)

Scrum Master II: Sample Exam von Dion Training

video locked

Über den Vortrag

Der Vortrag „Scrum Master II: Sample Exam“ von Dion Training ist Bestandteil des Kurses „Scrum Master II: Scaling (EN)“.

Quiz zum Vortrag

  1. Transparency
  2. Commitment
  3. Respect
  4. Focus
  1. Commitment, Openness, Respect
  2. Courage, Focus, Adaptability
  3. Transparency, Inspection, Adaptation
  4. Efficiency, Commitment, Courage
  1. A lightweight framework based on empiricism and lean thinking to reduce waste
  2. A theoretical framework that proposes the use of small teams to increase efficiency
  3. An adaptive framework that stipulates the most significant project roles and events
  4. A prescriptive framework for managing large projects involving many stakeholders
  1. Experience is the source of knowledge and that knowledge is used to make decisions.
  2. Making decisions based on incomplete information typically results in poor quality.
  3. Experience and knowledge almost always drive higher quality software and products.
  4. Data and information are transformed into knowledge through analysis and application.
  1. Striving for maximum value of an increment produced during the sprints
  2. Holding each member of the Scrum team accountable as skilled professionals
  3. Inspecting the daily work of the Developers to identify any necessary adaptations
  4. Assisting the members of the Scrum team to be as effective as possible
  1. Adopting new behaviors and ways of relating to one another
  2. Embracing an iterative approach to software development
  3. Following the user story approach for all requirements
  4. Implementing adaptive practices for project management
  1. Individuals and interactions over processes and tools
  2. Contract negotiation over customer collaboration
  3. Comprehensive documentation over working software
  4. Following a plan over responding to change
  1. We ask additional questions and share our own experience as part of the communications.
  2. We give the speaker our full attention and make use of non-verbal communication cues.
  3. We observe behavior cues that help in understanding what is being communicated.
  4. We fully commit to the speaker with the highest level of emotional engagement.
  1. Use active listening and ask questions when clarification is needed to understand the message.
  2. Pay close attention to the speaker in order to understand and absorb the message.
  3. Make notes about the topic so that they can follow up with the speaker later for any clarifications.
  4. Think of ways to relate their own personal experiences to what the speaker is saying.
  1. The Scrum Master should seek advice from the Product Owner in order to counter the resistance.
  2. The Scrum Master should actively share the organization's vision for the Agile and Scrum approach.
  3. The Scrum Master should ask for feedback from those expressing resistance and others to better prepare for the transition.
  4. The Scrum Master should provide support and coaching to all stakeholders in the transition, even those in favor of Agile.
  1. Adopting a new way of thinking
  2. Understanding Scrum artifacts
  3. Knowing the rules for sprints
  4. Recognizing Agile approaches
  1. Is the same as the sprint goal
  2. Planning target for the Scrum team
  3. Is part of the product backlog
  4. Long-term objective for the Scrum team
  1. Serving as a project manager
  2. Guiding the organization
  3. Promoting team ownership
  4. Facilitating Scrum events
  1. Selecting a designated leader for the team
  2. Building high levels of trust and respect
  3. Displaying honesty and humility
  4. Adopting a collaborative style of working
  1. 1, 4
  2. 1, 2
  3. 2, 3
  4. 3, 4
  1. Keeps in mind the overall project and sprint goals at all times.
  2. Conducts all daily Scrum meetings for the team.
  3. Mediates all conflicts between the team members.
  4. Solves all problems encountered by the Developers.
  1. Talk to these employees to determine their current level of Scrum knowledge.
  2. First seek to establish a trust-based relationship with these employees.
  3. Take a facilitator training course to be better prepared for the training.
  4. Ask a current Product Owner to join the session to share some insider tips.
  1. Helps to establish empirical product planning in a complex environment
  2. Documents all epics and user stories on behalf of the customers
  3. Removes barriers between the Scrum team and other stakeholders
  4. Ensures Scrum events take place in a positive, productive manner
  1. 1, 3
  2. 1, 2
  3. 2, 3
  4. 3, 4
  1. Preparing for resistance by identifying approaches for dealing with it
  2. Ensuring all projects are transitioned from the waterfall approach to Scrum
  3. Planning and advising the organization on the implementation of Scrum
  4. Training employees on the concept of self-managing teams
  1. The Scrum Master should facilitate interactions to identify what's working and what isn't.
  2. The Scrum Master should provide templates for different communication methods.
  3. The Scrum Master should recommend communication training for customers and the team.
  4. The Scrum Master should establish policies to govern these communications.
  1. You assist the team in facing the conflicts and coach them on finding appropriate solutions.
  2. You assist in resolving the disagreements and look for additional learning opportunities to offer.
  3. You recognize that the team needs to learn to resolve their own disagreements, so you choose not to intervene.
  4. You recognize that the team needs to learn to resolve their own disagreements so you provide feedback.
  1. Organization
  2. Developers
  3. Customers
  4. Product Owner
  1. 1, 3
  2. 1, 2
  3. 2, 3
  4. 3, 4
  1. Collaborates with all members of the Scrum team to define a sprint goal
  2. Observes interactions between the Scrum team and its customers
  3. Ensures the Developers explain how the product's value could be increased
  4. Proposes how new utility from this sprint will increase the product's value
  1. Refinement
  2. Ordering
  3. Prioritization
  4. Ranking
  1. How will the Developers deliver the next increment?
  2. What new product functionality will be delivered?
  3. Which product backlog items can we complete?
  4. Which user stories have the most business value?
  1. Each Developer selects a card representing the size of the effort and if everyone agrees, this is set as the size.
  2. After discussion, the Scrum Master and Developers select a card from the deck in order to size the backlog item.
  3. After discussing a backlog item, each Developer and the Product Owner play a card to suggest a size.
  4. Once each Developer plays a card, the average of the lowest and highest points determines the size.
  1. Functional, non-functional, and quality requirements are met, and the increment is usable.
  2. The product increment is ready for release to customers after a review by the Product Owner.
  3. Customers can use the product increment following the sprint review session.
  4. The functionality of the product increment is found to be acceptable by the customers.
  1. Prioritize these improvement user stories against other improvements found on the improvement board.
  2. Ask customers for feedback regarding the improvements before deciding which will be implemented.
  3. Determine if any identified improvements can be implemented prior to the start of the next sprint.
  4. Ensure the Product Owner and stakeholders agree that the improvements are appropriate for the team.
  1. Relative sizing of effort using a reference story as a baseline
  2. Sizing of relative effort based on detailed point formulas
  3. Sizing that's based on hours equivalency of story points
  4. Relative hours to complete a set number of story points
  1. As a servant leader to prevent interference, remove impediments, and coach the team on self-management
  2. As a leader to organize and coordinate the work efforts required to create the expected increment
  3. As a manager to assign and oversee all the day-to-day activities of the Developers performing the work
  4. As a liaison between the Developers and other stakeholders when input or feedback is needed
  1. A visual representation of sprint work and its progress
  2. A visual representation of the Developers' velocity
  3. A visual representation of Developers' assignments
  4. A visual representation of impediments encountered
  1. Topic two: user stories to be placed in the sprint backlog
  2. Topic one: the expected value of the selected user stories
  3. Topic three: the assignment of tasks to individual Developers
  4. Topic four: improvements to implement in this sprint
  1. These items will be resized and then returned to the product backlog for reordering.
  2. These items will be returned to the top of the Scrum product backlog for the next sprint.
  3. These items will remain in the sprint backlog for inclusion in the next sprint.
  4. These items will be marked as 'not done' and removed from the product backlog.
  1. Other stakeholders may attend but only to listen
  2. Only the Developers are allowed to attend
  3. Identifies improvements for the next sprint
  4. Detailed discussions occur during the meeting
  1. Helps the Scrum team to maximize responsiveness to feedback from customers
  2. Allows the users to perform acceptance testing for the product increment
  3. Enables the Scrum Master to provide coaching and direction for the next sprint
  4. Ensures the Product Owner discusses impediments removed during the sprint
  1. To identify ways in which the team could increase quality and effectiveness
  2. To assess the outcomes of the sprint in an effort to determine if requirements were met
  3. To review the sprint in an effort to increase the team's velocity in the next sprint
  4. To determine the accuracy of the Developers' sizing of backlog items
  1. Teams work from a single product backlog.
  2. Teams can work from a choice of product backlogs.
  3. Each team selects an epic from the product backlog.
  4. Each team is assigned its own product backlog.

Dozent des Vortrages Scrum Master II: Sample Exam

Dion Training

Dion Training

Jason Dion (DionTraining.com) is a professor and instructor with multiple information technology professional certifications, including Certified Information Systems Security Professional (CISSP), Certified Ethical Hacker (CEH), Certified Network Defense Architect (CNDA), Digital Forensic Examiner (DFE), Digital Media Collector (DMC), CySA+, Security+, Network+, A+, PRINCE2 Practitioner, and ITIL. With decades of project management and networking experience, Jason Dion has been a network engineer, Deputy Director of a Network Operations Center, and an Information Systems Officer for large organizations around the globe.

Kundenrezensionen

(1)
5,0 von 5 Sternen
5 Sterne
5
4 Sterne
0
3 Sterne
0
2 Sterne
0
1  Stern
0

© 2024 Lecturio GmbH. Alle Rechte vorbehalten.

Betreuung durch Dozenten
Auch unterwegs auf Tablet und Smartphone lernen
100% Geld-zurück-Garantie