Scrum

Adaptation in Scrum means that if an inspector detects some deviation outside of acceptable limits then an adjustment must be made. Such adjustment can be made at any time since we don't want to interrupt the progress of the project.

False

All Scrum Teams must use the same standard definition of "Done".

False

Anyone may cancel a Sprint at any time as long as all stakeholders agree to do so.

False

During a Sprint, the Sprint Backlog can only be changed by the Product Owner.

False

What is the output of a Sprint review? a. A revised Product Backlog used for the next Sprint. b. A revised Scrum Guide given to the entire team. c. A Sprint Retrospective Document for the entire team. d. A Sprint Review Document given to the Scrum Master. e. A modified Owner's Backlog used by the Development Team.

a

What is the recommended size range of a Development Team? a. 3 to 9 members b. Anything above 9 members c. 5 to 10 members d. 1 to 3 members e. Anything below 9 members

a

Which of the following is not a formal event for inspection and adaptation in Scrum? a. Sprint Planning b. Sprint Conclusion c. Sprint Review d. Sprint Retrospective e. Daily Scrum

b

Every member of a Development Team must have a different title so people's roles/responsibilities don't overlap and everyone inside and outside of the team knows who is doing what.

False

If there are several Scrum Teams working on the same product release, each Development Team may follow their own definition of "Done".

False

Inspection in Scrum is not necessary because it gets in the way of people's productivity.

False

A Burndown Chart shows the amount of work remaining to be "Done" in a Sprint.

True

The Development Team doesn't have to explain to the Product Owner and the Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal.

True

Which of the following activities is not included in a Sprint Review? a. Demonstration by the Development Team of the work "Done" and answering of questions about the Increment. b. Review of things like budget, timeline, potential capabilities, and marketplace of the next release of the product. c. In-depth discussion on specific technical issues and defects found during the Sprint and who was responsible and is now accountable for them. d. Discussion of what went well during the Sprint, what problems it ran into, and how those problems were solved. e. Collaboration by the entire group on what to do next, so that the Sprint Review provides valuable input to future Sprint Planning.

c

Which of the following is not part of a Scrum team? a. Development Team b. Product Owner c. Scrum Designer d. Scrum Master

c

Which of the following is not a responsibility for the Scrum Master? a. Ensures that the Development Team has a Daily Scrum meeting and teaches them to keep it within a 15 minute time box. b. Ensures that only Development Team members participate in the Daily Scrum. c. Ensures that the Scrum Team adheres to Scrum theory, practices and rules. d. Helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which are not. e. To actually conduct the Daily Scrum meeting.

e

The Product Owner can be represented by either a single individual or a committee. There is no difference as long as the requirements are clear, consistent, and transparent.

False

There is no time limit when it comes to planning for a 4-week sprint. This way we can ensure that all the things that need to be "Done" are included in the Sprint.

False

A Scrum team can be successful when everyone is committed, focused, respects each other and demonstrates courage.

True

A Sprint Backlog entails all the selected items from the Product Backlog plus a plan for getting them "Done" by the end of the Sprint.

True

A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog accordingly.

True

A typical Scrum Sprint is a time-box of less than 4 weeks. During such a Sprint a "Done", useable and releasable product increment is created.

True

After the Development Team has selected the items from the Product Backlog to get "Done" then a Sprint Goal is established by the whole Scrum Team

True

All Scrum events are time-boxed and have a fixed maximum duration.

True

All requirements in a Product Backlog are given a description, a priority/order and an estimated value.

True

An important example of transparency in Scrum is a common definition of "Done" (i.e. a common agreement of the meaning of "the work is done").

True

An important service of the Scrum Master to the Development Team is to remove any impediments to their work progress.

True

During Sprint Planning the Development Team solely selects a number of items from the Product Backlog to get "Done" during that Sprint. No one else is involved in this decision.

True

During a Sprint Planning session we typically ask: What can be accomplished during this Sprint and how?

True

During each Daily Scrum, the Development team keeps track of the total work remaining of that Sprint in order to estimate the likelihood of achieving the Sprint Goal.

True

Each increment entails all the requirements from the Product Backlog that have been completed during a Sprint and meet the definition of "Done". In addition, each Increment is added to all previous Increments and tested thoroughly to ensure that all work together well.

True

If everyone in the Development Team understands what "Done" means then it is easier to decide how many items from the Product Backlog to select during a Sprint Planning.

True

No one tells the Development Team how to turn Product Backlog into increments of releasable functionality.

True

Scrum does not recognize of any sub-teams within the Development Team.

True

Scrum is a process framework for any product development (including software). It is lightweight, simple to understand but difficult to master.

True

Scrum is founded upon empiricism, which asserts that knowledge comes from experience and making decisions based on what is know.

True

Scrum teams are self-organizing and they choose how to best accomplish their work on their own without being directed by others outside the team.

True

Sometimes the work turns out to be different than the Development Team expected. In that case, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint.

True

The Daily Scrum is a 15-minute daily meeting held at the same time and place by the Development Team only. During this brief standing-up meeting the team inspects the work accomplished since the last Daily Scrum and discusses the action items for the next one.

True

The Product Backlog contains a list of requirements and is provided by the Product Owner who has custody of it.

True

The Product Backlog is dynamic and never complete. It continually evolves.

True

The Scrum Master serves the Product Owner in several ways including effective management of the Product Backlog.

True

The Sprint Retrospective is a time-boxed meeting held by the Scrum Team and it occurs after each Sprint Review. It's main purpose is for the team to reflect and make improvements accordingly during the next Sprint.

True

The whole Development Team is ultimately accountable for the project rather than each individual member.

True

When using Scrum everyone involved should understand the definition of "Done" to ensure transparency.

True

Which of the following is not an objective of the Sprint Retrospective? a. Discuss how additional resources can be secured in order to complete the rest of the project. b. Locate and discuss the main items that went well and any possible improvements. c. Adjust the definition of "Done" as needed d. Discuss how the last Sprint went with respect to process, people, relationships, and tools e. Establish an effective plan for implementing potential improvements in alignment with the way the Scrum Team works.

a

Which of the following is not part of a Scrum Sprint? a. Sprint Planning b. Sprint Testing c. Sprint Review d. Sprint Retrospective e. Daily Scrums

b

Which of the questions below is not discussed during a Daily Scrum meeting by each member? a. Do I see any impediment(s) that prevents me or the Development Team from meeting the Sprint Goal? b. How can I modify the scope of the project so that the Development Team can stay on schedule? c. What did I do yesterday that helped the Development Team meet the Sprint Goal? d. What will I do today to help the Development Team meet the Sprint Goal?

b

Who is involved during a Sprint Review meeting discussing what was done in the Sprint? a. The Development Team only b. The Scrum Team and other key stakeholders c. The Product Owner with the Scrum Master d. The Scrum Team only e. The Scrum Master with the Development Team

b

Who is responsible for managing the Product Backlog? a. Scrum Designer b. Product Owner c. Scrum Master d. Scrum Tester e. Development Team

b

Who is typically responsible for estimating the value/order and effort needed to complete each requirement in the Product Backlog? a. Both the Scrum Master and the Product Owner b. The Development Team c. The Scrum Team d. The Product Owner

b