SCRUM Course Preparation Test

Project Management

Software Development

Agile Methodologies

PMI-ACP

Reviewed by Editorial Team

The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.

Learn about Our Editorial Process

| By Huemit1234

Huemit1234

Community Contributor

Quizzes Created: 1 | Total Attempts: 135

| Attempts: 135 | Questions: 33

Share on Facebook Share on Twitter Share on Whatsapp Share on Pinterest Share on Email Copy to Clipboard Embed on your website

Question 1 / 33

0 %

0/100

Score 0/100

1. 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

The Product Backlog is a one-dimensional(một chiều) (force-ranked) list in priority order. The Product Owner must constantly re-prioritize it as more is learned.

Explanation

The Product Backlog is a one-dimensional(một chiều) (force-ranked) list in priority order. The Product Owner must constantly re-prioritize it as more is learned.

Submit

About This Quiz

This Scrum Course Preparation Test is designed to assess understanding of Scrum principles, roles, meetings, and artifacts, ensuring readiness for Scrum implementation in projects.

What's your name? Tell us your name to personalize your report, certificate & get on the leaderboard!

2. 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?

See "Daily Scrum" section of the Scrum Primer

Explanation

See "Daily Scrum" section of the Scrum Primer

Submit

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

True

False

Sometimes

For more information, review the "Starting Scrum" section of the Scrum Primer

Explanation

For more information, review the "Starting Scrum" section of the Scrum Primer

Submit

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

True

False

Scrum is an alternative to traditional project management. It contradicts some parts of the PMBOK (Project management body of knowledge) . The essential (trọng yếu) responsibilities of the project manager role are split up between the Team, the Product Owner, and the Scrum Master.

Explanation

Submit

5. 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

See "Scrum Summary" in the Scrum Primer

Explanation

See "Scrum Summary" in the Scrum Primer

Submit

6. 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

Without integration the work there will not be a potentially-shippable product increment at the end of the Sprint

Explanation

Without integration the work there will not be a potentially-shippable product increment at the end of the Sprint

Submit

7. Question. 2/34 The CEO asks a team member to do some work outside the goals of the current Sprint in progress. What should the team member do?

Add it to the current Sprint.

Add it to the current Sprint while swapping out committed work of equal size.

Add it to the following Sprint.

Inform the Product Owner so he can work with the CEO

The Product Owner is the single person responsible for maximizing the return on investment (ROI) of the development effort.

Explanation

The Product Owner is the single person responsible for maximizing the return on investment (ROI) of the development effort.

Submit

8. 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

See "Scrum Roles" in the Scrum Primer

Explanation

See "Scrum Roles" in the Scrum Primer

Submit

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

True

False

Having different Sprint cycles commonly leads to problems in planning, synchronization (đồng bộ hóa) and stability as things are always moving.

Explanation

Having different Sprint cycles commonly leads to problems in planning, synchronization (đồng bộ hóa) and stability as things are always moving.

Submit

10. Question. 3/34 How 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

Most Product Backlog Items (PBIs) initially need refinement because they are too large and poorly understood. Teams have found it useful to take a little time out of Sprint Execution — every Sprint — to help prepare the Product Backlog for the next Sprint Planning Meeting.

See also the "Backlog Refinement Meeting" section of the Scrum Primer

Explanation

Submit

11. 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

"Tailoring" Scrum often leads to Scrum done poorly. Common reasons are
1) Not understanding the purpose of Scrum
2) The change Scrum requests is too difficult for the organization

Explanation

"Tailoring" Scrum often leads to Scrum done poorly. Common reasons are
1) Not understanding the purpose of Scrum
2) The change Scrum requests is too difficult for the organization

Submit

12. 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

Like chess, Scrum has a few simple rules that leave implementation decisions up to the people doing the work. Therefore it is intended to used as an empirical (dựa trên kinh nghiệm, quan sát hơn là lý thuyết) framework rather than a prescriptive, defined process.

Explanation

Submit

13. 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... 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

See "Updating the Sprint Backlog" in the Scrum Primer

Explanation

See "Updating the Sprint Backlog" in the Scrum Primer

Submit

14. 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

See "Sprint Retrospective" section of the Scrum Primer

Explanation

