Scrummaster Course Preparation Test

Question. 10/34 Scrum does not have a role called "project manager."

• True

• False

Question. 24/34 The time-box for the Sprint Planning Meeting is?

• 2 times 4 hours for a 4-week Sprint, proportionately(tỷ lệ tương ứng) less for shorter Sprints

• At the end of every Sprint

• 15 minutes

• How ever long is needed

Question. 17/34 Who has the last say on the priority of the Product Backlog?

• The Stakeholders

• The Team

• The ScrumMaster

• The Product Owner

• The Business Owner

• The CEO

Question. 26/34 What does the Team attempt (nỗ lực) to develop every Sprint?

• A potentially-shippable product increment

• A sellable product

• Failing unit tests, to identify acceptance tests for the next Sprint

• Compilable source code ready to be handed off to QA for testing

Question. 30/34 What is the time-box for the Daily Scrum (standup) meeting?

• 5 minutes

• 15 minutes

• 30 minutes

• As long as necessary

• Till people are tired standing

• One day, why else would it be called daily?

Question. 6/34 How is the Product Backlog arranged?

• Large items at the top to small items at the bottom

• Safer items at the top to riskier items at the bottom

• Most important items from customer perspective (quan điểm/góc nhìn) at the top to least important items at the bottom

• Items are randomly arranged

• Into categories P1, P2, P3, etc

Question. 7/34 Which of the following is the Team not responsible for?

• Planning how to meet a Sprint goal

• Monitoring and optimizing(tối ưu) the work to meet the Sprint goal at least daily

• Monitoring and increasing productivity and learning

• Removing impediments (trở ngại)

• Selecting the Product Owner

• Resolving internal conflicts (xung đột).

Question. 3/34How often should the Backlog Refinement Meeting (a.k.a. "Backlog Grooming" ) occur?

• Every Sprint

• Every release cycle

• Once, at the beginning of the project

• Once, at the end of the project

Question. 16/34 When multiple Teams are working on one product, they should make sure each team has different Sprint start dates

• True

• False

Question. 23/34 The team has negotiated clear Sprint goals with the Product Owner. Who determines (xác định) how the team will accomplish (hoàn thành/thực hiện) the goals?

• The Team

• The ScrumMaster

• The Product Owner

• The software architecture department

• The team lead appointed by the ScrumMaster

Question. 8/34 Who creates a Product Backlog Item's effort estimate?

• The Product Owner with input from the Team

• The Team after clarifying (làm rõ) the requirement

• The ScrumMaster

• The most senior people in the organization, including architects and subject matter experts

Question. 14/34 When should a Retrospective (cải tiến, rút kinh nghiệm) be held?

• Only at the end of a release

• At the end of each Sprint, before the Sprint Review Meeting

• At the end of each Sprint, after the Sprint Review Meeting

• Only at the end of a project

• Every now and then when the Team wants to improve

Question. 27/34 When many Teams are working on the same product, should all of their increments be integrated every Sprint?

• No, that is far too hard

• No, each Scrum team stands alone

• Yes, otherwise Product Owner may not be able to inspect what is done accurately

Question. 31/34 During a Sprint Retrospective, for what is the ScrumMaster responsible?

• Acting as a scribe (người ghi chép) to capture the team's entire discussion

• Facilitating so that the Retrospective is useful and done efficiently

• Summarizing and reporting the discussions to management

• Tell the Team what improvements they should do

Question. 32/34 Most organizations claiming (phản ánh, phàn nàn) to do Scrum

• Are doing it as well as possible

• Have changed Scrum which lead to a sub-optimal results or even worst development than before

Question. 28/34 When multiple Teams are working together on one product, each team should maintain a separate Product Backlog

• True

• False

Question. 4/34 Who owns Sprint commitments?

• Individuals, as determined during the Sprint Planning Meeting

• The team owns them collectively

• The ScrumMaster

• Individuals, as assigned by the ScrumMaster

Question. 13/34 In the Sprint Planning Meeting, a mature (trưởng thành), experienced Team engaged in complex work commits Product Backlog Items to one Sprint. The quantity of work it commits to each Sprint should be primarily based on?

• Collective opinion of the Team using whatever information they need

• Available team hours minus task hours

• (available team hours x load factor) - task hours

