Certified Scrum Master Class - Practice Test /Pre-class test

Similar documents
Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Certified ScrumMaster (CSM) Content Outline and Learning Objectives January 2012

Scrum. SE Presentation. Anurag Dodeja Spring 2010

Agile Scrum Workshop

D25-2. Agile and Scrum Introduction

Agile Project Management By Mark C. Layton

Sometimes: 16 % Often: 13 % Always: 7 %

PLM - Agile. Design Code Test. Sprints 1, 2, 3, 4.. Define requirements, perform system design, develop and test the system. Updated Project Plan

SCRUM 1. Upon what type of process control is Scrum based? a. Empirical b. Hybrid c. Defined d. Complex

EXIN Agile Scrum Foundation. Sample Exam

Would you like to have a process that unlocks ability to learn and produce faster?

Introduction to Agile and Scrum

Scrum methodology report

Scrum In 10 Slides. Inspect & Adapt

ScrumMaster Certification Workshop: Preparatory Reading

LEAN AGILE POCKET GUIDE

What is Scrum? Scrum Roles. A lean approach to software development. A simple framework. A time-tested process

EXIN Agile Scrum Foundation

AGILE - QUICK GUIDE AGILE - PRIMER

Scrum. Speaker: Dan Mezick URL: NewTechUSA.com. Copyright 2002: All rights reserved

Integrating Scrum with the Process Framework at Yahoo! Europe

T14 "TIMELINES, ARTIFACTS AND OWNERS IN AGILE PROJECTS" Hubert Smits Rally Software Development BIO PRESENTATION 6/21/2007 1:30:00 PM

Agile Systems Engineering: What is it and What Have We Learned?

CSPO Learning Objectives Preamble. Scrum Basics

A Glossary of Scrum / Agile Terms

Adapting Agile Software Development to Regulated Industry. Paul Buckley Section 706 Section Event June 16, 2015

FREE ONLINE EDITION. (non-printable free online version) Brought to you courtesy of Sprint-IT &

References: Hi, License: Feel free to share these questions with anyone, but please do not modify them or remove this message. Enjoy the questions!

The Basics of Scrum An introduction to the framework

ACP Exam Prep Plus Desk Reference including the Project Management Agile Body of Knowledge TM (PMABOK TM )

The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. July Developed and sustained by Ken Schwaber and Jeff Sutherland

Agile Software Development

Agile Information Management Development

Agile Project Management with Scrum

Certified Scrum Master Workshop

Scrum Guidelines. v W W W. S C R U M D E S K. C O M

Agile Development Overview

Using Scrum to Streamline Web Applications Development and Improve Transparency. Michelle Frisque

Agile Team Roles Product Owner & ScrumMaster. Brian Adkins Rick Smith

Agile Metrics. It s Not All That Complicated

Scrum. The Essence. Tobias Mayer, Sonntag, 19. Februar 12

How To Plan An Agile Project

SCRUM. A Tool from the Software World Can Improve Analytical Project Outcomes. By KyMBER WALTMUNSON

The Agile Manifesto is based on 12 principles:

Agile Software Development in the Large

Agile Software Development with Scrum. Jeff Sutherland Gabrielle Benefield

Issues in Internet Design and Development

Waterfall to Agile. DFI Case Study By Nick Van, PMP

Managing a Project Using an Agile Approach and the PMBOK Guide

Getting Agile with Scrum

Scrum Guide. By Ken Schwaber, May, 2009

Course Title: Managing the Agile Product Development Life Cycle

Agile Methods for Analysis

Agile project portfolio manageme nt

Lean QA: The Agile Way. Chris Lawson, Quality Manager

Introduction to Agile Practices

Product Development: From Conception to Execution. Slide 1

Introduction to Agile Scrum

Scaling Scrum. Colin Bird & Rachel Davies Scrum Gathering London conchango

There are 3 main activities during each Scrum sprint: A planning meeting where: the Product Owner prioritizes user stories in the product backlog

Vision created by the team. Initial Business Case created. Cross functional resource meeting held. Agile alignment meeting

SCRUM BODY OF KNOWLEDGE (SBOK Guide)

Scrum includes a social agreement to be empirical as a Team. What do you think an empirical agreement is?

Iteration Planning. also called Iteration Kickoff

Evaluation of agility in software development company

Atern The latest version of the DSDM approach which makes DSDM appropriate to all types of project.

Case Study on Critical Success Factors of Running Scrum *