See "Sprint Retrospective" section of the Scrum Primer

Submit

15. 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

See "Sprint Planning" in the Scrum Primer

Explanation

See "Sprint Planning" in the Scrum Primer

Submit

16. 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

See the "Starting Scrum" section of the Scrum Primer

Explanation

See the "Starting Scrum" section of the Scrum Primer

Submit

17. 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

See also Scrum Primer p4:

"Scrum is an iterative, incremental framework for projects and product or application development."

Explanation

See also Scrum Primer p4:

"Scrum is an iterative, incremental framework for projects and product or application development."

Submit

18. 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

See "Retrospective" section of the Scrum Primer

Explanation

See "Retrospective" section of the Scrum Primer

Submit

19. 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).

See also "Scrum Roles" section of Scrum Primer.

Explanation

See also "Scrum Roles" section of Scrum Primer.

Submit

20. 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

Daily builds are for wimps." --Ron Jeffries

While the Scrum framework does not explicitly specify technical practices, it does emphasize increasing rigor in the definition of "done." Modern software development teams have learned to use practices such as TDD (Test Driven Development), Refactoring and Continuous Integration to keep the software product in a constantly known state. For many teams, this means building much more frequently than once per day.

Explanation

Submit

21. 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

See also the "Backlog Refinement Meeting" section of the Scrum Primer

Explanation

See also the "Backlog Refinement Meeting" section of the Scrum Primer

Submit

22. 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

See "Scrum Roles" in the Scrum Primer

Explanation

See "Scrum Roles" in the Scrum Primer

Submit

23. 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

The Team is cross-functional (even if individuals on the team choose to remain specialized). For more information, please review "Scrum Roles" section of Scrum Primer

Explanation

The Team is cross-functional (even if individuals on the team choose to remain specialized). For more information, please review "Scrum Roles" section of Scrum Primer

Submit

24. 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

For more information, review the "Sprint Planning" section of the Scrum Primer

Explanation

For more information, review the "Sprint Planning" section of the Scrum Primer

Submit

25. 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

The Team themselves work directly with the Product Owner

Explanation

The Team themselves work directly with the Product Owner

Submit

26. 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

The role of an enterprise's management changes from telling people what to do to leading and helping everyone do their best to achieve goals

Explanation

The role of an enterprise's management changes from telling people what to do to leading and helping everyone do their best to achieve goals

Submit

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

True

False

A Product Backlog is per Product, not per Team

Explanation

A Product Backlog is per Product, not per Team

Submit

28. 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

When teams are given complex work that has inherent(vốn có/thuộc về~ essential) uncertainty, they must work together to decide how much items they can commit to. Teams might use previous Sprints velocity (tốc độ) or some kind of hour estimating, but in the end it will always be the teams opinion on how much they can do. See the "Sprint Planning" section of the Scrum Primer

Explanation

Submit

29. 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)

For more information, see the "Sprint Review Meeting" section of the Scrum Primer.

Explanation

For more information, see the "Sprint Review Meeting" section of the Scrum Primer.

Submit

30. 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

2 weeks timeboxed sprints are most common, though in general shorter is better due to an increased feedback loop.
Anything longer than 4 weeks isn't Scrum anymore

Explanation

2 weeks timeboxed sprints are most common, though in general shorter is better due to an increased feedback loop.
Anything longer than 4 weeks isn't Scrum anymore

Submit

31. 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

See also "Sprint Planning" section of the Scrum Primer

Explanation

See also "Sprint Planning" section of the Scrum Primer

Submit

32. 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

Scrum teams attempt to build a potentially shippable (properly tested) product increment every iteration.

Please review the "Scrum Summary" section of the Scrum Primer

Explanation

Scrum teams attempt to build a potentially shippable (properly tested) product increment every iteration.

Please review the "Scrum Summary" section of the Scrum Primer

Submit

33. 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

The Product Backlog is owned by the Product Owner who can change and re-prioritize it at any time. The Team updates the estimates as they learn more about the product.

Teams do not make release commitments and there is no project manager role in Scrum.

Also see "Starting Scrum" and "Release Backlog" sections of the Scrum Primer

Explanation

Submit

View My Results

Quiz Review Timeline (Updated): Apr 17, 2024 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.