• (available team hours x (load factor + contingency (dự phòng)factor)) - task hours

Question. 20/34 Which technique is the least productive way for the ScrumMaster to ensure the team communicates effectively with the Product Owner?

• Listen to their communications

• Act as a go-between for them

• Teach the team to talk in terms of business needs and objectives

• Teach the Product Owner about technologies employed during the Sprints

Question. 15/34 When should the Product Backlog be re-prioritized?

• Always. The Product Owner should re-prioritize the Product Backlog constantly, as we learn more

• Sometimes. The Product Owner should re-prioritize only before the elaboration (xây dựng)stage gate

• Never. The Product Backlog should be locked down before Sprinting begins

Question. 22/34 When developing a software product, how frequently do experienced Agile (nhanh nhẹn, linh hoạt) developers test?

• Every Sprint

• Once per week

• Once per day/night

• Every time the code changes (potentially many times per day)

• As soon as the QA person is available

Question. 1/34 Which statement best describes Scrum?

• A complete methodology (phương pháp) that defines how to develop software

• A cookbook that defines best practices for software development

• A framework with built-in reality checks, within which complex products are developed

• A defined and predictive process that conforms to the principles of Scientific Management

Question. 12/34 Scrum distinguishes (phân biệt/nhận ra/khác biệt) Product Backlog Items from tasks

• True

• False

• Sometimes

Question. 25/34 During Sprint Execution, when are new tasks added to the Sprint Backlog?

• As soon as possible after they are identified (được nhìn thấy, xác nhận), assuming they don't reflect a scope change in the Sprint goals or committed Product Backlog Items

• When the Product Owner identifies a new task

• When the ScrumMaster identifies a new task

• When the ScrumMaster approves them

• Never. The Sprint Backlog is fixed and decided during Sprint Planning

Question. 19/34 Does Scrum have rules, or just guidelines?

• Scrum has a few rules. Appendix A in the "Agile Project Management With Scrum"-book by Ken Schwaber is called "Rules."

• Scrum has guidelines, not rules

Question. 29/34 What is the most common length of a sprint?

• As long as it takes to finish the requirements

• Exactly 4 weeks

• Exactly 2 weeks

• Exactly 6 weeks

• Exactly 1 week

• 2 weeks, might be a little longer to finish the work

Question. 21/34 In a Scrum organization, which is a responsibility of management external to the Scrum Team?

• Monitor the Sprint Burndown Chart to ensure individuals are contributing (đóng góp)

• Help resolve Team-reported impediments and improve the organization

• Organize performance appraisals

• Coordinate activities between Scrum teams

• Monitor the Daily Scrum meetings and reward team players

Question. 18/34 When is the Sprint Backlog created?

• Prior to the Sprint Planning Meeting

• During the Sprint Planning Meeting Part Two

• During the Sprint.

• During the Sprint Planning Meeting Part One

• At the beginning of the project

Question. 9/34 Which skills are typically needed on a Team?

• Coding

• Testing

• Software architecture/design

• Business/requirements analysis

• User-interface design, user experience, information architecture, etc

• Technical writing

• Database

Question. 5/34 What is a Team expected to do during the first Sprint? (Choose two.)

• Build a thin slice of potentially-shippable (có khả năng chuyển giao) functionality

• Nail down the architecture

• Develop a detailed plan for the rest of the project

• Test the product

Question. 11/34 What should happen at the Sprint Review Meeting? (Choose two.)

• Live demonstration (thuyết minh, trình bày) of a potentially-shippable (properly tested) product increment

• Feedback from stakeholders resulting in additional items added to the product backlog

• A report about what happened during the Sprint

• A PowerPoint presentation about hypothetical (giả thuyết) things

• Applause (tán thưởng)

Question. 33/34 Which of the following statements is correct. The Product Backlog

• Usually stays the same for the release after the Team made their release commitment

• Can change at any time

• Is prioritized (sắp xếp ưu tiên) by the Product Owner

• Contains estimates which the Team can change at any time

• Contains all work that needs to be done on the product

• Contains all details of the requirements so they can be implemented

• Is used by the project manager to manage the project

Question. 34/34 When people attend a course, they often have *one* major question. The course would be a successful course when that major question gets answered. What is your *one* major question that needs to be answered during the course. Please remember your question as you'll be asked this during the course Your Answer