Agile Project. Management FOR DUMME&* by Mark C. Layton WILEY. John Wiley & Sons, Inc.

February Scrum: Developed and sustained by Ken Schwaber and Jeff Sutherland

AGILE & SCRUM. Revised 9/29/2015

Agile Software Project Management with Scrum

Course Title: Planning and Managing Agile Projects

Agile in Financial Services A Framework in Focus

The Agile Service Management Guide. By Jayne Gordon Groll

Introduction to Agile

Introduction to Scrum

Agile Project Management A Primer. Brian Stewart AVU ACEP Nairobi 17 th 2013

Development phase 1.3. isupport. Project Name: isupport Date: Release: 1.3. Document Name: HCCH isupport Development phase project team 1

TSG Quick Reference Guide to Agile Development & Testing Enabling Successful Business Outcomes

Mariusz Chrapko. Before: Software Quality Engineer/ Agile Coach, Motorola, Poland. My Public Profile:

Roles: Scrum Master & Project Manager

Agile Scrum and PMBOK Compatible or Contrary?

Certified ScrumMaster Workshop

BCS Foundation Certificate in Agile

Certified Scrum Developer (CSD) Course Description

Agile Projects 7. Agile Project Management 21

Agile Practitioner: PMI-ACP and ScrumMaster Aligned

26 May 2010 CQAA Lunch & Learn Paul I. Pazderski (CSM/CSP, OD-CM, CSQA) spcinc13@yahoo.com Cell: AGILE THROUGH SCRUM

Bridging the Gap Between Acceptance Criteria and Definition of Done

Agile Project Management

A Viable Systems Engineering Approach. Presented by: Dick Carlson

Scrum for Managers, Zurich March 2010

Agile with XP and Scrum

Managing Agile Projects in TestTrack GUIDE

SmartBear Software Pragmatic Agile Development (PAD) Conceptual Framework

IMQS TECHNOLOGY AGILE METHODOLOGY

Getting Agile with Scrum. Mike Cohn - background

ScrumMaster or Armchair Psychologist Scrum Fundamentals Webinar Q&A March 9, 2016

When is Agile the Best Project Management Method? Lana Tylka

Scrum and Kanban 101

Transcription:

Name: Your Score: Multiple Choice: For each of the following questions, circle the letter of the answer that best answers the question. 1. Which of the following is NOT an Agile Manifesto Value? A. Individuals and interactions over monitoring and control. B. Working software over comprehensive documentation. C. Customer collaboration over contract negotiations. D. Responding to change over following a plan. 2. Which of the following is an Agile Manifesto Principle? A. Business People and developers must work together daily throughout the project. B. Business People and developers must work together thru the Product Owner. C. Business People and developers must work together frequently throughout the project. D. Business People and developers must work together from early on the project. 3. Which of the following is NOT an Agile Manifesto Principle? A. Welcome changing requirements, early in development. Agile processes harness change for the customer's competitive advantage. B. Working software is the primary measure of progress. C. Simplicity--the art of maximizing the amount of work not done--is essential. D. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 4. Which of the following is NOT typically identified as a Scrum value? A. Trust B. Courage C. Commitment D. Respect 5. The pillars or foundations of Empiricism are? A. Transparency, Inspection, and Adaptation. B. Plan, Do, Check, Act. C. Commitment, Action, Inspection, and Correction. D. Hope, Honesty, and Hard-work.

6. After the third iteration of the project, it is found that the team is behind schedule per the release plan. What should the ScrumMaster do? A. Review task assignments and reconsider or reorganize the team to make the best use of the team with historical data about people and skill set. B. Bring the Executives in for an all-hands meeting with the project team to explain the priority and importance of the project so that the team get energized and motivated to work harder for the common goal. C. Communicate to the team members about the importance of the original schedule and importance of commitment. Be Present in the next Sprint Planning meeting to make sure team is pushed harder but in a healthy way to get more accomplished. D. Communicate to the team. Ask the team how and if this problem can be solved. Help the team in removing impediments. Help the team with administrative work. 7. An agile team is planning the tools they will use for the project. They are debating how they should show what work is in progress. Of the following options, which tool are they most likely to select? A. User story backlog B. Product roadmap C. Task board D. Work breakdown structure 8. In what order the team work on features in a project? A. The order specified by the project management office (PMO) B. The Product Owner and the Team collaboratively order the Product Backlog C. The Team order the Product Backlog D. The order specified by the project architect 9. What does incremental delivery mean? A. Team release working software to the testing group at the end of each sprint. B. Team deliver nonfunctional increments before every iteration retrospectives. C. Team improves and elaborates our agile process with each increment delivered. D. Team deploys functional increments of the product over the course of the project. 10. Which of the following is NOT a Scrum Role? A. Product Manager B. Team C. ScrumMaster D. Product Owner 11. Which of the following is NOT one of the responsibilitis of the ScrumMaster? A. Assigning tasks to team members at the Sprint Planning meeting. B. Helping the Team & Product Owner to follow Scrum values and practices. C. Facilitate the meetings in Scrum. D. Helping the organization learn about Scrum.

