Scrum Quiz How confident are you about your Scrum knowledge? Test your Scrum knowledge here by attempting our questions. Keep Learning! 2 minutes 4 multiple choice questions All unanswered questions will be counted as incorrect answers. Click the "Next" button to skip a question, and click the "Previous" button to return to the previous question. 1 / 10 1. Scrum Guide says: Scrum Team must fulfill (or abandon) one Product Goal before taking on the next. This improves: Openness Respect Courage Focus Collaboration The Product Goal describes a long-term objective or future state of the product. It is a vital part of the Product Backlog, referred to in the Scrum Guide as a commitment. The Scrum Team uses the Product Goal to plan against and maintain focus. Product Goals were added to the 2020 version of the Scrum Guide. The idea of incorporating this concept was to emphasize the importance of having a longer-term goal than a Sprint Goal. Plenty of research on self-managed, goal-oriented teams shares that goals give focus. 2 / 10 2. A traditional project manager can transform into a Scrum Master if: True Leadership attitude can be cultivated. Able to make decisions on behalf of the Developers. Able to estimate the work items in discussion with a Scrum Product Owner. Collaborate by continuing to command and control over team members. “A Scrum Master leads through influence, not authority.” 3 / 10 3. Product Backlog Items (User Stories) can be written by: Scrum Master Developers Product Owner Any of the above Anyone can write user stories. It's the product owner's responsibility to make sure a product backlog of agile user stories exists, but that doesn’t mean that the product owner is the one who writes them. Throughout a good agile project, you should expect to have user stories written by each team member. Also, note that who writes a user story is far less important than who is involved in the discussions of it. 4 / 10 4. Check all the formal opportunities to inspect and adapt. The Sprint Review The Sprint Planning The Daily Scrum The Sprint The Sprint Retrospective Sprints are the Scrum equivalent of an Agile iteration, which is a short period in which a team works to produce an end deliverable. Within each sprint, there are Scrum inspect and adapt events, also known as ceremonies. These events or meetings are specifically designed to enable critical transparency and inspection. There are four Scrum inspect and adapt events: Sprint Planning Daily Scrum (Daily Standup) Sprint Review Sprint Retrospective Scrum events create an empirical behavior amongst teams if done in the right spirit. The Scrum Master should ensure the team understands each event's why what, and how. These events also help to create a flow of communication and provide transparency at every level. 5 / 10 5. ______ are present in the Sprint Backlog and are normally estimated in hours. User cases. Features. Tasks. Stories. The best way for a team to estimate its product backlog items is in story points and its sprint backlog tasks in hours. This works well because story points are a more abstract measure that individuals with different strengths can agree on. Just as you and I can agree on the length of the measure “one foot,” even though our individual feet are most likely different lengths, so can agile team members of different skills agree that this user story will take twice as long to do as that user story. Story points don’t work, though, at the sprint level. During sprint planning, remember the goal is for a team to determine how much work to bring into the sprint. That’s hard with abstract units like story points. It’s far easier with hours. 6 / 10 6. A Scrum Team lives all the Scrum values, and also understands that the values are strongly interlaced with each other and that each cannot be displayed in isolation. While displaying the Scrum values, they build the following that can help them succeed in the longer run: Honesty Unity Integrity Trust Trust is the bedrock of self-organizing agile teams. Trust allows agile teams to communicate quickly and respond rapidly to changes as they emerge. Without sufficient trust, team members can waste effort and energy hoarding information, forming cliques, dodging blame, and covering their tracks. A climate of trust provides the foundation for effective team processes, adaptability, and high performance. 7 / 10 7. Empiricism is NOT: Knowledge to make a decision comes from experience and observation of prior iterations. Decision-making is based on past experience. Evidence-based rather than theory or pure logic. A defined process with a sequence of steps. Empiricism in Scrum is an approach whereby the team continuously learns and improves from mistakes. In Scrum, empiricism means that the team makes decisions and changes based on what the customer is experiencing, rather than what the developers intended them to experience. Additionally, the empiricism meaning in Scrum is the concept that customer feedback directly impacts the team’s actions. 8 / 10 8. Inspect and Adapt is the accountability of: (Select all that apply) Scrum Team Project Manager Developers Scrum Master Product Owner Sprint is a short period in which a team works to produce an end deliverable. Within each sprint, there are Scrum inspect and adapt events. Also known as ceremonies, these meetings are held by the Scrum team to clarify the purpose, progress, and results of a particular sprint. There are four Scrum inspect and adapt events in total: sprint planning, daily Scrum, sprint review, and sprint retrospective. 9 / 10 9. The following are mandatory skills for a Scrum Master: Estimation techniques. Systems thinking. Project management. Technical skills. 10 / 10 10. The 5th event in Scrum is: Sprint. It is a container event. Product Backlog Refinement. Sprint Planning. Sprint Retrospective. These five events are: Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint Your score is LinkedIn Facebook Restart quiz