12. Which of the following is NOT one of the responsibility of the Product Owner? A. Accepting or Rejecting work product in a Sprint. B. Prioritizing Product Backlog items. C. Maximizing the business value. D. Making sure that the team and organization understand the Scrum framework. 13. Which of the following is NOT one of the characteristics of the Team? A. The Team in Scrum is Self Organizing. B. The Team selects how much work they can do in a Sprint. C. The Team tracks progress of the work in a Sprint. D. The Team prioritizes Product Backlog items in a Product Backlog. 14. The ideal size of the Team in Scrum is A. In Scrum, Team size does not matter. B. 5 to 9 people. C. No more than 100. D. 10 to 20 people. 15. Who is responsible for helping team and organization learn Scrum? A. Agile Coach or Scrum Coach. B. ScrumMaster. C. Scrum Manager ( previously known as Project Manager) D. The Team. 16. Who makes plans for Sprint including creating Tasks in a Sprint backlog? A. ScrumMaster. B. Product Owner. C. Technical team lead & Test team lead D. The Team. 17. The Sprint Backlog is A. Similar to the WBS ( Work breakdown structure) and is a list of tasks that the Project Manager creates to accomplish the Spring Goal. B. The list of tasks that the team created at the Sprint planning meeting in order to deliver the selected Product backlog items in the sprint according to the definition of done. C. The list of items that the team will not be able to complete during the sprint because of time and/ or resource constraints. D. A list of tasks that the Scrum Master created at the sprint planning meeting. The ScrumMaster reviews the list with the team but will be managed by only the Scrum Master. It is used to monitor and control the work defined in the Sprint. 18. How is the Role Project Manager defined in Scrum? A. ScrumMaster and Product Owner report to the Project Manager. B. The Project Manager manages the team, assigns work to the team, and oversees the team. C. There is no Project Manager defined in Scrum. D. Reports to the Product Owner and is responsible for managing the stakeholders.

19. What is expected at the end of the Sprint Planning meeting? A. A Sprint Goal & a Sprint Backlog enough for team to make plans for the sprint. B. Sprint backlog with Tasks and resource assignments. C. Sprint backlog with tasks & dependencies. D. Updated Project plan on Microsoft Project or similar tools. 20. Which output from a Sprint Planning Meeting provides the Development Team with a target and overarching direction for the Sprint? A. The sprint goal B. The release plan C. The sprint backlog D. The sprint task list 21. Which of the following may be used as a tool to assess the progress of a Sprint by an Agile team A. A task board B. WBS on MS Project C. User Stories in Product backlog D. Release plan 22. The Primary purpose of a Sprint Burn-down chart is A. To help see the amount of work remaining in a Sprint. B. To help see the amount of work completed in a sprint. C. To help the product owner to see if the team will meet the release date. D. To help the functional manager to assess the performance of a team member. 23. Which of the following is NOT a ceremony in Scrum? A. Sprint Planning meeting. B. The Daily Scrum meeting. C. The Sprint Test planning meeting. D. The Sprint Retrospective meeting. 24. Which of the following is NOT True about Sprint? A. The length of a Sprint 30 days or less. B. The length of the Sprint changes from Sprint to Sprint to accommodate large user stories. C. The team delivers Potentially shippable product increment in every sprint. D. Sprint is a fixed period of time. 25. Which of the following is NOT True about Sprint Planning meeting? A. Every Sprint Starts with a Sprint Planning meeting. B. The Product Owner, Scrum Master, and Technical and test leads attend the Sprint Planning meeting not all the team members. C. During the Sprint Planning meeting, the team and the team alone determine how much work the team can do in a Sprint. D. Sprint Planning meeting is time boxed meeting.

26. Which of the following is NOT True about Sprint Planning meeting? A. Sprint Planning meeting has two parts; first for the team to work with the Product Owner to determine what needs to get done and second for the team to determine how to get the work done. B. In the first part of the meeting, the Product Owner presents ordered Product Backlog items to the Development Team, and the whole Scrum Team collaborates to understand the work. C. In the second part of the meeting, the team does sufficient design and planning to be confident of completing the work during the Sprint. D. In the second part of the meeting, the ScrumMaster make sure that every task is assigned to the right team member in the team. 27. Which of the following is NOT True about how much work get done in a Sprint? A. It is solely up-to the team to decide how much work is undertaken in a Sprint. B. It is upto the Product Owner and the Release team to decide how much work is undertaken in a sprint to be in line with the Release plan and the contractual agreements. C. The team considers the current state of the Product Increment, the past performance of the team, the team's current capacity, and the ordered Product Backlog in order to determine how much work the team can undertake in a sprint. D. The Team alone decides how much work to take on in a Sprint. Neither the Product Owner, nor any other agency, can push more work onto the Team. 28. Which of the following IS True about Daily Scrum Meeting? A. The daily Scrum Meeting is a status meeting for Scrum Master and Product Owner but not for any other stakeholders who are not involved in a day to day basis. B. The daily Scrum meeting is a communication and coordination meeting for the Team. C. The daily Scrum meeting is a Problem solving meeting for the team to discuss and resolve issues every day so problems do not stay unresolved for longer period of time. D. The daily Scrum meeting is a status meeting for the Scrum Master not anyone else including the Product Owner. 29. How does the team decide when a Product Backlog item is done? A. When the tester has signed off the product increment after testing in the agreed up on environment. B. When the Sprint timebox has ended. C. When the product increment meets the current definition of done. D. When the Scrum Master decides that the Product Backlog items are done. 30. Scrum is... (select the best answer from the list) A. A methodology with many rules, roles, and many defined best practices. B. A software development approach sometime correctly referred to as cowboy process where programmers create products without involving the customers because customers do not know what they want anyway. C. WA process control framework where the work is planned from start to finish in detail at the beginning of the project. D. A simple process framework for developing products with only a few roles, a few artifacts, and few defined ceremonies. It is an empirical process control approach that is based on Agile Values.

31. A Product backlog is... (select the best answer from the list) A. A prioritized list of functional and non-functional business needs. The Product Owner is responsible for creating and managing this list. B. A list of detailed functional and non-functional requirements. The Product Owner is responsible for creating and managing this list. C. A list of detailed functional and non-functional requirements that the team has determined that it will not complete in the sprint / project because of schedule and budget constraints. D. A prioritized list of tasks to realize the business / product needs. The Technical team is responsible for creating and managing this list. 32. The Sprint Review is A. A meeting at the end of every sprint where the team reviews the past Sprint for lessons learned during the sprint. B. A meeting at the end of every sprint where the team demonstrates the product increment that they created in-order-to get feedback from the stakeholders. Anyone interested in the product is invited to the meeting. C. A meeting at the end of every sprint that will act as a phase gate where the team working with the product owner to come up with a list of product backlog items that are ready for the testing phase. D. A meeting at the end of every sprint where the Project Manager reviews the progress of the product development with the stakeholders. 33. The Sprint Retrospective meeting is A. A meeting at the end of every sprint where the team reviews individual performance with metrics such as defects per person per user story in-order to improve team performance. B. A meeting at the end of every sprint where the team demonstrates the product increment that they created in-order-to get feedback from the stakeholders. Anyone interested in the product is invited to the meeting. C. A meeting that follows the Sprint Review meeting where the team reflects on the Sprint to improve their process. D. A meeting that follows the Sprint review meeting where the Project Manager or their delegate collects the lessons learned so that it can be documented in the process audit documentation. 34. Who has the authority to cancel a Sprint? A. It is a collaborative decision but the authority rests upon Product Owner. B. It is a collaborative decision but the authority rests upon ScrumMaster. C. It is a collaborative decision but the authority rests upon Project Manager. D. A Sprint is never cancelled for any reason. It is against the Scrum Value Commitment. 35. The definition of Done in Scrum is? A. A checklist of criterion conforming to the organization s standards, conventions and guidelines that is mutually agreed between the Team and Product Owner. For a product backlog items to be considered done, it needs to meet this criteria. A. A checklist defined by the Program management Office. B. It can change during the sprint. C. The test team s definition of when the product increment is considered done. D. The test scenarios that needs to pass upon which the Product increment is considered done and ready for production migration.