certification PSM 1 - SCRUM, SCRUM PSM I Assessment, Professional Scrum Master 1 (PSM1) "Questions and explanations", SCRUM MASTER, Scrum Study Guide - Rachel, Scrum, Scrum, PSM I Assessment, PSM I Assessment

अब Quizwiz के साथ अपने होमवर्क और परीक्षाओं को एस करें!

The feedback from the Sprint Review impacts the next Sprint Planning.

TRUE

Who is responsible for engaging the stakeholders?

The Product Owner

Who is responsible for managing the Product Backlog?

The Product Owner

A baselined Product Backlog is called:

"Baseline" is a term used in traditional environments for referring to a finalized upfront plan that would be followed in the future, and used for evaluating the actual performance. There's no upfront planning and no baselines in Scrum.

2 types of roles

1. Chicken 2. Pig

Which statement best describes Scrum?

A framework within which complex products in complex environments are developed.

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

A soon as possible after they are identified

Sort Scrum events in the right order. Sprint planning Daily scrum Sprint review Sprint retrospective

A sprint begins with Sprint Planning, then there are several Daily Scrum meetings following by Sprint Review and then Sprint Retrospective.

task

A task is a specific "todo" with a given work estimation. A Feature can be broken into multiple tasks and so does a User Story. A task will be something like "Add new column to database called Rate and model it in the application - 1 hour of effort", or "create javascript function to validate input on price field - 1.5 hours of effort" or "create landing page for our campaign with Nike and connect it to our analytics system - 3 hours". Task resolution will always be much smaller and much more technical than Feature or User Story. It will explain what to do rather than why.

definition of done

A very simple definition of done can be encapsulated as: 1. Code Complete 2. Test Complete(unit, integration, performance, regression) 3. refactored properly 4. Documented (just enough) 5. Approved by Product Owner

Which technique is the least productive way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?

Act as a go-between for them

The Definition of Done can change during the project. a. False b. True

A new Increment of working software must be available

An Increment of "Done" working software, which is potentially releasable, must be produced at the end of each Sprint.

The Product Owner can delegate some of their responsibilities to the developers. a. False b. True

Sprint burndown charts are an efficient tracking tool because they show:

An estimate of the total work remaining for the Sprint

Which of these may a Development Team deliver at the end of a Sprint?

An increment of working software that is "done"

Which of these may a Development Team deliver at the end of a Sprint?

An increment of working software that is Done.

Who creates the increment? 1) The Development Team 2) The Scrum Master 3) The Development Team and The Product Owner 4) The Product Owner 5) The Scrum Team

Only members of the Development Team create the Increment.

It's up to the self-organizing team to decide which Scrum artifacts are needed in the project. a. True b. False

What comprises Scrum (select four)?

Artifacts Rules Roles Events

Development Team membership should change:

As needed, while taking into account a short term reduction in productivity.

What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Development Teams?

Ask the developers to divide themselves into teams.

When can the Product Backlog be updated?

At any time when done by the Product Owner or at the Product Owner's discretion

It is important that the product increment be released to production or shipped to customers at the end of each Sprint. A. True B. False

B. False

Scrum does not scale to large teams. A. True B. False

B. False

What does a burn-down chart measure? a. The amount of business value delivered to the customer b. Cost of the project across time c. Work remaining across time d. Work that is done based on the Definition of Done

When is the Sprint over? a. When the Sprint Backlog tasks are done b. When the Scrum Master announces the end of the Sprint c. When the Product Owner cancels the Sprint d. When the Product Owner announces the end of the Sprint

When should we release the product? a. At the end of each Sprint b. When the Increment is releasable c. When the Product Owner finds it appropriate d. When the Increment is free of defects

What is the Product Owner accountable for in Scrum?

Clearly expressing a Product Backlog that maximizes value and represents the needs of the stakeholders

Who is the most important stakeholder that the Product Owner should satisfy?

Considering the end users as the most important stakeholder helps increase value.

Scrum does not allow additional meetings that are not defined in Scrum. True or False?

False. Scrum allows additional meetings if they facilitate achieving the Sprint Goal.

Which of the following is a formal opportunity for inspecting and adapting? a. Release Planning b. Burn-down chart c. Product Backlog Refinement d. Daily Scrum

What are three benefits of self-organization?

a) Increased self-accountability b) Increased creativity e) Increased commitment.

How many developers can there be in a Development Team? a. 5 ± 3 b. 3 to 11 c. 6 ± 4 d. 6 ± 3 e. 4 to 12

D 3 to 9

What's the timeboxed duration of Sprints? a. One month b. Between two and six weeks c. Maximum a couple of months d. Maximum one month

During the Sprint, the Scrum Master's role is to do which two of the following:

Due to Scrum Guide: - Facilitating Scrum events as requested or needed - Removing impediments to the Development Team's progress

When should a Sprint Goal be created?

During Sprint Planning

Upon What kind of process control is SCRUM based?

Empirical

A Product Owner wants advice from the Scrum Master about estimating work in Scrum. Which of these is the guideline that a Scrum Master should give?

Estimates are made by the Development Team.

The Product Owner may choose to delegate the responsibility of estimating to the Development Team.

Estimating is the responsibility of the Development Team by default. The Product Owner doesn't have such authority in the first place, to delegate it.

A Product Owner is essentially the same thing as a traditional Project Manager?

FALSE

Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master. True or False?

False. The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

The definition of "Done" describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Development Team do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?

Immediately raise the issue to the Scrum Master as an impediment.

How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?

Frequently, but it should not get in the way of the work

When does Inspection occur?

Frequently, but not so often that it gets in the way of the work

Which phrase best describes a Product Owner?

Go-between development team and customers.

The three pillars of empirical process control are:

Inspection, Transparency, Adaptation

Does Scrum have a role called "Project Manager"?

How much time does the Sprint Planning take?

Not more than 8 hours

Which of the following does NOT apply to/suit Scrum?

Requirements can't be static in Scrum

Scrum does not have a role called "project manager."

TRUE

Who creates the increment?

The Development Team

Who can abnormally terminate a Sprint?

The Product Owner

The Product Owner is responsible for the definition of "Done".

"Development Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. If the definition of ""Done"" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If ""Done"" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of ""Done"" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of ""Done""."

When is a Product Backlog item "ready" for selection in a Sprint Planning meeting?

"Product Backlog items that will occupy the Development Team for the upcoming Sprint are refined so that any one item can reasonably be ""Done"" within the Sprint time-box. Product Backlog items that can be ""Done"" by the Development Team within one Sprint are deemed ""Ready"" for selection in a Sprint Planning. Product Backlog items usually acquire this degree of transparency through the above-described refining activities."

What is the main reason for the Scrum Master to be at the Daily Scrum?

"Scrum Master does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum."

The Development Team decides to divide the Sprint Backlog and assign ownership of every Sprint Backlog Item to separate individuals on the team. The Scrum Master

"Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and,Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole."

How complete should Sprint Backlog be at the end of the Sprint Planning meeting?

"Sprint Backlog should be complete enough to ensure there is work for the first 1-2 days of the Sprint at the end of the Sprint Planning meeting. Not all tasks are identified in the Sprint Planning; just enough to show what the development team is going to do in the next few days. The rest of the tasks will be created during the Sprint."

Which two statements are right about technical debt?

"Technical debt creates uncertainty because when more code is added, more problems will occur and the development slows down. Also, it creates false assumptions about the current state of the system; e.g. it might not be releasable."

Who decides the duration of the Sprint?

"The ""right"" duration of Sprint should balance the Product Owner's appetite for receiving increments of value, with the ability of the Development Team to supply those deliverables. The Scrum Master may have some coaching duties to perform in that regard. So, the Scrum Master is maybe the most important team member who decides the duration of Sprint but we do not agree that the Scrum Master is the only one who decides this duration."

The Development Team is free to change its engineering practices whenever they want.

"The Development Team is self-organized and cross-functional; they have to decide how best to handle their development, and this decision can evolve during the project, as more is learned about the needs.This is about their development and doesn't have to be constrained by the Sprints. The elements that shouldn't be changed during the Sprint are those required for keeping them focused on their development."

Who assigns tasks to the developers?

"They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;"

Which of the following best describes transparency?

"Transparency is about visibility and doesn't contain understanding; even though we'd better try our best to create the right understanding too, but that's another story.The "whole process" might be too much for some stakeholders; "significant aspects" is enough, as we treat most things in Agile environments."

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?

(1) By facilitating Development Team decisions (2) By removing impediments that hinder the Development Team

What two things best help the Product Owner manage the value of a product?

(1)The order of the Product Backlog (2)Validating assumptions of value through frequent releases

To what extent does technical debt limit the value a Product Owner can get from a product?

(1)The velocity at which new functionality can be created is reduced when you have technicaldebt. (2)Technical debt causes a greater percentage of the product's budget to be spent on maintenance of the product.

Which are properties of the Daily Scrum?

* It is fifteen minutes or less in duration. * Its location and time should remain constant.

Which three of the following are true about Scrum?

*- Scrum is based on empirical process control theory.

The length of the Sprint should be?

*- Short enough to be able to synchronize the development work with other business events. - Short enough to keep the business risk acceptable to the Product Owner. - No more than one calendar month.

Which of the following is required by Scrum?

*- Sprint Burndown Chart.

What are the Scrum Values?

- Commitment - Courage - Focus - Openness - Respect

What is a Development Team responsible for?

- Resolving internal team conflicts. - Organizing the work required to meet the Sprint Goal.

Which three of the following are timeboxed events in Scrum?

- Sprint Retrospective. - Sprint Planning. - Daily Scrum.

2 artifacts

1. Product backlog 2. Sprint backlog

Which of the following is not a time-box in Scrum?

1. Release Testing 2. Sprint 0 3. Release Retrospective 4. Spring Testing

Roles

1. Scrum master 2. IT team of 5-9 people 3. Product Owner

Which three of the following are true about Scrum? (Choose three answers)

1. Scum is a framework for developing and maintaining complex products 2. Scum is based on empirical process and control theory 3. Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products

Which following are true about the Product Owner role? Choose 3 answers.

1. The Product Owner is 1 person 2. The product Owner is accountable for ordering the Product Backlog 3. The Product Owner can be influenced by a committee

What two things best help the Product Owner manage the value of a product?

1. The order of the Product Backlog 2. Validating assumptions of value through frequent releases

What three factors are best considered when establishing the Sprint length

1. The risk of being disconnected from the stakeholders. 2. The ability to go to market with a product release 3. The frequency that team composition can be changed

What two things should be done if the Product Owner is unavailable?

1. Within the Sprint, the Development Team makes the best decisions possible to assure progress toward the Sprint Goal, re-aligning with the Product Owner once he/she is available again. 2. In a permanent state of unavailability, a new Product Owner needs to be appointed. Development efforts without a Product Owner are not employing Scrum.

self oragnization qualities

1. members are committed to clear, short-term goals 2. members can gauge the group's progress 3. members can observe each other's contribution 4. members feel safe to give each other unvarnished feedback

Sprint 0

1. team needs to be assembled 2. hiring or moving people onto the project 3. hardware to acquire or at least set up 4. write an initial product backlog (just at a high level) 5. Minimum viable product is created

The time-box for a Daily Scrum?

15 minutes.

Every Development Team should have: 1 - One Lead Developper and no more than 8 other members 2 - The competencies and skills needed to deliver a Done Increment in a Sprint. 3 - At least one representative from each major software engineering discipline (like QA, Dev, UX)

2 - The competencies and skills needed to deliver a Done Increment in a Sprint.

A Development Team asks their Product Owner to re-order the Product Backlog. The Team is waiting for an external supplier to deliver a specific software component. Without that component there won't be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master to help. What would be good advice to give the Product Owner? 1 - Tell the Product Owner that the Product Backlog should be ordered to maximize utilization of the Development Team 2 - Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate sprint 3 - Remind the Product Owner that their primary concern is the flow of value reflected in the ordering of the Product Backlog

3 - Remind the Product Owner that their primary concern is the flow of value reflected in the ordering of the Product Backlog

What is the time-box for a Sprint Review (on a one-month Sprint)?

4 hours for a monthly sprint

The customer goes to the Development Team in the middle of a Sprint, and asks them to add an important item to the Sprint Backlog. What should they do? a. Refer the customer to the Product Owner. b. Add the item to the next Sprint Backlog. c. Replace one of the existing items in the Sprint Backlog with the new one. d. Reject the request.

A The Product Owner is the person responsible for the items and the order in which they are developed.

The purpose of each Sprint is to release a piece of working software. a. False b. True

A The purpose is to create a potentially releasable piece of software. It doesn't have to be released

The Definition of Done can change during the project. a. True b. False

A Yes, it can be improved during the project. However, it shouldn't change in the middle of the Sprint.

Why does a Development Team need a Sprint Goal?

A Sprint Goal ensures that all of the Product Backlog items selected for the Sprint are implemented.

Which two of the following are mandatory elements in Scrum? a. Progress measurement b. Daily Scrums c. Test-Driven Development d. Face-to-face communications e. Burn-down charts

A, B

Which two statements are correct about the Definition of Done? a. Can be improved during the project. b. Used by the developers to forecast how many items they can pick for the Sprint. c. It's defined by the Product Owner. d. It makes it easier for the Scrum Master to measure performance and report progress.

A, B (a) Like everything else, you can improve it. Just make sure you don't do it during the Sprint. (b) It's used only as a guide, and the final decision belongs to the developers.

Which two of the following should NOT change during the Sprint? a. Sprint Goal b. Expected quality c. Sprint Backlog d. Product Backlog

A, B Did you notice the word "not" in the question? Those that stay fixed during the Sprint are needed to avoid distractions, and create a more productive environment. After all, Sprints are not so long that they create problems.

Which two of the following contribute the most to the Scrum value "focus"? a. Timeboxing b. Product Backlog Refinement c. Sprint Review d. Sprint Goal

A, D Scrum values are commitment, courage, focus, openness, and respect.

The Product Owner is the equivalent of project manager in Scrum. a. True b. False

Time can be allocated between two Sprints for integration. a. True b. False

What's the normal timeboxed duration of Sprint Review when there are 6 developers in the team and Sprints are two weeks long? a. 8 hours b. 2 hours c. 4 hours d. Maximum 8 hours

B Note that the duration of events is not dependent on the number of developers. The timeboxed duration of events is as follows: Sprint - Maximum 1 month Daily Scrum - 15 minutes Sprint Planning - 8 hours in a one-month Sprint, and shorter proportionally Sprint Review - 4 hours in a one-month Sprint, and shorter proportionally Sprint Retrospective - 3 hours in a one-month Sprint, and shorter proportionally

The Definition of Done is composed by the Product Owner, to ensure that the Increments will be usable by the end-users. a. True b. False

B The Definition of Done may come from the organization. Inside the project, it's the developers who adjust or define it.

Scrum is a methodology that tells in detail how to build software incrementally. A. True B. False

B. False

How long is a Sprint Review? A. 4 hours. B. It depends on the lenght of the Sprint. C. 2 hours. D. 3 hours.

B. It depends on the lenght of the Sprint.

Which of the following is not allowed in Scrum? a. Using Story Points b. Release Planning c. Hardening Sprints d. Refactoring

C Some concepts are mandatory; e.g. Sprint Retrospective. Some are not mandatory, but allowed; e.g. using User Stories. Some are not allowed; e.g. Sprint Zero. It's important not to mix the "not mandatory, but allowed" with the "not allowed".

How would you know if a Development Team is cross-functional? a. Each developer is expert in all technical layers of the system. b. They can do Pair-Programming if they decide to. c. They can do Test Driven Development if they decide to. d. They can create releasable Increments each Sprint.

D (d) Cross-functional: they must have all skills needed to create a releasable Increments every Sprint. A cross-functional team is one that has all types of expertise that is required to develop the product. Note that this is about the team as a whole, not individual team members.

The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do? A) Add the item to the current Sprint without any adjustments. B) Add the item to the current Sprint and drop an item of equal size. C) Add the item to the next Sprint. D) Inform the Product Owner so he/she can work with the CEO.

D The items selected for a Sprint have been selected as most valuable with the Product Owner. The items serve the Sprint's goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Development Team (Sprint Backlog) and the Product Owner (Product Backlog).

The performance of the Sprint should be measured at least... a. Before or after each release b. Once a week c. Once per Sprint d. Once a da

D The performance of the project is measured at least once per Sprint, and the Sprint performance is measured daily.

The Development Team is self-organised, and therefore, can decide to drop the Daily Scrums.

Daily Scrum is mandatory for Development Team in Scrum

Definition of "Done" is

Definition of "Done" initially defined per product by Scrum Team, but may change throughout the product development duration. At Sprint Retrospective Team may discuss changes in Definition of Done

Choose 3 activities that are the responsibilities of the Development Team in Scrum:

Designing the software is part of the development and should be done by the developers. They are self-organized and make technical decisions. Estimation is the responsibility of the developers because they are the people who will develop the item. The rest is done by the Product Owner.

Which two statements are correct during the Sprint?

During the Sprint, as more is learned, the scope may be clarified and re-negotiated between the Product Owner and Development Team. This is mainly focused on the interpretation of the Product Backlog items and the tasks created by decomposing them

Which statement best describes the Sprint Backlog as outcome of the Sprint Planning? A. Each task is estimated in hours. B. It is the Development Team's plan for the Sprint. C. It is ordered by the Prodcut Owner. D. Every item has a designated owner. E. It is a complete list of all work to be done in a Sprint.

E. It is a complete list of all work to be done in a Sprint.

Upon what type of process control is Scrum based?

Empirical

Scrum is founded on

Empiricism

A product increment must be released to production at the end of each Sprint

FALSE

Cross-functional teams are optimized to work on a technical layer of a system (e.g. GUI, database, middle... design contracts.)

FALSE

Scrum is a methodology that tells in details how to build software incrementally.

FALSE

The value delivered by a product can only be determined by revenue.

FALSE

Of the following choices, what is the most effective ways a Scrum Master can keep a Development Team working at its highest level of productivity?

Facilitate Development Team decisions and remove impediments.

A Scrum Team is only allowed to meet with stakeholders during Sprint Review.

False

Definition of "Done" is created during the first Sprint and remains unchanged until the Product release.

False

It is mandatory that the product increment be released to production at the end of each Sprint.

False

Multiple Scrum Teams working on the same project must have the same Sprint start date.

False

Scrum has a role called a Project Manager.

False

Scrum is a methodology that tells how to build software incrementally.

False

Scrum is a methodology that tells in detail how to build software incrementally.

False

The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.

False

It is a good practice to have at least two Product Owners on big projects. True or False?

False. The Product Owner is one person, not a committee, but the Product Owner may represent the desires of a committee in the Product Backlog.

The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team. True or False?

False. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.

If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled.

False. The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and Development Team.

What is the main reason for the Scrum Master to be at the Daily Scrum?

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.

What it the main reason for the Scrum Master to be at the Daily Scrum?

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.

Why should the Product Owner be present at the Daily Scrum?

He/She doesn't need to be there.

Which does a self-organizing Development Team choose?

How to best accomplish its work

Which of the following is a prerequisite for starting the Sprint Planning meeting?

If even the one item from Product Backlog is not ready for the first Sprint the entire Scrum Team may begin to refine the Product Backlog and do all other activities during the Sprint Planning

What are the common outcomes of Daily Scrums? (choose 2 answers)

Impediments are pointed out in the Daily Scrum, but we don't discuss them. Each developer informs everyone about the tasks they will handle in the next 24 hours, which is how the team progresses towards the goal.

Non-functional requirements must be captured in Definition of Done

It Is a good practice but this is not mandatory. Non-functional features are usually part of the Definition of Done, and should be considered for every Product Backlog item and every Increment.

When can a Development Team cancel a Sprint?

It can't, Only Product Owners can cancel Sprints

Sprint Retrospective is going after Sprint Review

It is correct because Sprint Retrospective is the last meeting (event) in Sprint.

Resolving internal conflicts inside the team is NOT the responsibility of the Development Team.

It is the responsibility of the Development Team to resolve conflicts inside the team

What is not a Development Team responsibility?

It is the responsibility of the Product Owner to break down the large Product Backlog items into smaller ones. The Development Team usually "helps" in this, but it doesn't make them responsible.

Chicken

Just boss around, dont do any work, just give directions, advise they are the people for whom product is being developed eg functional manager, stakeholders

Work Forecasting

Mathematical technique by calculating focus factor. Focus Factor = Optimal Velocity / Capacity Forecast = Focus factor * available capacity for iteration

What is the key concern when multiple Development Teams are working from the same Product Backlog?

Minimizing dependencies between teams

When do Development Team members take ownership of a Sprint Backlog Item?

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual Development Team member.

Development Team members volunteer to own a Sprint Backlog item:

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual development team member.

A cross-functional team in Scrum consists of which types of team members

None of the above (A specialist in QA, An architect, A release manager)

The stakeholders reorder the Product Backlog in the Sprint Review meeting.

Only the Product Owner may re-order the Product Backlog.

Which statement best describes a Product Owner's responsibility?

Optimizing the value of the work the Development Team does.

During a Sprint Retrospective, for what is the Product Owner responsible?

Participating as a Scrum Team member

During a Sprint Retrospective, for what is the Product Owner responsible?

Participating as a Scrum Team member.

In the middle of the Sprint, a Development Team finds that they have more capacity for additional work. They decide to change the Sprint Backlog by adding a few more Backlog Items from the Product Backlog. Who should be present to decide additional work and accordingly modify the Sprint Backlog (choose 2 answers)

Product Owner and members of the Development Team should decide which items they can add to the current Sprint Backlog

Which agile planning artefact should be updated at least once semi-annually?

Product Roadmap should be updated at least once semi-annually

forecast. What would you expect a Product Owner to do?

Re-negotiate the selected Product Backlog items with the Development Team to meet the Sprint Goal.

The Development Team finds out during the Sprint that they aren't likely to build everything they forecasted. What would you expect a Product Owner to do?

Re-work the selected Product Backlog items with the Development Team to meet the Sprint Goal.

What relationship does Scrum have to technical practices?

Scrum Development Teams with excellent technical practices will likely be more successful.

Scrum ensures the exception of technical debt

Scrum cannot ensure the exception of technical debt.

Scrum is an iterative and incremental Agile framework.

Scrum employs an iterative, incremental approach to optimize predictability and control risk.

The Scrum is founded on what type of process theory?

A four-hour Sprint Planning is common for Sprints that are ... long.

Sprint Planning is 8 hours for a one-month Sprint, and usually shorter proportionally for shorter Sprints.

story points over hours

Story points are more suitable in these situations because the points more accurately reflect both required effort and complexity. This is a result of points being used not only for estimation, but also as a means to measure and convey commitments and team velocity.

A Sprint Review is the only time the stakeholders and the Scrum Team can come together

TRUE

Sprints are never longer than a calendar month.

TRUE

Team Level

Teams are what power the agile release trains. Whether your teams are practicing ScrumXP or Kanban, VersionOne provides a centralized system for coordinating multiple teams, while giving each individual team a dedicated, streamlined environment to collaborate and deliver working software with ease.

Value Stream Level

Which of the following is not improved by using timeboxed Sprints?

Technical debt is any shortcoming in the solution that makes it less than "good enough", and might create problems in the future. Refactoring is a common way of reducing technical debt. Timeboxing, however, doesn't help with technical debt.Timeboxing the Sprints forces everyone to focus on the most important parts of the work (prioritization). It also ensures there will be frequent increments which demonstrate progress.When working inside timeboxes, it's better to limit work-in-progress, and get items done before going to the next ones. Otherwise, chances would be high that the team ends up with many in-progress items, and not enough "Done" items at the end of the Sprint.

A Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won't be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help. What would be good advice to give the Product Owner?

Tell the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.

A Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won't be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help.What would be good advice to give the Product Owner?

Tell the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.

chirping bird effect

That's often a good time for the trainer to leave the room! We can talk about self organization until we're blue in the face, and they won't really get it until we leave them alone — temporarily — to let them do it. I heard a story of one Scrum coach taking a nap under the table to get a team to step up more, and of Ken Schwaber standing outside the door of the team room during a Daily Scrum. I've seen teams have breakthroughs in self management when the person traditionally responsible for managing them left the room. I am inspired by the breakthroughs Scrum led to, especially among the lower status team members who aren't well represented in this discussion.

What does the "cone of uncertainty" tell us about Scrum projects?

The "cone of uncertainty" is about the fact that uncertainty is highest at the beginning of the project, and reduced as we progress. This uncertainty can be about the duration, requirements, etc.

What does Cone of Uncertainty show? 1) Dependencies, start times and stop times for project tasks 2) Hierarchy of tasks that comprise a project 3) How much work remains till the end of the Sprint 4) How much is known about the Product over time

The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.

Please, check all opportunities to inspect and adapt.

The Daily Scrum The Sprint Retrospective The Sprint Planning The Sprint Review

Select all that apply. Who must participate in the Daily Scrum?

The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

Which two of the following is true about the Daily Scrum?

The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At this event, the Development Team plans work for the next 24 hours.

Who is allowed to participate in the Daily Scrum? 1) The Product Owner 2) The Key Stakeholders 3) The Development Team 4) The Scrum Master

The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

How are stakeholders external to the Scrum team involved in the Daily Scrum?

The Daily Scrum is only for the Development Team. Others can attend, but they won't participate.

Who determines how work is performed during the Sprint?

The Development Team

Who determines how work is performed during the spring?

The Development Team

Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

The Development Team

Who is allowed to change the Sprint Backlog during the Sprint?

The Development Team

Who is allowed to participate in the Daily Scrum?

The Development Team

Who is required to attend the Daily Scrum?

The Development Team

Who is responsible for all estimates in the Product Backlog?

The Development Team

Who is responsible for creation of the Definition of "Done"?

The Development Team

Who is responsible for managing the progress of work during a Sprint?

The Development Team

Who is responsible for the system architecture of a product being developed using Scrum?

The Development Team

Should the Development Team members be cross-functional?

The Development Team as a whole is cross-functional, which means the sum of all developers with their different expertise. It doesn't mean that we need to have cross-functional individuals, or "Development Team members". Each individual is expert in one or more technical layers or aspects of the project, and the team they create is cross-functional (have all the expertise required to get the job done, without any need for external resources).

Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

The Development Team.

When should Increment be shipped?

The Increment should be potentially releasable (shippable), but we don't have to release all of them. It depends on the project environment and the customer, and the Product Owner is supposed to decide on it

Which best describes the role of the PMO in an organization that uses Scrum?

The PMO may be tasked with higher level optimizations for program and portfolio management, based on effective application of techniques that complement Scrum.

What is the input to the Sprint Planning? Select four.

The Product Backlog Projected capacity of the Development Team during the Sprint The latest product Increment Past performance of the Development Team

All work that the developers should do originate from the Product Backlog.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.

Which Scrum artefacts can be prioritised?

The Product Backlog is ordered (prioritized) based on the business value. The items in the Sprint Backlog follow the same order they had in the Product Backlog, and therefore, are prioritized.

Who is responsible for clearly expressing Product Backlog items?

The Product Owner

Who is responsible for the Product Backlog?

The Product Owner

Who must do all the work to make sure Product Backlog items conform to the definition of "Done?"

The Product Owner

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?

The Product Owner

The number one priority of the Product Owner is

Who monitors the remaining work of the Sprint Backlog?

The Product Owner is responsible for measuring the progress of the project and tracking the remaining work in the Product Backlog.The Development Team is responsible for measuring the progress of the Sprint and tracking the remaining work in the Sprint Backlog

Who is responsible for maximising the value of the work the Development Team performs?

Who is allowed to make changes in the Product Backlog? Select two options. 1) The Product Owner 2) The Development Team, but with permission of the Product Owner 3) The Key Stakeholders 4) Anyone 5) The Scrum Master

The Product Owner is the sole person responsible for the Product Backlog. However, he or she can delegate some work related to product backlog management to the Development Team.

Agile pi

The Program Increment (PI) is the largest plan-do-check-adjust (PDCA) learning cycle in SAFe. A PI is to the Agile Release Train (or Value Stream) as an Iteration is to the Agile

For which is the Scrum Master responsible?

The Scrum (framework) process being adopted and used properly.

Who is responsible for coping with incomplete artifact transparency?

The Scrum Master

The Scrum Master does the following regarding the Daily Scrum (select all applicable variants): 1) Ensures that the Development Team has the meeting 2) Is responsible for conducting the Daily Scrum 3) Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box 4) If others are present at the Daily Scrum, ensures that they do not disrupt the meeting

The Scrum Master ◦ Ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. ◦ Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. ◦ If others are present at the Daily Scrum, ensures that they do not disrupt the meeting.

The Scrum Master is a management role.

The Scrum Master is a management role, but for the process, rather than for the people.

What is the right action from the Scrum Master in response to a Product Owner who has problems managing the Product Backlog?

The Scrum Master is supposed to know the tools and techniques and to help everyone in that regard. However, it's only about helping, training, coaching, and consulting, rather than taking over.

The Sprint Review is mainly an inspect and adapt opportunity for which group?

The Scrum Team and stakeholders.

What happens if the Development team cannot complete its work by the end of the Spring?

The Spring length holds and the development team continuously learns what is actually possible to do within a Spring of this length

What belongs solely to the Development Team?

The Sprint Backlog

The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.

The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint.

What output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

The Sprint Goal

Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

The Sprint Goal

The Sprint Retrospective is

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Sprint Review is the only time when stakeholder feedback is captured

The Sprint Review is probably the most important opportunity for capturing feedback, but adaptation is not limited to that. The Product Owner is constantly in contact with the stakeholders to identify new Product Backlog items, or to refine them.

What happens if the Development Team cannot complete its work by the end of the Spring?

The Sprint length holds and the development team continuously learns what is actually possible to do within a spring of this length

Which role is the equivalent of project manager in Scrum?

The project management activities are distributed among all three roles

What two factors should be most considered when establishing the length of a Sprint?

The risk of being disconnected from the stakeholders. The level of uncertainty over the technology to be used.

Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master. True or false?

The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.

Which of the following is done in the first Sprint?

There's no difference between the first Sprint and the next ones. The main purpose is creating Increments.

Which outcome is expected as Scrum Teams mature?

They will improve their definition of "Done" to include more stringent criteria.

Which is a benefit of establishing naming standards for code?

To make the code more readable.

A Scrum Master is essentially the same thing as a traditional PM (Project Manager).

True

A properly functioning Scrum Team will have at least one Release Sprint and may well have several.

True

Multiple Scrum Teams working on the same product or system all select work from the same Product Backlog.

True

Scrum does not describe agile processes and techniques.

True

Scrum does not have a role called "project manager."

True

The purpose of a Sprint is to have a working increment of product done before the Sprint Review

True

The purpose of a Sprint is to produce a done Increment of product.

True

Every Scrum Team must have a Product Owner and Scrum Master

True. Outcomes are affected by their participation and availability

How should the Product Owner forecast the completion date?

Using a trend line in the burn-down chart can help (if the team is using that chart), as well as simple or complex formulas such as the one mentioned above. But all of these are just guides for the Product Owner and s/he should consider all factors and come up with a reliable completion date forecast.

Which description best fits the role of the Product Owner?

Value Maximizer

Which phrase best describes a Product Owner?

Value Optimizer

Which answer best describes the topics covered in Sprint Planning?

What can be done and how to do it.

The Product Backlog is ordered by:

Whatever is deemed most appropriate by the Product Owner.

What variables should a Product Owner consider when ordering the Product Backlog?

Whatever is most appropriate for the Product Owner to achieve the product's goals and to optimize the value received

The Product Owner must release each Increment to production.

When it makes sense.

When might a Sprint be abnormally cancelled?

When the Sprint Goal becomes obsolete.

If burndown charts are used to visualize progress, what does a trend line through a release burndown indicate?

When the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team

If burndown charts are used to visualize progress, what do they track?

Work remaining across time

Could the Product Owner and the Scrum Master be a part of the Development Team?

Yes if they are also executing the work of the Sprint Backlog.

An organization has decided to adopt Scrum

but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?,All of the above.

stages of group development

forming, storming, norming, performing

The Product Owner can transfer some of his

her accountability to the developers. /The Product Owner can delegate his/her responsibilities to the development team, but s/he stays accountable

Select the two meetings in which people outside the Scrum Team are allowed to participate. 1) The Sprint Planning 2) The Sprint Review 3) The Daily Scrum 4) The Sprint Retrospective

◦ The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. ◦ The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting

What are three ways Scrum promotes self-organization? (Choose three.)

1. By the Development Team deciding what work to do in a Sprint. 2. By removing titles for Development Team members. 3. By being a lightweight framework.

When is a Sprint cancelled?

Sprints are cancelled by the Product Owner only because they don't make sense anymore, or become obsolete. It's mainly about the Sprint Goal

Daily Scrum and Sprint Executioin

Stand up meeting every morning @ 10 AM @same place Duration = 15 mins Memebers: SM, Team, PO(optional) purpose- 1. 3 questions everybody adressess, what i did, what ill do, what problems i faced 2. also a sidebar list is prepared(for irrelevant topics which can be discussed after the meeting) 3. everyone should be present. imp. Execution - TDD(Test driven development, test, code, refactor) - continuous integration server running regression testing - pair programming done Artifacts- information radiators - current Sprint Task List, - Sprint Burndown Chart, - Impediments List. -if boss present, invisible gun effect -a team that needs additional expertise in product requirements will benefit from increased Product Owner involvement, completion- when timebox expires output - potentially shippable product increment

story points

Story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story. In simple terms its a number that tells the team how hard the story is. Hard could be related to complexity, Unknowns and effort. - no specific measure of time - relative size - leverage fibonacci series - highlights larger differences - prevents premature commitments

What does it mean for a Development Team to be cross-functional

The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software.

The Product Backlog is ordered by

The Product Backlog is ordered by importance. This importance is generated by the Product Owner

Who has the final say on the order of the Product Backlog?

The Product Owner

Who should know the most about the progress toward a business objective or a release?

The Product Owner

What best describes the relationship of the Product Owner and the stakeholders?

The Product Owner actively asks for stakeholder input and expectations to process into the Product Backlog.

When a Development Team determines that is has over-committed itself for a Sprint, who has to be present when reviewing and adjusting the Sprint work selected?

The Product Owner and the Development Team

During a Sprint, a Development Team determines that it will not be able to finish the complete forecast. Who should be present to review and adjust the Sprint work selected?

The Product Owner and the Development Team.

The Product Owner can delegate the ordering of the Product Backlog to the Development Team

The Product Owner can delegate the ordering of the Product Backlog to the Development Team, however, the Product Owner remains accountable.

The Product Owner should invite stakeholders to the Sprint Retrospective.

The Product Owner invites the stakeholders to the Sprint Review meeting. The Sprint Retrospective is internal to the team. As usual, others can attend, but they cannot participate

This role represents the interests of the stakeholders and ensures the value of the work completed

Who is responsible for representing the interests of the stakeholders?

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?

The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item's priority must address the Product Owner. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner's decisions are visible in the content and ordering of the Product Backlog. No one can force the Development Team to work from a different set of requirements.

What comprises Scrum (select four)? 1) Artifacts 2) Reports 3) Burn-down charts 4) Roles 5) Events 6) Rules

The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum's success and usage. The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them.

What are the Scrum Artifacts? Select all applicable items. 1) Product Backlog 2) The Sprint Goal 3) Sprint Backlog 4) Increment 5) The list of removed impediments

The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.

....... are Scrum values

When the values of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the Scrum pillars of transparency, inspection, and adaptation come to life and build trust for everyone.

Imagine you are a Scrum Master. There are 10 professionals (developers and QAs) and the Product Owner. How to distribute people between development teams? Choose all applicable variants:

* 3 teams of 4, 3 and 3 people (each team is cross-functional) * 2 teams of 6 and 4 people (the professionals after a short meeting decided this is the best variant)

What are the two essential features a Scrum Team should possess?

* It should have all competencies needed to accomplish the work without depending on others not part of the team * It should choose how best to accomplish their work, rather than being directed by others outside the team

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly? A) The Product Owner B) The Development Team C) The Scrum Master D) The Project Manager

A The Product Owner is the sole person responsible for managing the Product Backlog, which includes that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.

The purpose of a Sprint is to produce a done increment of working product. A) True B) False

A The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", usable, and potentially releasable product Increment is created.

How much work must a Development Team do to a Product Backlog item it selects for a Sprint? A) As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done". B) As much as it can fit into the Sprint. C) All development work and at least some testing. D) Analysis, design, programming, testing and documentation.

A The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done".

What is Scrum?

A framework within which people can address complex adaptive problems, while delivering valuable products.

What is the result of the Sprint Review?

A revised Product Backlog that defines the probable Product Backlog items for the next Sprint

If an inspector determines that one or more aspects of a process deviate outside acceptable limits when an adjustment must be made?

As soon as possible to minimize further deviation

What is the recommended size for a Development Team (within the Scrum Team)? A) Minimal 7 B) 3 to 9 C) 7 plus or minus 2 D) 9

B Optimal Development Team size is small enough to remain nimble and large enough to complete significant work. Fewer than three Development Team members decreases interaction and results in smaller productivity gains. More than nine members simply requires too much coordination.

When multiple teams work together on the same product, each team should maintain a separate Product Backlog. A) True B) False

B Products have one Product Backlog, regardless of how many teams are used. Any other setup makes it difficult for the Development Team to determine what it should work on.

Why is the Daily Scrum held at the same time and same place? A) The place can be named. B) The consistency reduces complexity. C) The Product Owner demands it. D) Rooms are hard to book and this lets it be booked in advance.

B The Daily Scrum is held at the same time and place each day to reduce complexity.

The three pillars of empirical process control are: A) Respect For People, Kaizen, Eliminating Waste B) Planning, Demonstration, Retrospective C) Inspection, Transparency, Adaptation D) Planning, Inspection, Adaptation E) Transparency, Eliminating Waste, Kaizen

C Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

Development Team membership should change: A)Every Sprint to promote shared learning. B) Never, because it reduces productivity. C) As needed, while taking into account a short term reduction in productivity. D) As needed, with no special allowance for changes in productivity.

C Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.

The Product Backlog is ordered by: A) Size, where small items are at the top and large items are at the bottom. B) Risk, where safer items are at the top, and riskier items are at the bottom. C) Least valuable items at the top to most valuable at the bottom. D) Items are randomly arranged. E) Whatever is deemed most appropriate by the Product Owner.

E The Product Owner decides what makes the most sense to optimize the value of the work being done by the Development Team.

The Scrum Master does the following regarding the Daily Scrum (select all applicable variants):

Ensures that the Development Team has the meeting Enforces the rule that only Development Team members participate in the Daily Scrum Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box

How does the Scum Master help to the Product Owner? Select the three most appropriate answers.

Facilitating Scrum events as requested or needed Finding techniques for effective Product Backlog management Understanding product planning in an empirical environment

If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled.

False

It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.

False

It is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release.

False

Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master.

False

Scrum does not allow additional meetings that are not defined in Scrum.

False

What does Burn-down Chart show?

How much work remains till the end of the Sprint

The purpose of the Sprint Retrospective is to (select three):

Identify and order the major items that went well and potential improvements Inspect how the last Sprint went with regards to people, relationships, process, and tools Create a plan for implementing improvements to the way the Scrum Team does its work

What is the order of items in the Product Backlog?

Less valuable and most unclear items at the bottom

Is it allowed to skip the Daily Scrum if there is nothing interesting to tell about?

What part of the capacity of the Development Team does Product Backlog refinement usually consume?

Not more than 10%

What does Product Backlog management include? Select three most applicable items.

Ordering the items in the Product Backlog to best achieve goals and missions Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next Optimizing the value of the work the Development Team performs

How does the Scrum Master serve the Organization? Select the three most appropriate answers.

Planning Scrum implementations within the organization Leading and coaching the organization in its Scrum adoption Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization

What are the Scrum Artifacts? Select all applicable items.

Product Backlog Increment Sprint Backlog

What are the three most applicable characteristics of the Product Owner?

Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert

What are the three main qualities the team model in Scrum is designed to optimize?

Productivity

Sort Scrum events in the right order.

Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?

The Development Team

Who is responsible for the monitoring of the remaining work towards the Project Goal?

The Product Owner

Who participates in the Sprint Planning? Select three.

The Product Owner The Development Team The Scrum Master

Who is allowed to make changes in the Product Backlog?

The Product Owner The Development Team, but with permission of the Product Owner

Who is responsible for crafting the Sprint Goal at the Sprint Planning?

The Scrum Team

What provides guidance to the Development Team on why it is building the Increment?

The Sprint Goal

What are the formal Scrum events for inspection and adaptation?

The Sprint Planning The Daily Scrum The Sprint Retrospective The Sprint Review

In which meetings the Key Stakeholders are allowed to participate?

The Sprint Review

Select the two meetings in which people outside the Scrum Team are allowed to participate.

The Sprint Review The Sprint Planning

What is the Increment?

The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints

All Development Teams working on the same Product should use the same Product Backlog.

True

During each Sprint Retrospective the Scrum Team reviews the Definition of Done and changes it if necessary.

True

Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.

True

The Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

True

What are the three main questions each member of the Development Team should answer at the Daily Scrum?

What will I do today to help the Development Team meet the Sprint Goal? What did I do yesterday that helped the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less?

Yes, if the remaining work is also estimated, maybe in bigger units

How does Definition of "Done" help to the Scrum Team? Select the three most applicable items.

* DoD is used to assess when work is complete on the product Increment * DoD ensures artifact transparency * DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning

Who participates in the Sprint Review? Select all applicable variants.

* The Key Stakeholders * The Development Team * The Product Owner * The Scrum Master

What happens during the Sprint? Select three answers.

*No changes are made that would endanger the Sprint Goal *Quality goals do not decrease *Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned

Which two statements best describe the Product Backlog? a. It changes as we learn more about the project. b. Contains all tasks identified by the developers. c. It's used to create the project plan. d. It is never baselined.

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity? A) By facilitating Development Team decisions B) By removing impediments that hinder the Development Team C) By starting and ending the meetings at the proper time D) By keeping high value features high in the Product Backlog

A, B A Scrum Master is a servant-leader for the Development Team. Facilitation and removing impediments serves a team in achieving the best productivity possible.

Who is on the Scrum Team? Correct answer A) The Scrum Master B) The Product Owner C) The Development Team D) Project Manager E) None of the above

A, B, C The Scrum Team consists of the Scrum Master (manages the process), the Product Owner (decides what to do) and the Development Team (does the work).

Which two things does the Development Team do during the first Sprint? A) Deliver an increment of potentially releasable software. B) Determine the complete architecture and infrastructure for the product. C) Develop and deliver at least one piece of functionality. D) Develop a plan for the rest of the release. E) Create the complete Product Backlog to be developed in subsequent Sprints

A, C The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially releasable product Increment is created. This applies to every Sprint

Which of the below are roles on a Scrum Team? A) Development Team B) Users C) Customer D) Product Owner E) Scrum Master

A, D, E The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

What are the three pillars that uphold Scrum?

Adaptation Inspection Transparency

When many Development Teams are working on a single product, what best describes the definition of "Done?" A) Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint. B) Each Development Team uses its own but must make their definition clear to all other teams so the differences are known. C) All Development Teams must have a definition of "Done" that makes their combined work potentially releasable. D) It depends.

C Scrum requires an Increment to be releasable. This is an Increment of product. Many teams working on a single product are expected to deliver such an Increment.

When might a Sprint be abnormally cancelled? A) When it becomes clear that not everything will be finished by the end of the Sprint. B) When the Development Team feels that the work is too hard. C) When the sales department has an important new opportunity. D) When the Sprint Goal becomes obsolete.

D A Sprint can be cancelled before the Sprint time-box is over. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change.

When does the next Sprint begin? A) Next Monday. B) Immediately following the next Sprint Planning. C) When the Product Owner is ready. D) Immediately after the conclusion of the previous Sprint.

D A new Sprint starts immediately after the conclusion of the previous Sprint.

Who has the final say on the order of the Product Backlog? A)The Stakeholders B)The Development Team C)The Scrum Master D)The Product Owner E)The CEO

D The Product Owner is the sole person responsible for managing the Product Backlog.

Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum? A) Lead the discussions of the Development Team. B) Ensure that all 3 questions have been answered. C) Facilitate in a way that ensures each team member has a chance to speak. D) Teach the Development Team to keep the Daily Scrum within the 15 minute time-box. E) All answers apply.

D The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.

When is a Sprint over? A) When all Product Backlog items meet their definition of done. B) When the Product Owner says it is done. C) When all the tasks are completed. D) When the time-box expires.

D The duration of a Sprint is fixed and cannot be shortened or lengthened.

All the Scrum Teams working on the same product should have the same Sprint length.

False

It is a good practice to have at least two Product Owners on big projects.

False

Scrum recommends using only those Scrum components and rules which suit most for a particular project.

False

The Daily Scrum time-box depends on the size of the Development team.

False

The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team.

False

The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team.

False

How does the Scrum Master serve the Development Team? Select the three most appropriate answers.

Helping the Development Team to create high-value products Coaching the Development Team in self-organization and cross-functionality Removing impediments to the Development Team's progress

What does Cone of Uncertainty show?

How much is known about the Product over time

What happens when a Sprint is cancelled? Select three.

If part of the work is potentially releasable, the Product Owner typically accepts it Any completed and "Done" Product Backlog items are reviewed All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog

What is the Sprint Retrospective?

It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint

What are Product Backlog features? Select three.

It is never complete As long as a product exists, its Product Backlog also exists It is dynamic

What are the characteristics of a Development Team? Select three most appropriate choices.

Scrum recognizes no sub-teams in the Development Team Accountability belongs to the Development Team as a whole Scrum recognizes no titles for Development Team members other than Developer

Please, select a time-box for each Scrum event.

Sprint Planning - 8 hours or less Daily Scrum - 15 minutes Sprint Review - 4 hours or less Sprint Retrospective - 3 hours or less

The Scrum Team consists of

The Development Team The Scrum Master The Product Owner

What could be a source of requirements for any changes to be made to the product?

The Product Backlog

What is the Sprint Backlog?

The Product Backlog items selected for this Sprint plus the plan for delivering them

Who has the authority to cancel the Sprint?

The Product Owner

What are the questions the Sprint Planning answers? Select two.

What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved?

Could the Product Owner and the Scrum Master be a part of the Development Team?

Yes

Scrum can be used for sustaining complex products. a. False b. True

What is a Development Team responsible for? (Choose two.)

1. Resolving internal team conflicts. 2. Organizing the work required to meet the Sprint Goal.

Pig

Actual doers, committed to projects, creates tangile deliverable eg scrum master, PO, developers, testers

A Sprint Retrospective should be held:

At the end of each Sprint.

What should be taken into account for the Definition of "Done"? Select the two most appropriate items.

Definition of "Done" of other Scrum Teams working on the same Product Conventions, standards and guidelines of the Organization

A Product Owner is essentially the same thing as a traditional Project Manager?

False

Who should know the most about the project performance?

Measuring the release or project performance is the Product Owner's responsibility.

Why does a Development Team need a Sprint Goal?

The Development Team is more focused with a common yet specific goal

The Development Team should have all the skills needed to:

Turn the Product Backlog items it selects into an increment of potentially releasable product functionality.

The Product Owner must release each increment to production.

When it makes sense

Commitment driven sprint planning

brings the top-priority product backlog items into the meeting and describes them to the team, usually starting with an overview of the set of high-priority items.

difference between scrum and kanban

scrum ephasis on schedule On a Kanban team, there are no required time boxes or iterations. The limitations placed on various conditions in the work flow will be regulated early in a team's (or organization's) use of Kanban until an optimal set of limits is arrived at to keep the flow steady and efficient. Kanban cross functional team is not required team of experts and set of generalists work fine

Who is responsible for all estimation in Sprint?

Only the Development Team is responsible for estimation in Sprint

Which list below includes the attributes of a good User Story

"A good user story should be INVEST: - ""I""ndependent (of all others)- ""N""egotiable (not a specific contract for features)- ""V""aluable (or vertical)- ""E""stimable (to a good approximation)- ""S""mall (so as to fit within an iteration)- ""T""estable (in principle, even if there isn't a test for it yet)"

The Product Owner is accountable for the result and therefore should have the final say over the definition of "Done".

What does the Development Team do during the first Sprint? (select all that apply)

In this event, the Scrum Team adapts the definition of done

"During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of ""Done"", if appropriate and not in conflict with a product or organizational standards."

A new Sprint starts immediately after the conclusion of the previous Sprint

"Each new Sprint starts immediately after the conclusion of the previous one; there's no time between two Sprints."

All of the following occur in the second part of the Sprint Planning meeting, except

"Having set the Sprint Goal and selected the Product Backlog items for the Sprint, the Development Team decides how it will build this functionality into a ""Done"" product Increment during the Sprint. The Product Backlog items selected for this Sprint plus the plan for delivering them is called the Sprint Backlog. The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work may be of varying size or estimated effort. However, enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint."

Ordering the Product Backlog item is part of the Product Backlog refinement.

"Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail. Product Backlog items that will occupy the Development Team for the upcoming Sprint are refined so that any one item can reasonably be ""Done"" within the Sprint time-box. Product Backlog items that can be ""Done"" by the Development Team within one Sprint are deemed ""Ready"" for selection in a Sprint Planning. Product Backlog items usually acquire this degree of transparency through the above described refining activities."

Time can be allocated between the two Sprints for integration.

"Integration is part of the definition of "Done" and should happen as part of the development, during the Sprint.Each new Sprint starts immediately after the previous one; there's no time between the two."

That is the reason why the Daily Scrum is held at the same time and same place

"It's not wise to spend time everyday scheduling the next Daily Scrum when the meeting itself is only 15 minutes. We usually expect to have a common place for the team and have them collocated. The meeting will be held in the same commonplace, in front of the Scrum board; we don't book a meeting room for it."

What does it mean to say a Product Backlog item is "Done"? (Choose 3 answers)

"Items are "Done" when they are completely based on the definition of "Done". In that case, they would have the potential of creating a releasable/shippable Increment that is usable by the end user.Tests are also part of the work and items are not "Done" before the tests are complete; even the user acceptance tests.Quality requirements are part of the work, but not all of it (e.g. non-functional features and development processes are also part of the work).We cannot trust the identified tasks because we might have missed some tasks and the sum of them do not conform to the definition of "Done"."

What are the benefits of having tests in the definition of "Done"? (Choose three answers)

"Items are not really done unless we have tested them; so, tests should be included in the definition of "Done". In this case, the Increments will be closer to what we can practically call "complete", "done", "potentially releasable", or "potentially shippable"; to something useable for the users"

How should a Product Backlog item be refined when it is located at the top? (choose 2 answers)

"Items at the top of the Product Backlog should be small enough to fit in one Sprint. They should also be clear and detailed enough; but not too detailed (e.g. not with all the tasks identified), as it would be an upfront planning. Tasks are created gradually during the Sprint. Product Backlog items require multiple expertise, and are usually done by multiple developers. Therefore, they are not assigned. Tasks, however, are assigned to the individual developers, while everyone stays accountable"

How complete should the Sprint Backlog be at the end of the Sprint Planning meeting?

"Not all tasks are identified in the Sprint Planning; just enough to show what the development team is going to do in the next few days. The rest of the tasks will be created during the Sprint."

The Product Backlog attributes are:

"Product Backlog items have the attributes of a description, order, estimate, and value. Product Backlog items often include test descriptions that will prove its completeness when ""Done""."

When should the Product Backlog items be refined? (choose 2 answers)

"Product Backlog refinement is a continuous activity. When an item is at the top of the backlog, which means it will be developed in the near future, more refinements are usually needed to make sure it is clear and contains just enough details (not all possible details). It's preferable to have the items that will be selected in the Sprint Backlog completely refined before Sprint Planning; however, it's OK to have more refinement done during the development. Remember that there's no such thing as Sprint 0, and there's no time between two Sprints that can be spent on something such as refinement. The team is also cross-functional and does the a-z of the work needed for each item, including refinement; they don't use people from other parts of the company."

Software dependencies can influence how the Product Owner orders Product Backlog items

"Software dependencies may really influence PBI ordering. It doesn't mean the Product Owner must always order the PBI by referring to software dependencies, but the question is ""can"" instead of ""must"". Maybe it is not very good practice but it is up to the Product Owner to decide if this factor is important for ordering the items or not. So it can be one of the reasons to re-order the item. This is one of many so-called ""confusing"" questions in the real exam."

Which statement can be considered as an Increment?

"The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be ""Done,"" which means it must be in useable condition and meet the Scrum Team's definition of ""Done""."

An increment is

"The Incrementis the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be ""Done,"" which means it must be in useable condition and meet theScrumTeam's definition of ""Done"""

What is a Product Backlog?

"The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists."

The Development Team cannot deliver the Increment because they don't understand a functional requirement. What should they do?

"The Product Owner is responsible for making all items clear and understood. If the problem wasn't solved, then there's no option other than leaving it to go back to the Product Backlog at the end of the Sprint, and be done later. The team is cross-functional and doesn't use external help. We don't deliver partially complete items; everything should be done based on the definition of "Done"."

The Product Owner is the sole person responsible for managing the Product Backlog.

"The Product Owner is the sole responsible person, and they even "own" the Product Backlog. Note: remember that the Sprint Backlog is owned by the Development Team. This is not however in contrast to the fact that the Product Backlog items are estimated by the developers; they provide this information to the Product Owner to be included in the Product Backlog."

The Product Owner is not collaborating with the Development Team during the Sprint. What are two valuable actions for a Scrum Master to take? (Choose two.)

1. Bring up the problem in the Sprint Retrospective. 2. Coach the Product Owner in the values of Scrum and incremental delivery.

The Product Owner has doubts about the quality of the definition of "Done". What should s/he do?

"The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of ""Done"", if appropriate and not in conflict with a product or organizational standards."

How much of the Sprint Backlog should be defined during the Sprint Planning meeting?

"The Sprint Backlog includes the items selected from the Product Backlog and the tasks created by decomposing the items.The items are completely planned in the Sprint Planning, but not all tasks are created; just enough for the first few days of development. The rest of the tasks will be created during the Sprint."

The items selected from the Product Backlog for the Sprint Backlog must be "ready".

"The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a ""Done"" Increment."

Which statement best describes the Sprint Backlog?

"The Sprint Backlog is created during the Sprint Planning and includes the items selected from the Product Backlog (by the Development Team), and the tasks created by decomposing the items (by the Development Team). Developers keep adding tasks during the Sprint, so, the Sprint Backlog updates. It's the Development Team's plan for the current Sprint. This plan is not detailed upfront. If the Development Team cannot deliver some of the items, they will go back to the Product Backlog and will be ordered again; they do not go to the next Sprint automatically. Each task is assigned to one developer or a pair of developers, but the ownership is still shared. Items are not assigned or owned by specific developers, all of them share accountability."

Which two statements are true about the Sprint Backlog?

"The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a ""Done"" Increment. The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting."

The Product Owner is responsible for preparing the Sprint Goal before the Sprint Planning.

The Sprint Backlog makes visible all of the work the ... identifies as necessary to meet the Sprint Goal.

Which two of the following are true about the Sprint Retrospective? (Choose 2 answers)

"The Sprint Retrospective happens after the Sprint Review; it's the last event in the Sprint. It's three hours in a one-month Sprint, and all Scrum Team members attend it." Its purpose is planning for improvements in the process (the way we're working), but it's not the only time we try to improve. Similar to Sprint Planning, Sprint Review, and Daily Scrum, it's an opportunity for inspection and adaptation.

How can a Scrum Master help multiple teams keep their output aligned in a single product?

"The answer should be compatible with the self-organization concept; the Scrum Master or the Product Owner is not supposed to do anything directly in this regard; it's only the responsibility of the Development Team(s) to find their way."

Who makes sure that all developers are doing their tasks during the Sprint?

"The developers take responsibility for doing the tasks (assignment) themselves, and the Development Team ensures that all tasks are done properly. Remember that they are self-organized. When items are "Done", the Product Owner checks them, but this is focused on the item, rather than individuals; all developers are accountable for their outputs"

Which of the following roles can set the definition of "Done"?

"The development organization may have a definition of "Done" composed for all projects, in which case the team will use it as a minimum. Otherwise, the Development Team would be responsible for composing the definition of "Done". Multiple Scrum Teams adhere to the one (same) definition of "Done"" (The Nexus Integration Team is responsible for a definition of "Done" that can be applied to the Integrated Increment developed each Sprint. All Scrum Teams of a Nexus adhere to this definition of "Done) individual Scrum Teams may choose to apply a more stringent definition of "Done" within their own teams, but cannot apply less rigorous criteria than agreed for the Increment."

What should the Product Owner do during the Sprint Retrospective?

"The whole Scrum Team should participate in the Sprint Retrospective to find an improvement to be applied in the next Sprint; including the Product Owner"

What's the main responsibility of testers?

"There are only three roles in Scrum: Product Owner, Scrum Master, and Development Team. It's not allowed to define new roles and the Development Team members should not have any titles; they are all just "developers". It is so because we want all of them to be accountable for everything and to collaborate with each other.Each person has his/her own area of expertise, such as testing, and that person will be more focused on testing tasks, but it doesn't mean that we can call the person "tester""

Which of the following describes the definition of "Done"? (choose 2 answers)

"When a Product Backlog item or an Increment is described as ""Done"", everyone must understand what ""Done"" means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of ""Done"" for the Scrum Team and is used to assess when work is complete on the product Increment."

What two phrases best describe the relationship of the Product Owner and the Development Team?

(1) They collaborate often so the Development Team builds Increments keeping end-user and stakeholder concerns in mind. (2)They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items.

What are two typical activities for a Product Owner in a Sprint?

(1)Collaborate with stakeholders, user communities, and subject matter experts (2)Work with the Development Team on Product Backlog refinement.

What two things should be done if the Product Owner is unavailable?

(1)In a permanent state of unavailability, a new Product Owner needs to be appointed.Development efforts without a Product Owner are not employing Scrum. (2)Within the Sprint, the Development Team makes the best decisions possible to assure progress toward the Sprint Goal, re-aligning with the Product Owner once he/she is available again.

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level or productivity?

* By removing impediments that hinder the Development Team. * By facilitating Development Team decisions.

Choose two responsibilities of a self-organizing Development Team. Choose 2 answers

* Do the work planned in the Sprint Backlog. * Pull Product Backlog items for the Sprint.

During the Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master?

*- Learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum. - Coach the team on why the Daily Scrum is important as an opportunity to update the plan.

Which of the following are true about the Sprint Review?

*- Stakeholders may attend - The Product Owner presents what backlog items are "Done"

Which two activities will a Product Owner engage in during a Sprint?

*Answer questions from the Development Team about items in the current Sprint. *Work with the stakeholders

Which two things should the Development Team do during the first Sprint?

*Develop at least one piece of functionality *Create an increment of potentially releasable software.

What are two responsibilities of testers in a Development Team?

*Everyone in the Development Team is responsible for quality. *Scrum has no "tester" role.

What are two typical activities for a Product Owner in a Sprint?

*Work with the Development Team on Product Backlog refinement. *Collaborate with stakeholders, user communities and product managers.

Rational unified process(RUP)

- 94% of fortune 500 companies use this because they dont know what they want but they are very sure about what they dont want - disciplined approach to assign roles and responsibilities - focused on developing high quality software that meets the needs of its users within a predictable schedule and budget - can be tailored to specific organization or project needs 4 phases 1. Inception scope defined is the project technically and commercial feasible or not 2. elaborate elaborate software architecture have proof of concept prototypes done solutions and components we are going to produce are actually going to work 2gdr 3. construction build, test, verify, validate the software by starting with most abstract version and adding components or capabilities one by one doing iterative and incremental development and test it so that we have something that functions correctly 4. transition we have the product be used by few customers initially and then more no of customers license fee is huge for rational s/w so very costly its usually customized to make ti cheaper

How does Definition of "Done" help the Scrum Team? Select three most applicable items. 1) DoD helps in inspection and adaptation 2) DoD ensures artifact transparency 3) DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning 4) DoD is used to assess when work is complete on the product Increment 5) DoD helps to calculate velocity of the Scrum Team

- DoD is used to assess when work is complete on the product Increment - DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning - DoD ensures artifact transparency

release planning meeting

- High level planning for scrum - decide the milestones - number of sprints required based on the capacity of the team 1. used to create a release plan, which lays out the overall project goals, objectives and backlog of stories. 2. it is then used to create iteration plans for each sprint. 3. purpose - to have everyone in the team understand and commit to delivering the agreed release. 4. A release generally fixes only the target date or target scope, but not both since the time and effort to complete all the work is defined only at a high level

work in progress(WIP)

- Teams should limit user stories accepted into a sprint based on their sustainable velocity. - limits also highlight bottlenecks in a team's delivery pipeline before a situation becomes dire. So in Scrum WIP is limited per unit of time. In Kanban WIP is limited per workflow state.

MVP(minimum viable product)

- a developoment technique to develop product with the smallest possible feature set that addresses the user needs, creates the desired user experience - An MVP has three key characteristics: It has enough value that people are willing to use it or buy it initially It demonstrates enough future benefit to retain early adopters It provides a feedback loop to guide future development strategy for avoiding the development of products that customers do not want. The idea is to rapidly build a minimum set of features that is enough to deploy the product and test key assumptions about customers' interactions with the product.

SWAG(Scientific wild ass guess)

- a rough estimate made by an expert in the field, based on experience and intuition - In the Agile world, Swag is to portfolio items what story points are to backlog items. Swag provides a way to compare the size, time, and effort that it will take to complete a set of features without going through detailed backlog estimating activities. - A unit such as Team Weeks or Ideal Months can be much more appropriate for a Swag than, say, story points

user story mapping

- arranges user stories into a useful model to help understand the functionality of the system, - identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release. - Once user stories are organized as per the functionality, then they are sliced into sprints with a goal to deliver a valuable product increment in a release. - allows you to form a big picture of your backlog. - to understand the backlog better to make right decisions about grooming and prioritization. - promotes silent brainstorming. Horizontally, we can find the title for each grouped functionality; vertically, the main stories/issues related to each group. The functionalities are prioritized from left (more important) to right (less important). Each group will then have the stories prioritized again vertically.

Relative Mass Valuatioin

- biggest advantage of agile is stories are estimated relative to each other, not on the basis of hourly or daily effort. - this technique is most useful when you have large backlog of stories, estimation for each of them becomes daunting -this is a quick way to go thru all of them and estimate relatively Process: 1. firstly write a card for each story and set up a large table so that stories can be moved around easily relative to each other 2. pick any story to start and ask the team to estimate if they find it relatively large medium or small 3. position them at extreme ends acc to their sizes and med one at middle and then keep taking new stories to put them accordingly 4. this way its easy to est 100s of stories in a short while, team gets sense of accomplishment after seeing the scope of work laid out in front of them and estimated in order of effort 5. assign a no to stories like start from 1, until u feel this particular story is at least twice as difficult as first one, then assign 2. The idea is to get a rough point estimate, not a precise order.

Feature

- detailed experience of how your users will do something with your application. - In order to make "something" meaningful, a Feature must include (1) the reasoning behind it, the motivation, "the goal", "the pain to solve" - without it, it's simply impossible to judge Feature's ROI in terms of value versus effort and money. Once this is in place, Feature should include (2) user flows. A user flow might be "User can click on the delete button to delete his record, this will popup [a message] for him to verify first". Usually, a Feature will be built from multiple flows, edge-cases and wording to make sure the grand experience is fully complete. To help relating flow with look & feel, a Feature should (3) include mockups and other accessories. Lastly, (4) business (and even technical) notes should be added to wrap up the experience: URL structure, SEO considerations, user messages user, analytics requirements etc.

SAFe

- framework for applying lean and agile practices at enterprise scale - most important management responsibility remains measuring improvement and ROI - requires from management to choose the solution that best fits their business model & products, and helps shorten the delivery and release phases in order to outperform competitors. -SAFe describes three levels of scale: Team Program Portfolio NINE PRINCIPLES OF SAFE 1. Take an economic view 2. Apply systems thinking 3. Assume variability; preserve options 4. Build incrementally with fast, integrated learning cycles 5. Base milestones on objective evaluation of working systems 6. Visualize and limit WIP, reduce batch sizes and manage queue lengths 7. Apply cadence, synchronize with cross-domain planning 8. Unlock the intrinsic motivation of knowledge workers 9. Decentralize decision-making - at program level - no of scrum teams at proj level working 2gdr for a proj.. - 50-125 people - these people are called agile release train - this is also timboxed in PIs (program increments) which has 5 iterations by default - product manager in form of features in product backlog - train is governed by RTE(release train engineer) who acts as trained scrum master - he is the programmer manager of program level starts with planning meeting all team members gather 2gdr to see features upcoming for PI the teams identify what all they can do.. identifies dependencies and risks with other teams then the teams commits to business users what they can expect in the coming PI so there is a biweekly meeting of scrum masters which is called as scrum of scrum then they have the demo at the end of integrated system to show all teams wrking at same pace we plan only 4 iterations the 5th one is known as IP(Innovation planning) to come up with creative ideas..hackathon n all planning- retrospection and planning for next PI IP is also used to estimate if team is delivery speed at the value stream level there are many ARTs to build bigger system solution mgnt is content authority value stream engineer is coach and guide solution architect ensure good architect is used value stream are on the same PI cadence as the ARTs and planning solution demo portfolio level is differnt yet similar program portfolio mgnt helps dictate direction for all underlying value streams by driving strategic themes from enterprise strategy and allocate budget to value streams for these strategic themes

themes

- groups of related stories. - Often the stories all contribute to a common goal or are related in some obvious way, such as all focusing on a single customer. - However, while some stories in a theme may be dependent on one another, they do not need to encapsulate a specific work flow or be delivered together.

scrum of scrums (SoS)

- important technique in scaling Scrum to large project teams. - allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration. - Imagine a perfectly balanced project comprising seven teams each with seven team members. Each of the seven teams would conduct (simultaneously or sequentially) its own daily scrum meeting. Each team would then designate one person to also attend a scrum of scrums meeting. The decision of who to send should belong to the team. Usually the person chosen should be a technical contributor on the team—a programmer, tester, database administrator, designer, and so on—rather than a product owner or ScrumMaster. - The attendees should change over the course of a typical project. The team should choose its representative based on who will be in the best position to understand and comment on the issues most likely to arise at that time during a project. - For instance, early in a project the issues brought up at the scrum of scrums meeting may center mostly on technical issues or user experience design. Teams may opt to send someone strong in one of those areas to those early meetings. - Later, issues may center around how to collaborate on testing, and so testers will be the more likely participants. - If the number of teams participating is small, it may be acceptable for each team to send two representatives—a technical contributor, as described above, and a ScrumMaster—if the teams desire.

definition of ready

- there are many partially defined items in the product backlog - this causes a lot of frustration in the team solution - teams work with the PO to agree on what defines a "ready" state of a backlog item Story defined and written Story traceable to source document (where appropriate) Acceptance criteria defined Dependencies identified Size estimated by delivery team User experience included (where appropriate) Performance criteria identified (where appropriate) Person who will accept the user story is identified Team has a good idea about how to demo the user story

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?

1. By facilitating Development Team decisions 2. By removing impediments that hinder the Development Team

Vertical slicing

-Agile is very big on the concept of one team. There is no UI, SOA, or data team. There is only one team, focused on delivering a suite of features for the customer. -can be prioritized -no overhead to coordinate activities across multiple teams can be done in 10 ways 1. workflow steps 2. business rules 3. happy/unhappy flow 4. input option/platform 5. data types or parameters 6. operations 7. test scenario/test case 8. roles 9. optimize now vs optimize later 10. browser compatibility

burn up chart

-burn down chart shows work remaining -should be used when work is constant -burn up chart shows work completed -when work is changing -this chart shows all the work(prev+added) -so if SM looks only at the burn down chart he myt think no progress bt looking at burn up he ll knw work is being added so he ll adjust that

scrum task board

-make the sprint backlog visible by putting it on a Scrum task board. -Team members update the task board continuously throughout the sprint; -if someone thinks of a new task, she writes a new card and puts it on the wall. -Either during or before the daily scrum, estimates are changed (up or down), and cards are moved around the board. burn down chart is also shown on it sometimes story to do work in progress to verify done

Horizontal slicing

-projects are broken up roughly along architectural lines. -That is there would be one team for UI, one team for business logic and services (SOA), and another team for data. -adv- good communication and consistency within each slice -disadv-Only when all the layers are hooked up do they offer any value. -individual items do not offer business value -increase bottlenecks, instead of reducing them -cant be prioritized..evrythn is imp -That's why agile is so big on slicing projects vertically.

velocity chart

-used to forecast - work(story points) done in a specific period of time(sprints) - we can compare the actual velocity with the velocity required to meet the deadline

Wich statement best describes Scrum? 1 - A framework within which complex products in complex environments are developped 2 - A defined and preditive process that conforms to the principles of Scientific Managment 3 - A cookbook that defines best pracices for software development 4 - A complete methodology that defines how to develop software

1 - A framework within which complex products in complex environments are developped

What are the two good ways for a Scrum Team to ensure security concerns are satisfied? 1 - Add security concerns in the Definition of done 2 - Delegate the work to the concerned department 3 - Add a sprint to specifically resolve of security concerns 4 - Have the Scrum Team create Product Backlog items for each concern 5 - Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.

1 - Add security concerns in the Definition of done 4 - Have the Scrum Team create Product Backlog items for each concern

Wich of the following are true about the length of the Sprint? 1 - All Sprint must be 1 month or less 2 - The length of the Sprint should be proportionnal to the work that is done in between Sprint 3 - Sprint length is determinded during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, does not including time for any testing 4 - Sprint length is determined durint Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint 5 - It is best to have Sprints of consistent length throughout a development effort

1 - All Sprint must be 1 month or less 5 - It is best to have Sprints of consistent length throughout a development effort

Select two ways in wich technical debt impacts transparency? 1 - As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways 2 - When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the increment 3 - It leads to false assumptions about the current state of the system, specifically of an increment being releasable at the end of a sprint 4 - It enhanced transparency for the Product Owner as a Debelopment Team is not allowed to do additional feature development in a Sprint as long as there is technical debt

1 - As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways 3 - It leads to false assumptions about the current state of the system, specifically of an increment being releasable at the end of a sprint

You are the Scrum Master on a newly formed Scrum Team. Which two of the following activities would probably help the team in starting up? 1 - Ask the Product Owner to discuss the product, its vision, history, goals, and context, as well as answer questions 2 - Have the development managers for each Development Team member introduce their direct reports and go over their responsabilities on the Scrum Team 3 - Ensure the team understands they need a definition of "Done" 4 - Ensure the Scrum Team members have compatible personalities 5 - Introduce a bonus system for the top performers in the team

1 - Ask the Product Owner to discuss the product, its vision, history, goals, and context, as well as answer questions 3 - Ensure the team understands they need a definition of "Done"

Which two ways of creating Development Teams are consistent with Scrum's values 1 - Bring all the developpers together and let them self-organize into Development Teams 2 - Managers personnaly re-assign current subordinates to new teams 3 - The Chief Product Owner determines the new team structure and assignments 4 - Existing teams propose how they would like to go about organizing into the new structure 5 - Managers collaborate to assign individuals to specific teams

1 - Bring all the developpers together and let them self-organize into Development Teams 4 - Existing teams propose how they would like to go about organizing into the new structure

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity? 1 - By facilitating Development Team decisions 2 - By ensuring the meeting start and end at the proper time 3 - By removing impediments that hinder the Development Team 4 - By keeping high value features high in the Product Backlog

1 - By facilitating Development Team decisions 3 - By removing impediments that hinder the Development Team

What three ways Scrum promote self-organization?

1. By specifying a lightweight framework: three roles, five events, and three artifacts. 2. By removing titles for the Development Team members. Everyone is equal, and there is no hierarchy within the Development Team. 3. By empowering the Development Team and determining the best way to accomplish its work.

The Product Owner is not collaborating with the Development Teamduring the sprint. What are the two valuable actions for a Scrum Master to take? 1 - Coach the Product Owner in the values of Scrum and incremental delivey 2 - Stop the Sprint, send the Product Owner to a course and restart 3 - Inform the Product Owner's functional manager 4 - Nominate a prowy Product Owner 5 - Bring up the problem in the Sprint Retrospective

1 - Coach the Product Owner in the values of Scrum and incremental delivey 5 - Bring up the problem in the Sprint Retrospective

Which two things should the Development Team do during the first sprint? 1 - Create an increment of potentially releasable software 2 - Analyse, describe, and document the requirements for the subsequent Sprints 3 - Make up a plan for the rest of the project 4 - Analyse, design and describe the complete architecture and infrastructure 5 - Develop at least one piece of functionnality

1 - Create an increment of potentially releasable software 5 - Develop at least one piece of functionnality

What two techniques could the Scrum Maser use when the Scrum Team gets caught in an internal disagreement about which development techniques to apply? 1 - Involve the complete Development Team 2 - Send every team member to he company's HR departement to express their concerns 3 - Use coaching techniques, such as, open questions and active listening 4 - Ask an internal technical specialist to make the decision

1 - Involve the complete Development Team 3 - Use coaching techniques, such as, open questions and active listening

Choose two responsibilities of a self-organizing Development Team. Choose 2 answers. 1 - Pull product Backlog items for the sprint 2 - Do the work planned in he sprint backlog 3 - Reorder the product backlog 4 - Increase velocity 5 - Report daily progress to the stakeholders

1 - Pull product Backlog items for the sprint 4 - Increase velocity

Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (3 best answers) 1 - Respect 2 - Economic value added 3 - Focus 4 - Courage 5 - Earned value

1 - Respect 3 - Focus 4 - Courage

Which Three of the following are feedback loops in Scrum? 1 - Sprint Retrospective 2 - Refinement meeting 3 - Daily Scrum 4 - Release Planning 5 - Sprint Review

1 - Sprint Retrospective 3 - Daily Scrum 5 - Sprint Review

What two factors are best considered when establishing the Sprint length? 1 - The level of uncertainty over the technology to be used 2 - The frequency at which team formation can be changed 3 - The organization has mandated similar lenfth sprints 4 - The risk of being disconnected from the stakeholders

1 - The level of uncertainty over the technology to be used 4 - The risk of being disconnected from the stakeholders

What is accountability of the Product Owner during sprint 0? 1 - There is no such thing as Sprint 0 2 - Determine the compositon of the Development Team so they have the capacity to deliver forecast 3 - Make the complet project plan to commit date, budget and scope to the stakholders 4 - Gathering, elicting and analysing the requirements that will be inserted into product backlog 5 - Make sure enough Product Backlog items are refined to fill the first 3 sprints

1 - There is no such thing as Sprint 0

When a sprint be abnormally cancelled? 1 - When the Sprint becomes obsolete 2 - When the sales department has an important new opportunity 3 - When the development teams feel that the work is too hard 4 - When it becomes clear that not everything will be finished by the end of the sprint

1 - When the Sprint becomes obsolete

Who participates in the Sprint Review? Select all applicable variants. 1) The Scrum Master 2) The Development Team 3) The Product Owner 4) The Key Stakeholders 5) The Organization CEO

1) The Scrum Master 2) The Development Team 3) The Product Owner 4) The Key Stakeholders During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.

What are two good ways for a Scrum Team to ensure security concerns are satisfied?

1. Add security concerns to the definition of "Done" 2. Have the Scrum Team create Product Backlog item for each concern

Where are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

1. Add them to the Product Backlog and keep the Product Owner posted on the expected effort. 2. Add them to the definition of Done so the work is taken care of every Sprint.

What are two good ways for the Development Team to make non-functional requirements visible?

1. Add them to the definition of "Done" so the work is taken care of every Sprint. 2. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

A Scrum Master is keeping a list of open impediments, but it is growing and he/she has been able to resolve only a small portion of the impediments. Which three techniques would be most helpful in this situation?

1. Alerting management to the impediments and their impact 2. Prioritizing the list and working on them in order 3. Consulting with the Development team

Which of the following are true about the length of the Sprint

1. All Sprints must be 1 month or less 2. It is best to have Sprints of consistent length throughout a development effort

One of the Scrum events is the Daily Scrum. What are two outcomes of the Daily Scrum?

1. An update of the impediments for the Scrum Master to take care of 2. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal

You are the Scrum Master on a newly formed Scrum Team. Which three of the following activities would probably help the team starting up

1. Ask the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions. 2. Ensure the team understand they need a definition of "Done" 3. Have Scrum Team members introduce themselves to each other and give a brief background of their skills and work history

The Product Owner is not collaborating with the Development Team during the Sprint. What are two valuable actions for a Scrum Master to take?

1. Bring up the problem in the Sprint Retrospective. 2. Coach the Product Owner in the values of Scrum and incremental delivery

During a Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursday. Which two are the most appropriate responses for the Scrum Master?

1. Coach the team on why the Daily Scrum is important as an opportunity to update the plan 2. Learn why the Development Team wants this and work with them to improve the outcome of the daily Scrum

1. Consulting with the Development Team. 2. Prioritizing the list and working on them in order. 3. Alerting management to the impediments and their impact.

Sprint backlog

1. Contains committed PBIs negotiated between the team and the PO 2. has an end date 3. has committed backlog items representing the what and sprint tasks are identified(not started, in progress, completed) representing the how - Team will discover additional tasks needed to meet the fixed scope commitment during Sprint execution - Visible to the team - Referenced during the Daily Scrum Meeting

Which two things should the Development Team do during the first Sprint? Choose 2 answers.

1. Create an increment of potentially releasable software 2. Develop at least on piece of functionality

Scrum Development Team

1. Cross-functional (e.g., includes members with testing skills, and often others not traditionally called developers: business analysts, domain experts, etc.) 2. Self-organizing / self-managing, without externally assigned roles 3. Negotiates commitments with the Product Owner, one Sprint at a time 4. Has autonomy regarding how to reach commitments 5. Intensely collaborative 6. Most successful when located in one team room, particularly for the first few Sprints 7. Most successful with long-term, full-time membership. Scrum moves work to a flexible learning team and avoids moving people or splitting them between teams. 8. 7 ± 2 members 9. Has a leadership role

Which three of the following are feedback loops in Scrum?

1. Daily Scrum 2. Sprint Retrospective 3. Sprint Review

Which events are time-boxed according to the Scrum Guide?

1. Daily Scrum. 2. The Sprint. 3. Sprint Review.

Which are NOT appropriate topics for discussion in a Sprint Retrospective? Choose 2 answers

1. Definition of "Done". 2. Sprint Backlog for the next Sprint.

Which two things does the Development Team do during the first Sprint?

1. Deliver an increment of potentially releasable software. 2. Develop and deliver at least one piece of functionality.

The definitions of "Done" is used to:

1. Describe the work that must be done before the Sprint is hallowed to end 2. Increase transparency

Which two things should the Development Team do during the first Sprint? (Choose two.)

1. Develop at least one piece of functionality. 2. Create an increment of potentially releasable software.

feature driven development(FDD)

1. Develop overall model 2. Build a features list 3. Plan by features 4. Design by features 5. Build by features

Which of the below are roles on a Scrum Team?

1. Development Team 2. Product Owner 3. Scrum Master

challenges for transition to scrum agile

1. Difficult to understand the terminologies used in Agile 2. Fast paced environment leads to, inaccurate estimates and improper requirement documents sometimes 3. For off-shore teams, communication and co-ordination can be a big challenge 4. Learning and using the Agile tracking tool can become a challenge for team 5. Due to improper documentation, it becomes a challenge for QA team to understand the requirements correctly 6. Ensuring the tasks allocation to all the team members equally 7. Prioritization of tasks, based on the dependency 8. Inaccurate estimates can leads to burn-down of engineers 9. Long and frequent meetings due to less documentation. 10. The engineers who worked in Waterfall model earlier take it as a wastage of time and they start skipping the meetings 11. Frequent changes in the requirements may lead to frustration to the engineers

A Development Team pulled a Product Backlog item into the Sprint and worked on it. However, it does not meet their definition of "Done" by the end of the Sprint. What three things should happen with the incomplete Product Backlog item?

1. Do not include the item in the increment this Sprint. 2. Do not show it in the Sprint Review. 3. Re-estimate it and return it to the Product Backlog for the Product Owner to decide what to do with it.

Choose two responsibilities of self-organizing Development Team

1. Do the work planned in the Spring Backlog 2. Increase Velocity 3. Pull Product Backlog Items for the Sprint

Choose three responsibilities of a self-organizing Development Team. Choose three answers

1. Do the work planned in the Sprint Backlog 2. Increase Velocity 3. Pull product backlog items for the spring

What are two responsibilities of testers in a Development Team? (Choose two.)

1. Everyone in the Development Team is responsible for quality. 2. Scrum has no tester role.

Which two ways of creating Development Teams are consistent with Scrum's values? (Choose two.)

1. Existing teams propose how they would like to go about organizing into the new structure. 2. Bring all the developers together and let them self-organize into Development Teams.

During the Sprint, the Scrum Master's role is to do which two of the following:

1. Facilitate inspection and adaptation opportunities as requested or needed 2. Remove impediments.

In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn't figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however.Which of the following two actions should the Scrum Master support? (Choose two.

1. Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint. 2. Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order ProductBacklog items. Because of this, the Development Team couldn't figure out how many Product Backlog items it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however.Which of the following two actions should the Scrum Master support? (Choose two.)

In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn't figure out how much functionality it could forecast for the upcoming Sprint. They were able to agree on a Sprint Goal, however. Which of the following two actions should the Scrum Master support?

1. Forecast the most likely Product Backlog to meet the goal and create Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint 2. Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

The definition of "Done" is used to:

1. Guide the Development Team on how many Product Backlog items to select for the Sprint. 2. Create a shared understanding of when work is complete. 3. Increase transparency.

You are the Scrum Master on a newly formed Scrum Team. Which three of the following activities would probably help the team in starting up? (Choose three.)

1. Have the Scrum Team members introduce themselves to each other and give a brief background of their skills and work history. 2. Ensure the team understands they need a definition of Done. 3. Ask the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions.

Which two things are appropriate for a Scrum Master to do if the Development Team doesn't have the engineering tools and infrastructure to completely finish each selected Product Backlog

1. Have the Team define "done" and do the same work for all Product Backlog items it selects. 2. Have the Team improve its skills, tools, and infrastructure over time and adjust the definition of done; accordingly.

Which two things are appropriate for a Scrum Master to do if the Development Team doesn't have the engineering tools and infrastructure to completely finish each selected Product Backlog item?

1. Have the development team establish a definition of done that is actually possible to achieve given current circumstances 2. coach the development team to improve its skills, tools, and infrastructure over time and adjust the definition of done accordingly

What are three benefits of self-organization?

1. Increased self-accountability 2. Increased commitment 3. Increased creativity

Sprint Burn-down Chart

1. Indicates total remaining team task hours within one Sprint 2. Re-estimated daily, thus may go up before going down 3. Intended to facilitate team self-organization 4. Fancy variations, such as itemizing by point person or adding trend lines, tend to reduce effectiveness at encouraging collaboration 5. Seemed like a good idea in the early days of Scrum, but in practice has often been misused as a management report, inviting intervention. The ScrumMaster should discontinue use of this chart if it becomes an impediment to team self-organization.

A Scrum Team has been working on a product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog. However, he is unsure about his responsibilities. Which two activities are part of the Product Owner role according to Scrum?

1. Interacting with stakeholders 2. Providing the Development Team with detailed specification

What three techniques should the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which development techniques to apply?

1. Involve the complete team. 2. Use coaching techniques like open questions and active listening. 3. Consult with team members individually, carefully listening.

Which two statements explain why the definition of "Done" is important to the Product Owner?

1. It assures the Increment reviewed at the Sprint review is usable so the Product Owner may choose to release it. 2. It creates transparency regarding progress within the Scrum Team.

A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items "Done" by the end of the Sprint. Which three phrases describe the purpose of a definition of "Done"

1. It creates transparency over the work inspected at the Sprint Review. 2. It defines what it takes for an increment to be ready for release. 3. It guides the Development Team in creating a forecast at the Sprint Planning.

A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items Done by the end of the Sprint. Which three phrases best describe the purpose of a definition of Done? (Choose three.)

1. It creates transparency over the work inspected at the Sprint Review. 2. It trucks the percent completeness of a Product Backlog item. 3. It defines what it takes for an Increment to be ready for release.

A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items "Done" by the end of the Sprint. Which three phrases best describe the purpose of a definition of "Done"? Choose 3 answers

1. It creates transparency over the work inspected at the Sprint Review. 3. It defines what it takes for an increment to be ready for release. 3. It guides the Development Team in creating a forecast at the Sprint Planning.

Which of the following are true about the length of the Sprint? (Choose two.)

1. It is best to have Sprints of consistent length throughout a development effort. 2. All Sprints must be 1 month or less.

Which are properties Daily Scrum? Choose 2 answers.

1. It is fifteen (15) minutes or less in duration 2. Its location and time should remain constant

Select two ways in which technical debt impacts transparency. (Choose two.)

1. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint. 2. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.

Which two are properties of the Daily Scrum?

1. Its location and time should remain constant 2. It's fifteen minutes or less in duration

What are two guidelines a Scrum Master would use to divide a group of 100 people into multiple Development Teams?

1. Let the Development Teams decide. 2. Ask the developers to divide themselves into teams.

prioritization techniques

1. MOSCOW M - MUST have this. S - SHOULD have this if at all possible. C - COULD have this if it does not effect anything else. W - WON'T have this time but would like in the future. Each requirement will have the priority which would be tagged to MSCW. "M" being the highest and "W" being the lowest. 2. Business Value based In this case, each requirement carries a business value it could potentially generate to the company. The business value would be decided either by the Product Owner or the Product owner team. The requirement with highest business value is implemented during earlier releases . 3. Technology risk based In this method, requirements are prioritized based on the risk associated in implementing it. The risk is typically based on the technology. The requirement with highest technology risk is implemented during the earlier iterations. 4. Kano model In this method, the requirements are prioritized based on the customer preferences. Attractive Basic Performance Indifferent Reverse 5. Walking skeleton In this method, the requirements are selected such that minimal carefully selected end to end features are built within a short span of time. 6. Validated Learning In this method, features are chosen based on the highest market risk i.e. some thing that is not experimented yet. Release it to the market, get the feedback and apply the learning onto the new feature

Which two (2) things does the Development Team not do during the first Sprint?

1. Nail down the complete architecture and infrastructure. 2. Develop a plan for the rest of the project.

A Development Team is required to deliver a done increment by the end of a Sprint. Select two statements that explain what Done means. (Choose two.)

1. No work left from the definition of Done. 2. All work to create software that is ready to be released to end users.

Product backlog

1. One dimensional forced ranked list of customer centric features prioritized by the product owner 2. Contains everything team might ever do 3. Anyone can add anything throughout project 4. PO will constantly re prioritize it and SM will make it visible 5. Doesnt contain tasks 6. Contains product backlog items(PBIs) 7. gets larger as development continues from sprint to sprint because every sprint review demo prompts more and different requirements 8. Items at top are more granular than items at bottom

The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)

1. Opportunities to insect and adapt the Sprint Backlog are lost. 2. Impediments are raised and resolved more slowly. 3. The Product Owner cannot accurately report progress to the stakeholders.

estimation techniques

1. Planning Poker 2. T shirt sizes 3. Relative Mass Valuation 4. Bucket System 5. Dot Voting 5. Numeric Sizing (1 through 10) 6. Fibonacci Sequence (1, 2, 3, 5, 8, 13, 21, 34, etc.) 7. Dog Breeds (Chihuahua,.........,Great Dane)

A scrum master is keeping a list of open impediments, but it is growing and he/she has been able to resolve only a small portion of the impediments. Which three techniques would be most helpful in this situation?

1. Prioritize the list and work on them in order 2. Alert management to the impediments and their impact 3. Consult with the development team

Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces). What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)

1. Productivity may suffer when making this kind of move. 2. Getting support from the business side first helps. 3. Feature teams have less communication overhead.

Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)

1. Respect 2. Focus 3. Courage

types of impediments

1. Scrum Master owned 2. Organizational 3. Team owned Psychological Impediments: geographically distributed (have formal meetings with timelines set, time allocation set and emails and reminders), presence of people who conduct appraisals (keep them away at the retrospective meeting cuz the core of scrum is self management and collaboration) (invisible gun effect) and people jumping to conclusions.(orid technique) Organization impediment: An example of an organizational impediment would be something like, "I have a person on my team who is constantly being asked by other managers to take on other duties. As a result, he are never able to properly commit to and focus on the work for this project " So I would work with managers to remove this impediment either by: Having the person replaced with someone who had fewer distractions Having the other managers take those distracting items off his list of things to do. Scrum master level impediment: "The team has been trying to have a meeting with the tech lead from another team for 4 days now. He is hard to catch up with and his calendar is nearly full." As a scrum master I would coordinate/facilitate a face to face meeting so that the team is not consumed with administrivia. Team Level impediment: "We need to test this feature but we don't have enough testers." As a Scrum master I would guide the team to solving this themselves by "swarming" so that everyone becomes a tester so that we could get items to done.

Select three incorrect, untrue, or misleading statements about Scrum?

1. Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment. 2. Scrum is like traditional processes but with self-organization to replace Project Managers. 3. Scrum is a framework that eliminates complexity.

agile 4 principles

1. interaction and integration over process and tools 2. wrking s/w over documentaiton 3. customer collaboration over contract negotiation 4. responding to changes over plan

Product Owner

1. Single person responsible for maximizing the return on investment (ROI) of the development effort 2. Responsible for product vision 3. Constantly re-prioritizes the Product Backlog, adjusting any long-term expectations such as release plans 4. Final arbiter of requirements questions 5. Accepts or rejects each product increment 6. Decides whether to ship 7. Decides whether to continue development 8. Considers stakeholder interests 9. May contribute as a team member 10. Has a leadership role

Sprint Task

1. Specifies how to achieve the PBI's what 2. Requires one day or less of work 3. Remaining effort is re-estimated daily, typically in hours 4. During Sprint Execution, a point person may volunteer to be primarily responsible for a task 5. Owned by the entire team; collaboration is expected SMART Specific Measurable Attainable Relevant Time Bound

Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose 2 answers)

1. Spring Backlog for the next Sprint 2. The value of work currently in the Product Backlog

Baiscally 4 meetings

1. Sprint Planning meeting 2. Daily Scrum -------Backlog Refinement Meeting------- 3. Sprint Review Meeting 4. Sprint Retrospective Meeting

As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? (Choose two.)

1. The Development Team ensures that the Product Owner is aware, starts the Sprint, and monitors progress. 2. Remove or change selected Product Backlog items.

Which of the following are true about the Product Owner role?

1. The Product Owner is one person. 2. The Product Owner is accountable for ordering the Product Backlog. 3. The Product Owner can be influenced by committee.

What two factors are best considered when establishing the Sprint length? (Choose two.)

1. The level of uncertainty over the technology to be used. 2. The risk of being disconnected from the stakeholders.

You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select Two conditions you should strive for in this scenario.

1. The product has one Product Backlog 2. There should be only one Product Owner.

Which two of the following are true about the Scrum Master role?

1. The scrum master teaches the development team to keep the scrum meetings to their timebox 2. the scrum master helps those outside the team interact with the scrum team

You have just been hired by a company new to Scrum. Your management has assigned you to be the Scrum Master of six new Scrum Teams. These teams will build one product. Select two conditions you should strive for in this scenario:

1. There should be only one Product Owner. 2. The product has one Product Backlog.

What two phrases best describe the relationship of the Product Owner and the Development Team?

1. They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items. 2. They collaborate often so the Development Team builds Increments keeping end-user and stakeholder concerns in mind.

Self-organization works best when there are goals and boundaries. Select two requirements from the Scrum framework that are key for a Scrum Master to teach teams to help them self-organize:

1. Time-boxing events to manage risks 2. Creating a releasable Increment by the end of each Sprint

Product / Release Burndown Chart

1. Tracks the remaining Product Backlog effort from one Sprint to the next 2. May use relative units such as Story Points for Y axis 3. Depicts historical trends to adjust forecasts

scrum 3 pillars

1. Transparency Artifacts Meetings Information Radiators 2. Inspection Scrumboard and information radiators approval from PO, stakeholders in review meeting 3. Adaption Change requests Retrospective meetings Constant risk identification

3 types of user stories or items in product backlog

1. User Stories Brief simple statements of a desired product function from an end user's perspective. As a <End User Role>, I want to <desired action>, so that <desired benefit>. As a Personal Checking Account Holder, I want to register for an online banking account, so that I can access my account details online. As a Registered Online Banking Customer, I want to view a list of all my accounts, so that I can quickly see my current balances. 2. Non-User Stories Brief simple statements of foundational or infrastructure needed in order to deliver User Stories in the Product Backlog. As a <Team Role>, I want to <desired action>, so that <desired benefit>. As a Developer, I want to configure our assigned development region, so that we can begin developing User Stories in our backlog. As a Tester, I want to prepare a test lab, so that we have representation of all device types & operating systems we need to execute tests on. 3. Spikes Brief simple statements of research that is needed in order to move forward with other items in the Product Backlog. As a <Team Role>, I want to <desired action>, so that <desired benefit>. As a Developer, I want to research the latest security protocols, so that we feel confident we selected the best method for securing our customer's financial data. As a Business Analyst, I want to research the state specific business rules for handling white goods taxes, so that our customer's are charged appropriately for the items they purchase.

2 types of sprint planning

1. Velocity driven 2. Commitment driven

Which three questions are answered by alt Development Team members at Dally Scrum?

1. What work did I do yesterday to help the team achieve its goal 2.What work am I going to do today to help the team achieve its goal 3. What impediments are in my or in the way of the team

61 Which two activities will Product Ownwers engage in during a Sprint? Choose 2 answers.

1. Work with the stakeholders 2. Answer questions from the Development Team about items in the current Sprint

1. You cannot do Scrum without feature teams. 2. Getting support from the business side first helps. 3. Productivity may suffer when making this kind of move.

Scrum

1. light weight agile project management framework for software development. follows incremental & iterative approach 2. using one or more cross-functional, self-organizing teams. 3. provides a structure of 1. roles, 2. meetings, 3. artifacts. 4. uses fixed-length iterations, called Sprints, 15 days upto 30 5. teams attempt to build a potentially shippable (properly tested) product increment every iteration. - an alter to waterfall model 6. ability to develop a subset of high-value features first, incorporating feedback sooner. 7. new approach to increase speed and flexibility of development 8. key principle is its recognition that customers mind can change anytime during a project 9. usually associated with object-oriented software development. 10. useful for complex work involving knowledge creation and collaboration, such as new product development.

Planning Poker

1. makes sure that everybody participates and that every voice is heard. 2. each team member is given a set of cards with numbers on them. The numbers are usually ordered from 0 to 21 using the Fibonacci sequence: 0, 1, 2, 3, 5, 8, 13, and 21. 3. each story is read aloud, every1 asked to hold up their card showing level of effort they believe it requires for team 4. initially scattered ans but later they all realise 5. once all votes are in, highest n lowest estimates give explanation 6. frequently, experts with detailed knowledge tell rest of team why certain story is more diff or easy than they think of it cz of unexpected requirements 7. through this process team members inc their knowledge base regarding req, clarity 8. stories with more than 20 points should be broken down

Scrum master

1. no management authority, no project manager role(project management is done by team and PO) 2. Facilitates the Scrum process 3. protects the team from distractions & interruptions, Helps resolve impediments 4. teaches the team how to use scrum 5. Promotes improved engineering practices 6. provides visibility 7. enforces time boxes 8. Creates an environment conducive to team self-organization 9. Captures empirical data to adjust forecasts 10. Has a leadership role

types of velocity

1. planned - 2 types velocity based- total no of story points/ tot no of sprints capacity based - abilility of a particular person in terms of man hours, eg sm1 myt b a shared resource .. also used to determine no of sprints 2. initial - estimation for 1st sprint, initially it ll b high..after 2-3 sprint they cm to knw..usually its 1/3rd of planned velocity 3. optimal- avg of all previous sprint velocities 4. current velocity - velocity of current sprint

scrum artifacts

1. product backlog 2. sprint backlog 3. velocity chart 4. burn down/ burn up chart 5. Story 6. Task Boards PBI Sprint task Sprint bd chart product bd chart

Extreme Programming

1. shorter iterations of 1-2 weeks rather than 2-4 2. team can change features as long as they havent started working on that features, unlike sprint 3. customer decides the the order and team executes it in same manner, unlike PO doing prioritization and team executing it in wtev order they want in sprint 4. emphasizes more on engineering practices like TDD, pair programming unlike scrum where teams are self organizing and cross functional to decide wtev fits them - it has freq releases in short development cycles - intended to improve productivity and introduce checkpoints where new cust requirements can be adopted feature: pair programming extensive code review unit testing integration testing user stories spike solutions simplicity and clarity in code expect changes in req freq commn with customers disadv good only for small to med projs code centric-more focus on code than desgin..s/w dev requires gud design no focus on quality

T shirt sizes

1. using numbers for estimation is quite difficult sometimes, sometimes over or under estimation happens cz of nos 2. extra-small, small, medium, large, extra-large, or double extra-large 3. implied precision of numerical score removed 4. helps team come out of their analytical thought processes and into a more flexible, relative mindset. disadvantage: 1. non-numerical scales are generally less granular. While that can speed up the voting process by reducing the number of options, it may also reduce the accuracy of velocity estimates. 2. the ability to compare stories with each other can be a little bit more complicated, since there is no clear mathematical relationship between a medium and an extra-small. 3. requires extra effort on the part of the person coordinating the agile process. The T-shirt sizes need to be converted to numerical values for the sake of tracking effort over time and charting an estimated velocity for the team. so useful only for teams who are just starting with agile, later numerical techniques should be used

Product Backlog Items (PBI)

1. written in form of use cases, user stories or epics 2. Specifies the what more than the how of a customer-centric feature 4. Has a product-wide definition of done to prevent technical debt 5. May have item-specific acceptance criteria 6. Effort is estimated by the team, ideally in relative units (e.g., story points) 7. Effort is roughly 2-3 people 2-3 days, or smaller for advanced teams should have these qualities(INVEST): 1. I Independent-The PBI should be self-contained, in a way that there is no inherent dependency on another PBI. 2. N Negotiable-PBIs, up until they are part of an iteration, can always be changed and rewritten. 3. V Valuable-A PBI must deliver value to the stakeholders. 4. E Estimable-You must always be able to estimate the size of a PBI. 5. S Small-PBIs should not be so big as to become impossible to plan/task/prioritize with a certain level of certainty. 6. T Testable-The PBI or its related description must provide the necessary information to make test development possible.

The time-box for a Daily Scrum is?

15 minutes

The time-box for a Daily Scrum is?

15 minutes.

How often should Development Team membership change? 1 - Every Sprint to promote shared learning 2 - As needed, while taking into account a short term reduction in productivity 3 - As needed, with no special allowance for changes in productivity 4 - Never, because it reduces productivity

2 - As needed, while taking into account a short term reduction in productivity

When does the Sprint begin? 1 - The Monday following the Sprint Review 2 - Immediately following the next sprint planning 3 - When the Product Owner is ready 4 - Immediately after the conclusion of the previous Sprint

4 - Immediately after the conclusion of the previous Sprint

What enhances the transparency of an increment? 1 - Reporting Sprint progress to the stakeholders daily 2 - Doing all work needed to meet the definition of "Done" 3 - Keeping track of and estimating all undone work to be completed in a separate Sprint 4 - Updating Sprint tasks properly in the elecronic tracking pool

2 - Doing all work needed to meet the definition of "Done"

During a Sprint Retrospective, for what is the Scrum Master responsible? 1 - Acting as scribe to capture the Development Team's answers 2 - Participating as a Scrum team member and facilitating as requested or needed 3 - Prioritizing the resulting actions items 4 - Summarizing and reporting the discussions to management

2 - Participating as a Scrum team member and facilitating as requested or needed

As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? Choose 2 answers 1 - Cancel the sprint 2 - The Development Team ensures that the Product Owner is aware, starts the sprint, and monitor progress 3 - The Development Teams works overtime during the Sprint 4 - Remove or change selected Product Backlog items 5 - Recruit additional Development Team members before the work begin

2 - The Development Team ensures that the Product Owner is aware, starts the sprint, and monitor progress 4 - Remove or change selected Product Backlog items

What is recommended size of a Development Team? 1 - At least 7 2 - 7 plus or minus 3 3 - 3 to 9 4 - 9

3 - 3 to 9

When many Development Teams are working on a single product, what best describes the definition of "done?" 1 - Each Development Team defines and uses its own. The difference are discussed and reconciled during a hardening Sprint 2 - It depends 3 - All Development Teams must have a definition of "Done" that makes their combined work potentially released 4 - Each Development Team uses its own but must make their definition clear to all other teams so the difference are known

3 - All Development Teams must have a definition of "Done" that makes their combined work potentially released

At the end of a Sprint of Product Backlog item worked on during the Sprint does not meet the definition of "done". What two things should happen with the undone Product Backlog item? 1 - Review the item, add the "Done" part of the estimate to the velocity and create a Story for the remaining work 2 - If the stakeholders agree, the Product Owner can accept it and release it to the users 3 - Put it in the Product Backlog for th eProduct Owner to decide what to do with it 4 - Do not include the item in the increment this sprint

3 - Put it in the Product Backlog for th eProduct Owner to decide what to do with it 4 - Do not include the item in the increment this sprint

What are two responsibilities of testers in a Development Team? 1 - Verifying the work of programmers 2 - Finding bugs 3 - Scrum has no tester role 4 - Tracking quality metrics 5 - Everyone in the Development Team is responsible for quality

3 - Scrum has no tester role 5 - Everyone in the Development Team is responsible for quality

How is management external of the Scrum Team involved in the Daily Scrum? 1 - The Scrum Master speaks on their behalf 2 - Management gives an update at the start of each Daily Scrum 3 - The Development Team self-manages and is the only management required at the Daily Scrum 4 - The Product Owner represents their opinion

3 - The Development Team self-manages and is the only management required at the Daily Scrum

You are the Scrum Master for four Scrum Teams working from the same Product Backlog. Several of the developpers come to you complaining that work identified for the upcoming two sprints will require full-time commitment from a technical specialist who is external to the teams. What are two key concern to the Scrum Master to take into account in this situation? 1 - The desire to maintain a stable velocity 2 - The need to have enough work to keep all Development Team members busy 3 - The benefit of Development Teams figuring out a solution for themselves 4 - The ability of the Development Teams to produce integrated increments

3 - The benefit of Development Teams figuring out a solution for themselves 4 - The ability of the Development Teams to produce integrated increments

What is the recommended size for a Development Team (within the Scrum Team)?

3 to 9

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, when must an adjustment be made? 1) After Scrum Master approval 2) As soon as possible to minimize further deviation 3) After clarifying all the details with the Product Owner 4) The deviations should be discussed at the Daily Scrum and then an adjustment must be made

3) After clarifying all the details with the Product Owner If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.

The length of a sprint should be: 1 - Short enough to keep the business risk acceptable to the Product Owner 2 - short enough to be able to synchronize the development work with other business events 3 - No more than one calendar month 4 - All of these answers are correct

4 - All of these answers are correct

When should a sprint goal be created? 1 - A sprint goal is not mandatory in Scrum 2 - It must be established before Sprint Planning in order to begin planning 3 - At any time during a Sprint 4 - During a Sprint Planning 5 - It should have been created in the previous Sprint during Product Backlog refinement

4 - During a Sprint Planning

The Product Owner detemines how many Product Backlog items the Development Team select for a sprint. 1 - True, accordingly to what was committed to the stakholders 2 - False, capacity and commitment are the Project manager's responsbility 3 - True 4 - False 5 - True, but only confirmation by the resource manager that the team has enough capacity 6 - False, the Scrum Master does that

4 - False

What is the main reason for the Scrum Master to be at the Daily Scrum? 1 - To make sure every team answers the three questions 2 - To gather status and progress information o report management 3 - To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down 4 - He or she does not to have to be there; he or she only has to ensure the Development Team has a Daily Scrum

4 - He or she does not to have to be there; he or she only has to ensure the Development Team has a Daily Scrum

The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do? 1 - Add the item to the next Sprint 2 - Add the item to the current Sprint without any adjustments 3 - Add the item to the current Sprint and drop an item of equal size 4 - Inform the Product Owner so he/she can work with the CEO

4 - Inform the Product Owner so he/she can work with the CEO

During the Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master? Choose 2 answers 1 - Have the developpers vote 2 - Acknowledge and support the self-organizing team's decision 3 - Consider the request and decide on which days the Daily Scrum should occur 4 - Learn why the Development Team wants this and work with them to improve the outcome of the daily scrum 5 - Coach then team on why the daily scrum is important as an opportunity to update the plan

4 - Learn why the Development Team wants this and work with them to improve the outcome of the daily scrum 5 - Coach then team on why the daily scrum is important as an opportunity to update the plan

What is the key concern when multiple Development Teams are working from the same Product Backlog? 1 - Making sure there's enough work for everyone on every team 2 - Meeting original scope projections 3 - Maximizing velocity 4 - Minimizing dependencies between teams 5 - Clear definition of requirments

4 - Minimizing dependencies between teams

Five new Scrum Teams have been created to build one product. A few of the developpers on one of the Development Teams ask the Scrum Master how to coordinate their work with the other teams. What should the Scrum Master do? 1 - Visit the five teams each day to inspect that their Sprint Backlogs are aligned 2 - Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidaded plan for the entire Sprint 3 - Teach the Product Owner to work with the lead developpers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint 4 - Teach them that it is their responability to work with the other teams to create an integrated increment

4 - Teach them that it is their responability to work with the other teams to create an integrated increment

The Product Backlog is ordered by: 1 - Size, where the small items are at the top and large items are at the bottom 2 - Items are randomly arranged 3 - Risk, where safer items are at the top, and riskier items are at the bottom 4 - The Product Owner with the most valuable items placed at the top

4 - The Product Owner with the most valuable items placed at the top

For which is the Scrum Master responsible? 1 - Keeping track of resource allocation 2 - Managing the performance of the Scrum Team 3 - The meetings and the objectives that a Scrum Team sets for itself 4 - The Scrum framework being adopted and used properly

4 - The Scrum framework being adopted and used properly

Wich outcome is expected as Scum Team mature? 1 - There is no need for a time-boxed Sprint, since time-boxes are only for new Scrum Teams 2 - A Scrum Master is no longer needed since they are a mature team now 3 - Sprint Reviews will no longuer be needed. 4 - They will improve their definition of "done" to include more stringent criteria 5 - The Sprint Retrospective will grow to be longuer than 4 hours

4 - They will improve their definition of "done" to include more stringent criteria

What is the role of management in Scrum? 1 - To monitor the Development Team's productivity 2 - To continually monitor staffing levels of the Development Team 3 - To identify and remove people that aren't working hard enough 4 - To facilitate the Scrum Teams with insights and resources that help them improve

4 - To facilitate the Scrum Teams with insights and resources that help them improve

When is implementation of a Product Backlog item considered complete? 1 - At the end of the sprint 2 - When all works in the sprint backlog related toi him is finished 3 - When QA reports that the item passes all acceptance area 4 - When the item has no work remaining in order to be potentially released

4 - When the item has no work remaining in order to be potentially released

What is the time-box for the Sprint Review?

4 hours for a monthly Sprint.

The maximum length of the Sprint Review (its time-box) is:

4 hours for a monthly Sprint. For shorter Sprints it is usually shorter.

How many weeks are required to release increment based on the following information:- 240 points release backlog - 3-week per Sprint - 45 points velocity per Sprint?

45 points are velocity for 1 Sprint (3 weeks). It means that velocity for 1 week is 15 points (45/3 = 15)There are 240 points to complete release. 240 points / 15 points (1 week) = 16 weeks. But the duration of Scrum is 3 weeks and the increment will be ready only after the third week of the Sprint. So the correct answer is 18 weeks.

Wich of the following might the Scrum Team discuss during a Sprint rerospective? 1 - Methods of communication 2 - The way the Scrum Team does the Sprint Planning 3 - Skills needed to improve the Development Team's ability to deliver 4 - Its definition of "Done" 5 - All of the above

5 - All of the above

What is included the Sprint Backlog? 1 - User Stories 2 - Tasks 3 - Use Cases 4 - Tests 5 - Any of the above which are a decomposition of the selected Product Backlog items

5 - Any of the above which are a decomposition of the selected Product Backlog items

Who creates a Product Backlog item's estimate? 1 - The Product Owner with input from the Developper Team 2 - The most senior people in the organization, including architects and subject matter experts 3 - The Scrum Master 4 - The Development Team, alone 5 - The Development Team after clarifying requirements with the Product Owner.

5 - The Development Team after clarifying requirements with the Product Owner.

What is the time-box for the Sprint Planning meeting?

8 Hours for a monthly Sprint

What is the time-box for the Sprint Planning meeting?

8 Hours for a monthly Sprint.

The time-box for the Sprint Planning meeting is?

8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.

Which three of the following are timeboxed? a. Daily Scrum b. Release Planning c. Sprint testing d. Sprint Retrospective e. Product Backlog Refinement f. Sprint Planning

A, D, F

A company that is mature is using Scrum, and it also has a PMO. What is the role of that PMO? a. Manage portfolios and programs and facilitate the application of techniques that complement Scrum. b. There's no place for a PMO in such an organization. c. The PMO will be responsible for making higher level decision in the project. d. The PMO should manage and help the Scrum Masters.

At the end of the Sprint, all items are done except for one that is almost done. What should be done with this item? a. Move it back to the Product Backlog. b. It can be added to the Increment if the user acceptance tests are done. c. The Sprint will be extended until we complete the item. d. It can be added to the Increment if the customer accepts it.

Daily Scrums are held at the same time and same place every day. a. True b. False

The Development Team can have a Team Leader to improve communications and collaboration. YoursExpected a. False b. True

The Product Owner is the sole person responsible for managing the Product Backlog, which includes that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.**Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly? A) The Product Owner B) The Development Team C) The Scrum Master D) The Project Manager

The developers forecast that 5 out of 12 items they have in the Sprint Backlog won't be done by the end of the Sprint. What should they do? a. Review the work with the Product Owner to see if any adjustments are required, and keep working. b. Cancel the Sprint. c. Work overtime and try to complete all items. d. Extend the duration of the Sprint, to be able to deliver everything.

The performance of the project should be measured at least... a. Once per Sprint b. Once a week c. Once a day d. Before or after each release

The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done".**How much work must a Development Team do to a Product Backlog item it selects for a Sprint? A) As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done". B) As much as it can fit into the Sprint. C) All development work and at least some testing. D) Analysis, design, programming, testing and documentation.

What do we do with Done items when the Sprint is cancelled? a. They will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them. b. They should be moved back to the Product Backlog, and will be taken care of in future Sprints. c. They should be moved to the next Sprint Backlog.

What does a burn-down chart measure? a. Work remaining across time b. Cost of the project across time c. Work that is done based on the Definition of Done d. The amount of business value delivered to the customer

What does a burn-down chart measure? a. Work remaining across time b. Work that is done based on the Definition of Done c. The amount of business value delivered to the customer d. Cost of the project across time

What does it mean for a Development Team to be cross-functional? a. The team includes not only programmers, but also testers, architects, UI designers, etc. b. The developers work closely with business analysts, architects, and testers external to them. c. The team should collaborate with all functional units. d. Each Development Team member has all the expertise required for creating potentially releasable Increments.

What does it mean for a Development Team to be cross-functional? a. They have all the expertise required for the product, in such a way that they do not need any help from the outside. b. The developers work closely with business analysts, architects, and testers external to them. c. The team should collaborate with all functional units. d. Each Development Team member has all the expertise required for creating potentially releasable Increments.

What happens to the Done Product Backlog items when the Sprint is cancelled? a. They will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them. b. They should be moved back to the Product Backlog, and will be taken care of in future Sprints. c. They should be moved to the next Sprint Backlog.

What type of test should be done during the Sprint? a. Every type of test b. All tests, except for user acceptance tests c. All tests, except for integration tests d. Unit tests

What's the main responsibility of a tester in Scrum? a. There are no testers in Scrum b. Tracking quality metrics c. Finding bugs d. Writing the test scripts as soon as the programmers start working on the code

When is an item in the Sprint Backlog considered complete? a. When it can be part of a potentially releasable Increment b. When the customer approves its completeness c. The item is ready for user acceptance testing d. When user acceptance tests are passed

Which of the following actions may a Scrum Master take in starting up a project? a. Ask the Development Team to discuss and identify the way they are going to develop the product. b. Ensure that a bonus system is in place for the top performance of individuals. c. Ask the development managers to introduce their departments and capabilities. d. Ask the team to work together and prepare a complete Product Backlog.

Which of the following are correct about the length of Sprints? a. All Sprints must be one month or less. b. Sprint length is set during Sprint Planning, and is long enough for programming and testing all items, but not for integrating them. c. Sprint length is set during Sprint Planning, and is long enough to develop all items in the Sprint Backlog. d. Depends on the position of the stars ;)

Which of the following best describes Sprint Planning? a. What can be done and how to do it b. What to do and who will do it c. Who will be in the team this Sprint? d. What was the feedback and how should we adapt the Product Backlog?

When forming multiple Scrum teams, which two of the following are the most important considerations?

All teams should be cross-functional, with optimal size 3 to 9 members. Also, it is very important for teams to avoid dependencies on each other as much as it possible.

Which of the following best describes Sprint Review? a. An inspection of the Increment to collect feedback and see what to do in the next Sprint b. It's a celebration at the end of the Sprint to appreciate the work of the developers. c. A formal meeting to receive approval of the customer for the Increment d. A demo at the end of the Sprint for everyone in the organization to see the Increment.

Which of the following is LEAST likely to be used by a Scrum team? a. WBS, Gantt Chart b. Wiki, online forum c. Digital camera, task board d. Large screen, Planning Poker cards

Which of the following is NOT a feedback loop in Scrum? a. Product Backlog Refinement b. Sprint Planning c. Sprint Review d. Daily Scrum

Which of the following is a benefit of self-organization? a. Increased buy-in b. Increased cross-functionality c. Increased respect d. Increased predictability

Which of the following is required by Scrum? a. Definition of Done b. Story Points c. Test-Driven Development d. Having full-time developers

Which of the following may change during the Sprint? a. Sprint Backlog b. Composition of the team c. Expected quality d. Sprint Goal

Which statement best describes the Product Backlog? a. It may change anytime, and it is never complete. b. Contains only small and clear items. c. Contains all tasks identified by the developers. d. Provides just enough information to enable the developers to design the product.

Which statement explains a benefit of having tests in the Definition of Done? a. Increments would be closer to potentially releasable. b. It defines when the Increment should be released. c. Increments would be more complete.

Who estimates the size of the Product Backlog items? a. The Development Team b. The Scrum Master c. The Product Owner d. The Scrum Team

Who owns the Product Backlog? a. The Product Owner b. The Development Team c. The whole Scrum Team d. The Scrum Master

The Product Backlog is baselined before the first Sprint a. False b. True

A "Baseline" has a specific meaning in project management that may apply to some elements in Scrum. However, Scrum.org interprets it as keeping the subject fixed, and therefore, believes that there are no baselines in Scrum.

How many hours per day should a Development Team member work? a. At a constant pace b. At least 6 ideal man-hours c. As much as needed for realizing the Sprint Backlog items by the end of the Sprint d. Between 6 and 16 hours, depending on the situation

A (a) This is one of the 12 Agile principles.

What is a benefit of having tests in the Definition of Done? a. Increases transparency of the Increments. b. Increments would be more complete. c. It defines when the Increment should be released. d. It makes reporting easier for the Project Manager.

A (a) Without tests, you never know if the integrated output really works, and you can't say if the Increment is what everyone expected it to be.

What does it mean for a Development Team to be cross-functional? a. The team includes not only programmers, but also testers, architects, UI designers, etc. b. Each Development Team member has all the expertise required for creating potentially releasable Increments. c. The team should collaborate with all functional units. d. The developers work closely with business analysts, architects, and testers external to them.

A (a) i.e. all skills needed to create the product. A cross-functional team is one that has all types of expertise that is required to develop the product. Note that this is about the team as a whole, not individual team members.

Scaled Scrum is one that conforms to Scrum and uses more than one team for all Sprints. a. False b. True

A 1. Scaled Scrum conforms to Scrum; i.e. it's compatible with Scrum. 2. It's called Scaled Scrum when there are more than one team; however, it's not necessary to have more than one team in all Sprints; it can be for some of them.

A real self-organizing team doesn't need a Scrum Master a. False b. True

A A Scrum Master doesn't disrupt self-organization; e.g. they "help" by removing impediments.

When the team becomes mature enough in using Scrum, they won't need a Scrum Master anymore. a. False b. True

A A Scrum Master is always needed; at least for removing impediments

When the team becomes mature enough in using Scrum, they won't need a Scrum Master anymore. a. False b. True

A A Scrum Master is always needed; at least for removing impediments.

Scrum does not have a role called "project manager." A) True B) False

A A Scrum Team has a Scrum Master, a Product Owner and a Development Team. As a whole they have all controls needed.

The Scrum Master can also be a member of the Development Team a. True b. False

A A better way of asking is "Can the same person play both the Scrum Master role and a Development Team member role?" One person can have more than one role in Scrum (not recommended, but allowed).

What's the role of the Product Owner during Sprint Retrospective? a. Participate as a Scrum Team member b. Capture requirements for the Product Backlog c. Summarize and report the results of the meeting to stakeholders d. To answer questions of the developers

A All three roles participate in the Sprint Retrospective, and they work together to see how they can improve the way they work in the next Sprint.

What's the role of the Scrum Master during Sprint Retrospective? a. Participate as a Scrum Team member b. They should not participate in this meeting c. To answer questions of the developers d. Summarize and report the results of the meeting to stakeholders

A All three roles participate in the Sprint Retrospective, and they work together to see how they can improve the way they work in the next Sprint.

Adding new developers to the team may cause a short-term decrease in productivity. a. True b. False

A Because established members have to spend time and effort getting new ones to know the solution and the environment and start working.

What is included in the Sprint Backlog?

Any of the above (or others) which are a decomposition of the selected Product Backlog items.

Which statement is correct about the Sprint Backlog? a. It has just enough detail. b. It has all the details. c. It has no detail.

A Both Sprint Backlog and Product Backlog evolve during their lives, and the amount of information grows as time passes. So, at each point in time, they don't have as much detail as they will have in the future (also imaginary future). On the other hand, we never add all the details there. For example, it's common to say that a User Story doesn't provide all the information, but is an excuse for people involved in the project to have communications around a certain topic. The details are in those communications, and are not completely captured in the backlog.

Who can attend the Daily Scrum meeting? a. Anyone b. The Development Team and the Scrum Master c. The whole Scrum Team d. The Development Team

A Daily Scrum is for the developers; only they "participate" (=talk). Others can "attend" (=watch)

Who can attend the Daily Scrum meeting? a. Anyone b. The Development Team c. The Development Team and the Product Owner d. The whole Scrum Team

A Daily Scrum is for the developers; only they "participate" (=talk). Others can "attend" (=watch).

Which of the following is LEAST likely to be used by a Scrum team? a. WBS, Gantt Chart b. Digital camera, task board c. Large screen, Planning Poker cards d. Wiki, online forum

A Did you notice the word "least" in the question? WBS and Gantt Chart are mainly used in planning predictive projects rather than adaptive (Agile) ones.

Which of the following is LEAST likely to be used by a Scrum team? a. WBS, Gantt Chart b. Wiki, online forum c. Digital camera, task board d. Large screen, Planning Poker cards

A Did you notice the word "least" in the question? WBS and Gantt Chart are mainly used in planning predictive projects rather than adaptive (Agile) ones.

Which element is NOT an attribute of Product Backlog items? a. Owner b. Description c. Value d. Estimate

A Did you notice the word "not" in the question? There are 3 pieces of information in each Product Backlog item: the description (in the form of a User Story, or otherwise), value, and estimate (i.e. estimated size). The ownership of items is shared, therefore, there's no need to record it in the item.

Which element is NOT an attribute of Product Backlog items? a. Owner b. Value c. Estimate d. Description

Sprint Review is NOT a formal meeting. a. True b. False

A Did you notice the word "not" in the statement? It's not a formal meeting, in the sense that you and the customer won't work on approval/acceptance of the product and exchanging signatures (that would block feedback generation). This may be confusing, because on the other hand, Sprint Review (and other events) are considered "formal opportunities for inspecting and adapting". The word "formal" has been used for two different meanings in the exam, the former is what we have in this question, and the latter simply means "serious"! So, make sure you understand the context of the question to interpret words such as "formal".

The Product Owner and Scrum Master should NOT be part of the Development Team. a. False b. True

A Did you notice the word "not" in the statement? OK, this is usually tricky! Think of it like this: is it correct to say that they should not be part of the Development Team? No, this is not correct (because they can be part of the team), therefore, the statement is false. What some people do is think about the opposite statement, and get confused. Note that the opposite of this statement is NOT "the Product Owner and Scrum Master should be part of the Development Team". The correct opposite of "should not" is "could" or "can" or "may", NOT "should". One person can have more than one role in Scrum (not recommended, but allowed).

Each item in the Sprint Backlog is owned by one or a pair of developers. a. False b. True

A Each item may be done by one or a pair of developers (usually more people are involved), but those people won't "own" the item, and all developers stay accountable for it and share the ownership.

The Product Owner is the main person responsible for engaging the stakeholders. a. True b. False

A Engagement of stakeholders is mostly about and around the Product Backlog items, and at least indirectly, about the value created in the project. That's why this is mainly the responsibility of the Product Owner to keep them engaged.

The Scrum Master should ask each developer to answer the three standard questions at the Daily Scrum. a. False b. True

A First, it's a good idea to go over the three questions, but it's not mandatory. Second, the meeting is managed by developers (by default).

What is the main reason for the Scrum Master to be at the Daily Scrum? a. The developers have asked the Scrum Master to facilitate their Daily Scrum. b. To make sure that every developer answers the three questions. c. To get a report on progress of the Sprint. d. To track changes to the Sprint Backlog.

A In general, Daily Scrum is for the Development Team, which means that only the developers "participate" (talk). Others can "attend" (watch), but they won't "participate" (talk). Well, unless it's about a Scrum Master facilitating the meeting (not so common), in which case they will talk a little ;) However, this contribution of the Scrum Master is about the context, not the content.

A 2x increase in the number of developers will double productivity. a. False b. True

A It can increase productivity in the long-term, but probably not linearly.

Each Scrum Team should have a Scrum Master and a Product Owner. a. True b. False

A It doesn't mean that those people cannot be the Product Owner or Scrum Masters of other teams. When there are multiple teams, multiple "people" can work as the Scrum Master, but they will all have one Product Owner. Still, the statement stays valid: there's one person you can identify as your Product Owner.

It's wrong to have a Project Manager in Scrum. a. True b. False

A There's no project manager role in Scrum, and it's not allowed to add new role to the existing three. Also, none of those three roles are the equivalent of a project manager; project management activities are distributed among all of them. This is only about the project level; you can always have higher management levels (e.g. program management), and those "can" be compatible with what you do in your Scrum projects.

Which of the following is a valid service from the Scrum Master to the Product Owner? a. Help the Product Owner find techniques for managing the Product Backlog. b. Act as the middleman between the Product Owner and the Development Team, as requested or required. c. Help the Product Owner order the Product Backlog items in order to maximize value. d. Act as a proxy when the Product Owner is not available to the team

A It has to be coaching/training rather than doing the actual work. For example, helping them order the backlog is not a good idea, but helping them understand how to order the backlog is a good idea.

Sprint Review is a formal meeting. a. False b. True

A It's not a formal meeting, in the sense that you and the customer won't work on approval/acceptance of the product and exchanging signatures (that would block feedback generation). This may be confusing, because on the other hand, Sprint Review (and other events) are considered "formal opportunities for inspecting and adapting". The word "formal" has been used for two different meanings in the exam, the former is what we have in this question, and the latter simply means "serious"! So, make sure you understand the context of the question to interpret words such as "formal".

It's allowed to have Team Leaders when many developers are working on a complex project. a. False b. True

A It's not allowed to introduce new roles or titles in Scrum.

All teams should be cross-functional in scaled Scrum. a. True b. False

A It's one of the basic concepts in Scrum to have cross-functional, self-organizing teams.

A Product Owner who used to be a project manager in the past is using burn-up charts instead of burn-down charts. Is that acceptable? a. There's nothing wrong with it. b. Burn-up charts are used in traditional methods, and they should be replaced by burn-down charts.

A It's up to the Product Owner to decide how they want to measure and visualize performance.

Who prioritizes or orders the tasks in the Sprint Backlog? a. The Development Team b. The Product Owner c. Stakeholders d. The whole Scrum Team e. The customer f. The Project Manager

A Items in the Product Backlog are ordered and prioritized by the Product Owner, but when it comes to the Sprint Backlog, it's up to the developers to decide how to manage their tasks.

In scaled Scrum, each developer should be a member of only one team. a. False b. True

A None of the Scrum roles are necessarily full-time, and the person can occupy more than one role (e.g. both Scrum Master and developer), or be a developer in more than one team. E.g. there may be a special expertise that is needed in multiple teams, but its not needed in a full-time basis. So, one person can provide that special type of expertise to multiple teams.

When multiple teams are working on the same product, one person can be a member of more than one Development Team. a. True b. False

What's the normal timeboxed duration of Sprint Retrospective when there are 6 developers in the team and Sprints are two weeks long? a. 1.5 hours b. 4 hours c. 3 hours d. Maximum 8 hours

A Note that the duration of events is not dependent on the number of developers. The timeboxed duration of events is as follows: Sprint - Maximum 1 month Daily Scrum - 15 minutes Sprint Planning - 8 hours in a one-month Sprint, and shorter proportionally Sprint Review - 4 hours in a one-month Sprint, and shorter proportionally Sprint Retrospective - 3 hours in a one-month Sprint, and shorter proportionally

Who is required to attend the Daily Scrum? A) The Development Team. B) The Scrum team. C) The Development Team and Scrum Master. D) The Development Team and Product Owner. E) The Scrum Master and Product Owner.

A Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Scrum Master or Product Owner is also on the Development Team, they will need to be at the Daily Scrum. Otherwise, the Scrum Master simply has to make sure the Development Team knows how to conduct a Daily Scrum and does so.

Who is required to attend the Daily Scrum? a. The Development Team b. The Development Team and the Product Owner c. The Development Team and the Scrum Master d. The whole Scrum Team

A Others "can" attend the meeting, but it's not correct to say that they "should", or "are required to" attend (they don't have to be there, but they can attend, if they want). Daily Scrum is for the developers; only they "participate" (=talk). Others can "attend" (=watch).

Scrum Teams should normalize their estimations, so that management can measure and compare their performance. a. False b. True

A Progress measurements are done internally, not by external "managers". Also, comparing the velocity (dependent on the estimates) of two different teams is never reliable, and it's not productive even if it were reliable (e.g. by normalizing them).

Which of the following best describes the way a Product Owner can order the items in the Product Backlog? a. Based on value, priority, dependencies, and risk b. Based on risk; riskier items at the top c. Based on size; smaller items at the top d. Based on size; larger items at the top

A Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice, the next best answer (the old-fashioned one) is "based on value". Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have".

Which of the following best describes the way a Product Owner can order the items in the Product Backlog? a. Based on value, priority, dependencies, and risk b. Based on risk; safer items at the top c. Based on size; larger items at the top d. Based on size; smaller items at the top

Which three of the following are pillars of Scrum? a. Adaptation b. Value optimization c. Collaboration d. Transparency e. Sustainable pace f. Inspection

A, D, F Pillars are transparency, inspection, and adaptation. Make sure you're not confusing these pillars with the Scrum values (commitment, courage, focus, openness, and respect).

What is a proper role of a PMO in a company that uses Scrum? a. Manage portfolios and programs and facilitate the application of techniques that complement Scrum. b. The PMO should manage and help the Product Owners. c. The PMO will be responsible for making higher level decision in the project.

A Remember that there are limits to the self-organization of the team, and the important thing is to have power within the borders of the project. However, each project is run in a wider organization with multiple levels of management that impact the project, and it's not possible or even acceptable to reject that structure, as long as it doesn't block internal self-organization of the team.

Scrum is a technique for developing complex products. a. False b. True

A Scrum is "considered" a framework, not a methodology, process, techniques, etc. It can be used to develop new products or maintain/sustain existing ones.

Upon what type of process control is Scrum based? A) Empirical B) Hybrid C) Defined D) Complex

A Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

It's up to the self-organizing team to decide which Scrum events are needed in the project. a. False b. True

A Self-organization is not unlimited; e.g. you should follow the Scrum framework.

Which of the following is not allowed in Scrum? a. Sprint Zero b. Using Planning Poker c. Using Story Points d. Refactoring

A Some concepts are mandatory; e.g. Sprint Retrospective. Some are not mandatory, but allowed; e.g. using User Stories. Some are not allowed; e.g. Sprint Zero. It's important not to mix the "not mandatory, but allowed" with the "not allowed".

How often should the composition of the team change? a. As needed, considering that it will have a short-term reduction in productivity b. As needed, without a need to be concerned about changes in productivity c. Every Sprint, to encourage creativity and openness d. Never, because it reduces productivity

A Sometimes you will see questions like this in the exam. You may know that the composition of the team should not change during the Sprint, yet, the correct choice here may imply that. Well, it is up to you to interpret it in a way that it doesn't mean such a thing! So, the precise statement would be "As needed, so long as it's not in the middle of the Sprint, and we consider that it may have a short-term reduction in productivity".

Which of the following has the most to do with capturing and using lessons learned? a. Sprint Retrospective b. Sprint Planning c. Product Backlog Refinement d. Sprint Review

A Sprint Retrospective is about discussing the way work was done and finding ways to improve it next time; this is mainly about lessons learned.

Who is responsible for managing the progress of work during a Sprint? A) The Development Team B) The Scrum Master C) The Product Owner D) The most junior member of the Team

A The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.

Having the team members and a complete Product Backlog are the only things needed to start the project. a. False b. True

A The Product Backlog is never complete.

The first Sprint can start as soon as the Product Backlog is complete. a. False b. True

A The Product Backlog is never complete.

Which statement best describes a Product Owner's responsibility? A) Optimizing the value of the work the Development Team does. B) Directing the Development Team. Incorrect answer C) Managing the project and ensuring that the work meets the commitments to the stakeholders. D) Keeping stakeholders at bay.

A The Product Owner is responsible for maximizing the value of the product and the work of the Development Team.

The Scrum Master should NOT allow the Sprint Planning meeting to start when the Sprint Goal is not ready. a. False b. True

A The Sprint Goal is prepared during the Sprint Planning meeting. Also, Scrum Masters don't order people, they teach and convince people to do the right thing.

How does the Product Owner determine the number of items for the Sprint Backlog? a. They don't do it! b. Based on a combination of velocity and team capacity c. Based on what is needed for the next release d. Based on the feedback received from the customer in the previous Sprint Review

A The developers decide how many items to select for the Sprint Backlog, not the Product Owner.

How does the Product Owner determine the number of items for the Sprint Backlog? a. They don't do it! b. Based on velocity c. Based on what is needed for the next release d. In a way that maximizes the value of the Increment

A The developers decide how many items to select for the Sprint Backlog, not the Product Owner.

The purpose of each Sprint is to release a piece of working software. a. False b. True

A The purpose is to create a potentially releasable piece of software. It doesn't have to be released.

What's the timeboxed duration of Sprint Retrospective meetings? a. Maximum 3 hours b. Maximum 8 hours c. 8 hours in a one-month Sprint d. 4 hours in a one-month Sprint

A The timeboxed duration of events is as follows: Sprint - Maximum 1 month Daily Scrum - 15 minutes Sprint Planning - 8 hours in a one-month Sprint, and shorter proportionally Sprint Review - 4 hours in a one-month Sprint, and shorter proportionally Sprint Retrospective - 3 hours in a one-month Sprint, and shorter proportionally

The Development Team is self-organized, therefore, they can decide to drop Daily Scrums. a. False b. True

A Their empowerment (self-organization) is not unlimited; e.g. they can't make changes to the framework.

There are no testers in Scrum. a. True b. False

A There are no people "titled" as testers, because we don't have extra roles and titles in Scrum. However, there can be "developers" who are expert in testing. Remember that everyone in the Development Team is called a "developer".

Who's responsible for quality? a. All developers b. Team leaders c. Testers

Since the Product Owner is accountable for the value of the product, they have the final say over the Definition of Done. a. True b. False

At least one high-priority process improvement item exists in each Sprint Backlog. a. True b. False

A This is one of the statements added to the latest update of Scrum Guide: At least one high-priority process improvement item exists in each Sprint Backlog. It was a little unexpected, because it's mixing content related to the product with the content related to the process in the Sprint Backlog; but, well, that's how it is now.

Some items in Sprint Backlogs are not directly about the features and functions of the product. a. True b. False

Which statement is not true about the Scrum? "

A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists. Due to this requirements cannot be static"

What are Product Backlog features? Select three. 1) It is never complete 2) It is dynamic 3) As long as a product exists, its Product Backlog also exists When the final version of a product is rolled out, its Product Backlog is dismissed 4) A Product Backlog could be closed when it contains no items to include into the next Sprint

A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.

The Sprint Review is an event that requires

Which of the following is true about the Sprint Review? (choose 2 answers)

A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate on what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done in order to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. This is at most a four-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendees understand its purpose. The Scrum Master teaches everyone involved to keep it within the time-box.

A key measure of success for the Product Owner is velocity.

A key measure of success for the Product Owner is high value product

potentially shippable product

A potentially shippable product is one that has been 1. designed, 2. developed and 3. tested and is therefore ready for distribution to anyone in the company for review or even to any external stakeholder. Adhering to 1. list of "done" and 2. acceptance criteria ensures that the sprint product is truly shippable.

At the end of a Sprint a Product Backlog items worked on during the Sprint does not meet the definition of "Done". What two things should happen with the undone Product Backlog items?

A) Do not include the item in the Increment this Sprint B) Put it on the Product Backlog for the Product Owner to decide what to do with it.

Select three incorrect, untrue, or misleading statements about Scrum? A) Scrum is like traditional processes but with self-organization to replace Project Managers. B) Scrum is based on empirical process control theory. C) Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment. D) Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products. E) Scrum is a framework that eliminates complexity. F) Scrum is a framework for developing and sustaining complex products.

A) Scrum is like traditional processes but with self-organization to replace Project Managers. C) Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment. E) Scrum is a framework that eliminates complexity.

Who is on the Scrum Team?

A) The Scrum Master B) The Product Owner C) The Development Team

Which of the following might the Scrum Team discuss during a Sprint Retrospective?

A) The way the Scrum Team does Sprint Planning B) its Definition of "Done" C) Methods of communication D) Skills needed to improve the Development Team's ability to deliver **E) All of the above

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?

A) Without a new vocabulary as a reminder of the change, very little change may actually happen. B) The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. C) Management may feel less anxious. **D) All answers apply.

Which two of the following are correct about the whole Scrum Team role? a. Is designed in a way to maximize creativity b. Is designed in a way to maximize flexibility c. Makes the Product Backlog transparent and visible d. Is responsible for maximizing the value of the work of the Development Team e. Is accountable for all changes to the Product Backlog

A, B

Which two of the following are pillars of Scrum? a. Transparency b. Adaptation c. Collaboration d. Value optimization e. Creativity

A, B

Which two of the following can be reasons for the Scrum Master to attend the Daily Scrum? a. The developers have asked the Scrum Master to facilitate their Daily Scrum. b. It's not necessary for them to be in the meeting. c. To get a report on progress of the Sprint. d. To assign tasks to developers. e. To make sure that every developer answers the three questions.

A, B

Which two statements are correct about the Definition of Done? a. There can be more than one Definition of Done when multiple teams are working on the same project. b. Used by the developers to forecast how many items they can pick for the Sprint. c. It helps the Product Owner measure the progress of Sprints. d. It helps the Product Owner track open work during the Sprint.

A, B

Which two statements explain when a Product Backlog item is considered complete? a. When no work is left based on the Definition of Done b. When everything is Done based on the Definition of Done c. When the Scrum Master approves it d. When user acceptance tests are passed

A, B

Which two of the following is correct about the length of Sprints? a. It's preferred to have Sprints with the same length. b. All Sprints must be one month or less. c. Depends on the position of the stars ;) d. Sprint length is set during Sprint Planning, and is long enough for programming and testing all items, but not for integrating them. e. Sprint length is set during Sprint Planning, and is long enough to develop all items in the Sprint Backlog.

A, B (a) We don't change the timeboxed duration of Sprints on an ad hoc basis; maybe just a few times, based on what we've learned from the project. (b) One month is the maximum timeboxed duration for Sprints in Scrum.

Which two of the following can be considered real outputs of the Sprint? a. A piece of software that is usable by the end users b. An Increment of working software c. A plan for the next Sprints d. A user interface layout that is designed for the whole solution

A, B A real output is the Increment: a piece of working software that is Done based on the Definition of Done. From a wider perspective, you can also consider the feedback that is generated by the customer and the improvements you plan in the Sprint Retrospective as real outputs; but a question like this is focused on checking if you can distinguish DONE items from technical tasks; the former is valuable for us, while the latter is just the means.

Which two of the following are mandatory elements in Scrum? a. Daily Scrums b. Sprint Reviews c. Planning Poker d. Face-to-face communications e. Burn-down charts

A, B Only the roles, events, and artifacts (+ Definition of Done and progress measurement) are mandatory.

Which three of the following are pillars of Scrum? a. Inspection b. Transparency c. Adaptation d. Collaboration e. Creativity f. Sustainable pace

A, B, C Pillars are transparency, inspection, and adaptation. Make sure you're not confusing these pillars with the Scrum values (commitment, courage, focus, openness, and respect).

Which three of the following are timeboxed? a. Sprint Review b. Daily Scrum c. Sprint testing d. Sprint e. Product Backlog Refinement f. Sprint Zero

A, B, D

Which two of the following are required by Scrum? a. Sprint Retrospectives b. User Stories c. Burn-down charts d. Answering the three standard questions during Daily Scrums e. Definition of Done

A, E

An organization has decided to adopt Scrum. Which three of the following describe what happens if they tailor the Scrum terminology to match their current environment? a. Management may feel less enthusiastic about the change. b. The change might not be obvious to everyone, and therefore very little change actually happens. c. They will get better results adopting Scrum this way. d. The change might not be obvious to everyone, and some benefits may be lost.

A, B, D Scrum is a simple framework rather than a comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your project by the practices and techniques that you add; e.g. Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers.

Which three statements best describe the Product Backlog? a. It may change anytime, and it is never complete. b. The customer's change requests are reflected in it. c. Contains only small and clear items. d. Contains all tasks identified by the developers. e. It is never baselined.

A, B, E

Which three of the following actions may a Scrum Master take in starting up a project? a. Ask the Development Team to discuss and identify the way they are going to develop the product. b. Ask the Product Owner to explain the project, its business need, history, goals, and context. c. Ask the development managers to introduce their departments and capabilities. d. Ensure that team members have clear roles and responsibilities. e. Ask the team to work together and prepare a complete Product Backlog. f. Ask the Development Team members to introduce themselves to each other and tell about their skills and background.

A, B, F

Which three of the following actions may a Scrum Master take in starting up a project? a. Ask the Product Owner to explain the project, its business need, history, goals, and context. b. Ask the Development Team members to introduce themselves to each other and tell about their skills and background. c. Ask the development managers to introduce their departments and capabilities. d. Ask the team to work together and prepare a complete Product Backlog. e. Ensure that there's a clear understanding of the whole scope of the project. f. Ask the Development Team to discuss and identify the way they are going to develop the product.

A, B, F

Which three of the following are NOT acceptable in Scrum? a. Release Sprints b. Sprint Zero c. Using User Stories d. Using Story Points e. Refactoring f. Integration Sprints

A, B, F (a) Not allowed, because it's a reason for having Increments that are not potentially releasable and waiting for "release" Sprints. (b) Not allowed; preparing the tools and infrastructure is done gradually during normal Sprints. Otherwise, it will block adaptation and generation of value. (f) Not allowed, because all items must be integrated before we can consider them Done.

Which three of the following are pillars of Scrum? a. Inspection b. Adaptation c. Sustainable pace d. Value optimization e. Collaboration f. Transparency

A, B, F Pillars are transparency, inspection, and adaptation. Make sure you're not confusing these pillars with the Scrum values (commitment, courage, focus, openness, and respect).

The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially releasable product Increment is created. This applies to every Sprint**Which two things does the Development Team do during the first Sprint? A) Deliver an increment of potentially releasable software. B) Determine the complete architecture and infrastructure for the product. C) Develop and deliver at least one piece of functionality. D) Develop a plan for the rest of the release. E) Create the complete Product Backlog to be developed in subsequent Sprints

A, C

Which two of the following are correct about the Product Owner role? a. Is responsible for maximizing the value of the product b. Prioritizes tasks in the Sprint Backlog c. Makes the Product Backlog transparent and visible d. Can make changes to the Sprint Backlog e. Helps the organization implement Scrum

A, C

Which two statements describe what happens when organizations change the Scrum terminology while implementing it? a. The change might not be obvious to everyone, and therefore very little change actually happens. b. They will get better results adopting Scrum this way. c. Management may feel less enthusiastic about the change. d. It's necessary to tailor Scrum to suit the project.

A, C

Which two statements explain when a Product Backlog item is considered complete? a. When there's nothing more we need to do before it can be used by end users b. When all identified tasks are done c. When everything is Done based on the Definition of Done d. When the Scrum Master approves it

A, C (a) Usable for end-users = potentially shippable = potentially releasable = done based on the Definition of Done (c)This is the ultimate answer! The Definition of Done is composed in a way that ensures this behavior.

When is the Sprint over? (Choose two answers) a. When the Product Owner cancels the Sprint b. When the Sprint Backlog tasks are done c. When the timeboxed duration is over d. When the Scrum Master announces the end of the Sprint e. When all Sprint Backlog items are done

A, C It's a simple question: you need to know what timeboxing means, and that Sprints are timeboxed. Other than the normal ends of Sprints, the Product Owner also has the authority to cancel a Sprint.

The Development Team cannot forecast how much work they can do in the upcoming Sprint, because of uncertainties in the Product Backlog that the Product Owner is not able to overcome. What two actions should the Scrum Master recommend? a. Invite everyone to discuss this problem in the next Sprint Retrospective and try to find a solution. b. Extend the duration of Sprint Planning and ask them to discuss the items more and get into agreement. c. Ask the developers to come up with their best guess and do not worry about the capacity. d. Cancel the Sprint Planning meeting, give them some time to prepare, and then hold another Sprint Planning. e. Cancel the Sprint and start the next one when the items are clear.

A, C It's fine! You just pick a number of items. If it was not enough, you can pick more later. If it was too many, you will just deliver as many as you can. Nothing bad happens if you don't deliver all items in the Sprint Backlog. The goal is to generate value, not to develop all items in the backlog.

Which three statements best describe the Product Backlog? a. It may change anytime, and it is never complete. b. Contains all tasks identified by the developers. c. It is never baselined. d. The customer's change requests are reflected in it. e. Contains only small and clear items.

A, C, D

What are the three questions of the Daily Scrum? a. What impediments are in my way or in the way of the team? b. Are we able to deliver all Sprint Backlog items by the end of the Sprint? c. What work am I going to do today to help the team achieve its goal? d. What work did I do yesterday to help the team achieve its goal? e. How many hours did I spend on the project yesterday? f. What is the progress of the Sprint?

A, C, D It's not mandatory to use these questions, but very common and recommended.

What are the three questions of the Daily Scrum? a. What work am I going to do today to help the team achieve its goal? b. How many hours did I spend on the project yesterday? c. What impediments are in my way or in the way of the team? d. What work did I do yesterday to help the team achieve its goal? e. Are we able to deliver all Sprint Backlog items by the end of the Sprint? f. What problems did I have yesterday?

A, C, D It's not mandatory to use these questions, but very common and recommended.

Which three Scrum values are demonstrated by focusing on the most valuable items first? a. Focus b. Adaptation c. Courage d. Respect e. Earned Value

A, C, D Scrum values are commitment, courage, focus, openness, and respect.

Which three of the following may be done in the Sprint Retrospective meeting? a. Discuss the composition of the team b. Discuss the Product Backlog items for the next Sprint c. Discuss the way Increments are demonstrated to the customer d. Calculate Velocity e. Discuss the relationship with the customer and the way user acceptance testing is done f. Refining the Product Backlog

A, C, E

Which three statements best describe the Product Backlog? a. It may change anytime, and it is never complete. b. Contains only small and clear items. c. It changes as we learn more about the project. d. It's used to create the project plan. e. The Product Owner is accountable for it.

A, C, E

Which three statements show the result of changing Scrum terminology while implementing it in the organization? a. Management may feel less enthusiastic about the change. b. It's necessary to tailor Scrum to suit the project. c. The change might not be obvious to everyone, and therefore very little change actually happens. d. They will get better results adopting Scrum this way. e. The change might not be obvious to everyone, and some benefits may be lost.

A, C, E Scrum is a simple framework rather than a comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your project by the practices and techniques that you add; e.g. Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers.

Which three of the following may be done in the Sprint Retrospective meeting? a. Discuss the timeboxed duration of Sprints b. Discuss the next Sprint goal c. Discuss techniques used to facilitate the Sprint Retrospective meeting d. Refining the Product Backlog e. Discuss the Definition of Done f. Calculate Velocity

A, C, E Sprint Retrospective is about the way we work. It's about the things that affect the product, but we don't discuss the product directly. In general, it's about the context, not the content. For example, we can talk about the way Product Backlog is refined, but we won't refine the Product Backlog in the Sprint Retrospective meeting.

What are the three questions of the Daily Scrum? a. What work did I do yesterday to help the team achieve its goal? b. What problems did I have yesterday? c. What work am I going to do today to help the team achieve its goal? d. What is the progress of the Sprint? e. How many hours did I spend on the project yesterday? f. What impediments are in my way or in the way of the team?

A, C, F It's not mandatory to use these questions, but very common and recommended.

Which two of the following actions may a Scrum Master take in starting up a project? a. Ask the Product Owner to explain the project, its business need, history, goals, and context. b. Ask the team to work together and prepare a complete Product Backlog. c. Ask the development managers to introduce their departments and capabilities. d. Ask the Development Team to discuss and identify the way they are going to develop the product. e. Ensure that team members have clear roles and responsibilities.

A, D

Which two of the following are mandatory elements in Scrum? a. Sprint Planning b. Story Points c. Pair-Programming d. Progress measurement e. Face-to-face communications

A, D

Which two statements best describe the Product Backlog? a. It is never baselined. b. Provides just enough information to enable the developers to design the product. c. Contains only small and clear items. d. The customer's change requests are reflected in it.

A, D (a) Scrum.org interprets "baseline" as fixing something (which is not entirely correct), and therefore says that nothing should be baselined in Scrum.

Which two of the following contribute the most to the Scrum value "focus"? a. Timeboxing b. Sprint Review c. Product Backlog Refinement d. Sprint Goal

A, D Scrum values are commitment, courage, focus, openness, and respect.

Which three of the following may be done in the Sprint Retrospective meeting? a. Discuss the way Product Backlog Refinement is done during the Sprints b. Calculate Velocity c. Discuss the Product Backlog items for the next Sprint d. Discuss the Definition of Done e. Refining the Product Backlog f. Discuss tools used to communicate with remote team members

A, D Sprint Retrospective is about the way we work. It's about the things that affect the product, but we don't discuss the product directly. In general, it's about the context, not the content. For example, we can talk about the way Product Backlog is refined, but we won't refine the Product Backlog in the Sprint Retrospective meeting.

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.**Which of the below are roles on a Scrum Team? Correct answer A) Development Team B) Users C) Customer D) Product Owner E) Scrum Master

A, D, E

Which two of the following best describe Sprint Planning? a. What are we going to do during the Sprint? b. Who will do what we have decided to do in the Sprint? c. Who will be in the team this Sprint? d. What went wrong in the last Sprint and what to do about it e. How are we going to do what we have decided to do in the Sprint?

A, E

Which two of the following are timeboxed? a. Sprint Planning b. Release Planning c. Sprint testing d. Product Backlog Refinement e. Sprint Retrospective

A, E The events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective) are timeboxed.

Which three of the following may be done in the Sprint Retrospective meeting? a. Discuss techniques used to facilitate the Sprint Retrospective meeting b. Refining the Product Backlog c. Discuss the next Sprint goal d. Calculate Velocity e. Discuss the relationship with the customer and the way user acceptance testing is done f. Discuss the Definition of Done

A, E, F

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog? A. As soon as possible after they are identified. B. When the Scrum Master has time to enter them. C. During the Daily Scrum after the Development Team approves them. D. When the Product Owner identifies new work.

A. As soon as possible after they are identified.

If the Product Backlog is not ready for Sprint Planning, what happens? A. Cancel the Sprint until backlog is ready. B. Let the team decide what should be done. C. Identify enough work for the first day and set up a second Sprint Planning meeting when the Product Backlog is ready. D. Work during Sprint Planning to refine the backlog for one Sprint.

A. Cancel the Sprint until backlog is ready. If a Product Backlog isn't ready for Sprint Planning, it means that the Development Team will be unable to make a forecast (i.e. they won't be able to create a Sprint Backlog), nor will they be able to commit to makking an incremental delivery of value. The Sprint should be canceled.

Who is responsible for crafting the Sprint Goal at the Sprint Planning? 1) The Product Owner 2) The Scrum Team 3) The Scrum Master 4) The Development Team 5) The Key Stakeholders

After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.

If two Scrum Teams are added to the development of a product that previously had only one Scrum team, what will be the immediate impact on the productivity of the original Scrum Team? A. Its productivity is likely to decrease. B. Its productivity is likely to stay the same. C. Its productivity is likely to increase.

A. Its productivity is likely to decrease.

Pick roles that support the Scrum Master in removing impediments. A. Senior Management B. The Development Team C. The Product Owner D. The Customer

A. Senior Management B. The Development Team

When multiple teams are working on the same product, each team should have their definition of "Done".

All teams can use the same definition of "Done", but individual Scrum Teams may choose to apply a more stringent definition of "Done" within their own teams, but cannot apply less rigorous criteria than agreed for the Increment.

Who is on the Scrum Team'? A. The Development Team B. None of the above C. The Scrum Master D. Project Manager E. The Product Owner

A. The Development Team C. The Scrum Master E. The Product Owner

Which two statements are true about the Sprint Backlog? A. The development team modifies the Sprint Backlog during the Sprint. B. The Product Owner decides on the Scope of the Sprint. C. The Sprint Backlog is said to emerge during the Sprint. D. The Sprint Backlog does not change after the Sprint Planning Meeting.

A. The development team modifies the Sprint Backlog during the Sprint. C. The Sprint Backlog is said to emerge during the Sprint.

When is a Product Backlog item considered complete? A. The item has no work remaining that must still be done before it can be used by its end user. B. When QA reports that it passes all acceptance criteria. C. At the end of the Sprint. D. When all work in the Sprint Backlog that is related to is complete.

A. The item has no work remaining that must still be done before it can be used by its end user.

Which outcome is expected as Scrum Teams mature?

A. They will improve their definition of Done to include more stringent criteria.

Software dependencies can influence how the Product Owner orders Products Backlog items. A. True B. False

A. True

Scrum Master is a 'management' position? A. True B. False

A. True The Scrum Master manages the Scrum process. If the Scrum Master is not a management position, he or she may not have the influence to remove impediments. The Scrum Master does not manage the team.

When is a Sprint over? A. When the timebox expires. B. When all the tasks are completed. C. When all Product Backlog items meet their definition of done. D. When the Product Owner says it is done.

A. When the timebox expires

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint? A. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done. B. No, each Scrum Team stands alone. C. Yes, but only for Scrum Teams whose work has dependencies. D. No, that is far too hard and must be done in a hardening Sprint.

A. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done. Each increment released by each Scrum team at the end of a Sprint must be potentially shippable. This implies that they must not only be integrated, but also subjected to whatever system integration, UAT, or pre-release testing is needed.

Which of the following is the LEAST productive way for the Scrum Master to improve the Development Team's communications with the Product Owner?

Acting as a go-between weakens the team and blocks their self-organization. The Scrum Master is supposed to teach and coach

When does (at which Scrum event) adaptation occur in Scrum?

Adaptation occurs during all Scrum events

What are two good ways to make non-functional requirements visible?

Add them to the Product Backlog and keep the product owner posted on the expected effort Add them to the definition of "Done" so the

Which of the following best describes an increment of working software?

Additional features in a usable state that complement those delivered in previous iterations.

Which of the following best describes an increment of working software?

Additional features in a useable state that complement those delivered in previous iterations.

Which artifact contains a plan for realizing the Sprint Goal? a. Product vision b. Product Backlog c. Sprint Goal itself d. Sprint Backlog

Scrum is not:

Agile is all about depending on adaptation, instead of a predictive (static, upfront) plan and design.

When many Development Teams are working on a single product, what best describes the definition of "Done?"

All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

When many Development Teams are working on a single product, what best describes the definition of "done?"

All Development Teams must have a definition of "done" that makes their combined work potentially releasable.

Which statements are correct about Sprint Retrospective meeting?

All Scrum ceremonies are opportunities for inspection and adaptation

It's up to the Development Team to decide which Scrum events are needed during the Sprint.

All Scrum events are necessary for Development Team

What are some consequences if a Development does not have a consistent Definition of Done from Sprint to Sprint?

All answers are correct

In order to make investment decisions, the Product Owner is likely to look at the Total Cost of Ownership (TCO) of the product being built. What costs will a Product Owner take into account?

All investments required to conceive, develop, operate and maintain the product

What is the best description of the job of a Product Owner?

All items are less or more applicable, but remember that the main responsibility of the Product Owner is to maximize value, and "working with stakeholders to identify the most important requirements" is the closest answer to "increasing value".

Which of the following might the Scrum Team discuss during a Sprint Retrospective?

All of the above (1. The way the Scrum Team does Sprint Planning. 2. Skills needed to improve the Development Team's ability to deliver. 3. Methods of communication. 4. Its Definition of "done")

The Sprint Goal provides the following

All of the above are the Sprint Goal characteristics

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?

All of the above.

Which Scrum Value is affected by a lack of trust in the Scrum Team?

All of the above. (A. Focus B. Respect C. Openness D. Courage E. Commitment.)

Where can Scrum be used? Check all the applicable items. 1) Research and identifying of viable markets, technologies, and product capabilities 2) Development and sustaining of Cloud and other operational environments 3) Development of products and enhancements 4) Development of almost everything we use in our daily lives as individuals and societies 5) Development of software and hardware 6) Managing the operation of an organization

All of them! Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies. Scrum has been used extensively, worldwide, to: ◦ Research and identify viable markets, technologies, and product capabilities; ◦ Develop products and enhancements; ◦ Release products and enhancements, as frequently as many times per day; ◦ Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and, ◦ Sustain and renew products.

The length of a Sprint should be:

All of these answers are correct. (1. Short enough to keep the business risk acceptable to the Product Owner. 2. Short enough to be able to synchronize the development work with other business events. 3. No more than one month.)

What is the maximum length of a Sprint?

All of these answers are correct. - Not so long that the risk is unacceptable to the product owner. - Not so long that other business events can't be readily synchronized with the development work. - No more than one calendar month.

Sprint Retrospective Meeting

All the meetings are regarding product but this one is regarding the assessment of the process. Its mostly about learning from previous sprints for process improvement by asking 2 questions 1. what went well during sprint 2. what could be improved in next sprint Techniques 1. Safety check 2. classic scrum retrospective 3. focused conversation principles (Objective, reflective, interpretive, and decisional (ORID)) 4. silent writing 5. timeline retrospective 6. decisions Impediments -presence of people who conduct performance appraisals -invisible gun effect -human tendency to jump to conclusions and propose actions too quickly -geographic distribution

A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take?

Allow the Development Team to self manage and determine for itself what to do.

All interactions between the stakeholders and the Development Team should be through the Product Owner.

Almost always these interactions go through the Product Owner but of course, it is not prohibited to discuss some questions with stakeholders. But those who want to change a Product Backlog item's priority must address the Product Owner.

Sprint burndown charts are an efficient tracking tool because they allow:

An estimate of the total work remaining for the sprint

What are the two essential features a Scrum Team should possess? 1) It should choose how best to accomplish their work, rather than being directed by others outside the team 2) It should have all competencies needed to accomplish the work without depending on others not part of the team 3) It should use tools, processes and techniques approved by the Organization 4) It should be flexible enough to complete all the work planned for the Sprint even if some team members are on vacation

Answer 1 and 2. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

Which two ways of creating Development Teams are consistent with Scrum's values? Choose 2 answers

Answer 1 of 2: Bring all the developers together and let them self-organize into Development Teams. Answer 2 of 2: Existing teams propose how they would like to go about organizing.

A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected items done by the end of the Sprint. Select two statements that explain what done means.

Answer 1 of 2: No work left from the definition of "Done". Answer 2 of 2: All work to create software usable by end users.

As the Sprint Planning meeting progresses, the Development Team sees that the workload is greater than they can handle. Which two are valid actions? Choose 2 answers

Answer 1 of 2: Remove or change selected Product Backlog items. Answer 1 of 2: Recruit additional Development Team members before the work can begin.

What are two ways that architecture and infrastructure are handled in Scrum?

Answer 1 of 2: They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small. Answer 2 of 2: They are implemented along with functional development of the product.

The purpose of the Sprint Retrospective is to (select three): 1) Identify and order the major items that went well and potential improvements 2) Get technical or domain advice from specialists invited by The Development Team or The Scrum Master 3) Create a plan for implementing improvements to the way the Scrum Team does its work 4) Inspect how the last Sprint went with regards to people, relationships, process, and tools 5) Get feedback from the Key Stakeholders invited by the Product Owner

Answer 1, 3 and 4. The purpose of the Sprint Retrospective is to: - Inspect how the last Sprint went with regards to people, relationships, process, and tools; - Identify and order the major items that went well and potential improvements; and, - Create a plan for implementing improvements to the way the Scrum Team does its work.

Who is allowed to change the Sprint Backlog during the Sprint? 1) The Development Team 2) The Product Owner 3) The Scrum Team 4) The Scrum Master 5) The Development Team and the Product Owner

Answer 1. Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.

What part of the capacity of the Development Team does Product Backlog refinement usually consume? 1) Not more than 10% 2) Not more than 20% 3) Not more than 5% 4) The Development Team is not authorized for Product Backlog refinement

Answer 1. Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team.

In which meetings the Key Stakeholders are allowed to participate? 1) The Sprint Review 2) The Sprint Retrospective 3) The Sprint Planning 4) The Daily Scrum

Answer 1. The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time,

Who is responsible for the Product Backlog? 1) The Product Owner 2) The Product Owner and The Scrum Master 3) The Scrum Master and The Development Team 4) The Product Owner and The Development Team 5) The Scrum Master 6) The Development Team

Answer 1. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering

What is the Sprint Retrospective? 1) It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint 2) It is a meeting to inspect the Increment and adapt the Product Backlog if needed 3) It is the key inspect and adapt meeting 4) It is a meeting where the Development Team synchronizes activities and creates a plan for the next 24 hours

Answer 1. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

What is the Sprint Backlog? 1) The Product Backlog items selected for this Sprint plus the plan for delivering them 2) The plan for delivering Product Backlog items 3) The Product Backlog items selected for this Sprint 4) The Product Backlog items selected for this Sprint plus the Team Backlog items

Answer 1: The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

What is the result of the Sprint Review? 1) A list of improvements that the Scrum Team will implement in the next Sprint 2) A revised Product Backlog that defines the probable Product Backlog items for the next Sprint 3) Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved 4) Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog

Answer 2. The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, when must an adjustment be made? 1) After Scrum Master approval 2) As soon as possible to minimize further deviation 3) The deviations should be discussed at the Daily Scrum and then an adjustment must be made 4) After clarifying all the details with the Product Owner

Answer 2. If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.

Who is responsible for creation of the Definition of "Done"? 1) The Product Owner 2) The Development Team 3) The Scrum Team 4) The Scrum Master

Answer 2. If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."

What is the essence of Scrum? Select the most appropriate option. 1) The Scrum Guide 2) A small team of people that is highly flexible and adaptive 3) The Development Team 4) The Scrum Master and the Product Owner

Answer 2. The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.

What does Burn-down Chart show? 1) Dependencies, start times and stop times for project tasks 2) How much work remains till the end of the Sprint 3) The evolution of the amount of uncertainty during a project 4) Hierarchy of tasks that comprise a project

Answer 2: Burn-down chart shows the evolution of remaining effort against time.

What are the three pillars that uphold Scrum? 1) Self-organization 2) Cross-functionality 3) Inspection 4) Transparency 5) Adaptation 6) Agility

Answer 3, 4 and 5. Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

What is Scrum? 1) A software development methodology which is intended to improve software quality. 2) A sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards. 3) A framework within which people can address complex adaptive problems, while delivering valuable products.

Answer 3. A framework within which people can address complex adaptive problems, while delivering valuable products.

Who is responsible for crafting the Sprint Goal at the Sprint Planning? 1) The Key Stakeholders 2) The Scrum Master 3) The Scrum Team 4) The Development Team 5) The Product Owner

Answer 3. After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.

Who creates the increment? 1) The Scrum Team 2) The Product Owner 3) The Development Team 4) The Scrum Master 5) The Development Team and The Product Owner

Answer 3. Only members of the Development Team create the Increment.

Who is responsible for managing the Product Backlog? 1) The Development Team 2) The Scrum Master 3) The Product Owner 4) The Key Stakeholders

Answer 3. The Product Owner is the sole person responsible for managing the Product Backlog.

What is the result of the Sprint Review? 1) A list of improvements that the Scrum Team will implement in the next Sprint 2) Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved 3) A revised Product Backlog that defines the probable Product Backlog items for the next Sprint 4) Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog

Answer 3. The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.

Products have one Product Backlog, regardless of how many teams are used. Any other setup makes it difficult for the Development Team to determine what it should work on.**When multiple teams work together on the same product, each team should maintain a separate Product Backlog. A) True B) False

Scrum Master is NOT a management role. a. True b. False

Who is responsible for all estimates in the Product Backlog? 1) The Product owner and the Scrum Master 2) The Scrum Team 3) The Scrum Master and the Development Team 4) The Development Team 5) The Product Owner 6) The Product owner and the Development Team 7) The Scrum Master

Answer 4. The Development Team is responsible for all estimates in the Product Backlog. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.

Who is responsible for managing the Product Backlog? 1) The Key Stakeholders 2) The Development Team 3) The Scrum Master 4) The Product Owner

Answer 4. The Product Owner is the sole person responsible for managing the Product Backlog.

Who has the authority to cancel the Sprint? 1) The Development Team 2) The Product Owner and the Scrum Master 3) The Key Stakeholders 4) The Scrum Master 5) The Product Owner

Answer 5. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.

Who is responsible for monitoring progress toward high-level goals? 1) The Scrum Master and The Development Team 2) The Product Owner and The Development Team 3) The Product Owner 4) The Scrum Master 5) The Development Team 6) The Scrum Team

Answer 5. The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

In the first part of the Sprint Planning meeting, what is accomplished?

Answer: All of the above - Items are selected from the Product Backlog - The Development Team decides how much work can be accomplished - The Scrum Team defines the Sprint Goal

What should be taken into account for the Definition of "Done"? Select the two most appropriate items. 1) Definition of "Done" of other Scrum Teams working on the same Product 2) Advice of the Scrum Master 3) Definition of "Done" of other Scrum Teams working on other products Experience of the Product Owner 4) Conventions, standards and guidelines of the Organization

Answers 1 and 4. If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."

How does the Scrum Master serve the Organization? Select the three most appropriate answers. 1) Leading and coaching the organization in its Scrum adoption 2) Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization 3) Planning Scrum implementations within the organization 4) Mixing experienced developers and junior specialists across different Development Teams in the organization to speed up Scrum adoption 5) Making sure the key stakeholders are invited on all Scrum Reviews within organization

Answers 1, 2 and 3. The Scrum Master serves the organization in several ways, including: ◦ Leading and coaching the organization in its Scrum adoption; ◦ Planning Scrum implementations within the organization; ◦ Helping employees and stakeholders understand and enact Scrum and empirical product development; ◦ Causing change that increases the productivity of the Scrum Team; and, ◦ Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

Check all the formal opportunities to inspect and adapt. 1) The Daily Scrum 2) The Sprint 3) The Sprint Retrospective 4) The Sprint Review 5) The Sprint Planning

Answers 1, 3, 4 and 5. Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection.

What are the characteristics of a Development Team? Select three most appropriate choices. 1) Accountability belongs to the Development Team as a whole Having the Scrum Master as a part-time Developer in the Development Team 3) Having at least one test engineer in the Development Team 4) Scrum recognizes no sub-teams in the Development Team 5) Scrum recognizes no titles for Development Team members

Answers 1, 4 and 5. Development Teams have the following characteristics: ◦ They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; ◦ Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; ◦ Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person; ◦ Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and, ◦ Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

Imagine you are a Scrum Master in a small Organization that tries to adopt Scrum. There are 10 developers and the Product Owner. How can they be divided into teams? Choose all applicable options: 1) 2 teams of 6 and 4 people (because it is good to have a separate QA team) 2) 2 teams of 6 and 4 people (after a short meeting the developers decided this is the best option) 3) 1 team of 10 people (because there is no reason to divide) 4) 3 teams of 4, 3 and 3 people (each team is cross-functional)

Answers 2 and 4. Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.

What does Product Backlog management include? Select three most applicable items. 1) Presenting Product Backlog items to the Key Stakeholders 2) Optimizing the value of the work the Development Team performs 3) Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next 4) Ordering the items in the Product Backlog to best achieve goals and missions 5) Moving Product Backlog items into the Sprint Backlog

Answers 2, 3 and 4. Product Backlog management includes: ◦ Clearly expressing Product Backlog items; ◦ Ordering the items in the Product Backlog to best achieve goals and missions; ◦ Optimizing the value of the work the Development Team performs;

It is mandatory for the Product Owner to monitor and share progress of Product Backlog through?

Any projective practice based on trends of work completed and upcoming work

No one is allowed to participate in the Daily Scrum, but the developers.

Anyone can "attend" the Daily Scrum, but only the developers are allowed to "participate".

How much work must a Development Team do to a Product Backlog item it selects for a Sprint?

As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done".

As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of done.

How often should Development Team membership change?

As needed, while taking into account a short term reduction in productivity.

When may a Development Team change its engineering practices?

As needed, while taking into account a short term reduction in productivity.

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

As soon as possible after they are identified.

As the Development Team starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do?

As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.

impediments and blockers

As soon as the first Sprint has started, each Team Member can add the so-called impediments (Blockers) to a list. Each Team Member announces their Blocker for the implementation of a task as soon as it arises and places it in the list of Blockers. It is the task of the Scrum Master to eliminate these Blockers. An impediment is anything that slows down or diminishes the pace of the Team. When the Team is confronted with impediments (or obstacles), the Team could move forward but in advancing they may generate waste. Or the whole process of making progress is more difficult than it should be (think about the little girl in the picture). In contrast, a blocker is anything that stops the delivery of the product. Without the elimination of the blocker, the Team cannot advance at all. We can think of them as internal and external impediments.. on internal impediments we still have control since things gtin delayed cz team's internal reasons and we can do something about it but if the impediments are external (blockers), things arent our control anymore. so it becomes a kind of blocker..without it team cant even move forward..

A member of the Development Team takes the Scrum Master aside to express his concerns about data security issues. What should the Scrum Master do?

Ask the person to share the issue with the team as soon as possible.

Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal? 1) The Product Owner 2) The Scrum Team 3) The Development Team 4) The Scrum Master 5) The Product Owner and the Development Team

At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be summed. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress.

Who is managing the progress of work during a Sprint?

Who monitors the remaining work of the Product Backlog?

At any point in time, the total work remaining to reach a goal can be summed. The Product Owner tracks this total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

Program Level

At the Program level, SAFe focuses on the principle of alignment as the efforts of a number of agile teams are integrated to create customer value. VersionOne helps you plan and track your program increments, and coordinate all of the activities of your release trains.

The process of regular inspection and adaptation employs knowledgeable and skilled inspectors. What are two ways in which the Product Owner takes the lead in the inspection process?

At the Sprint Review the Product Owner shares the current state of Product Backlog, which, combined with the inspection of the Increment, leads to an updated Product Backlog. The Product Owner invites stakeholders to the Sprint Review to learn how the current state of the marketplace influences what is the most valuable thing to do next

For the purpose of transparency, when does Scrum say a new increment of working software must be available?

At the end of every Sprint

For the purpose of transparency, when does Scrum say a new increment of working software must be available?

At the end of every Sprint.

Daily Scrums are held at the same time and same place every day. a. False b. True

How many people can there be in a Development Team? a. 3 to 11 b. 3 to 9 c. 5 to 12 d. 5 ± 3 e. 3 to 10

The Daily Scrum is held at the same time and place each day to reduce complexity.**Why is the Daily Scrum held at the same time and same place? A) The place can be named. B) The consistency reduces complexity. C) The Product Owner demands it. D) Rooms are hard to book and this lets it be booked in advance.

The Product Owner is not collaborating with the developers during the Sprint. What would you do as the Scrum Master? a. Talk to the functional manager of the Product Owner. b. Bring up the issue in the next Sprint Retrospective. c. Nominate someone else as the proxy Product Owner. d. Cancel the Sprint and start training the Product Owner

The Scrum Master should cancel the Sprint if the Product Owner has not created the Sprint Goal before Sprint Planning. a. True b. False

Velocity of Scrum Teams should be normalized, so that management can measure and compare their performance. a. True b. False

What does a burn-down chart measure? a. The amount of business value delivered to the customer b. Work remaining across time c. Work that is done based on the Definition of Done d. Cost of the project across time

When multiple teams are working on a project, they should select work from the same Product Backlog. a. False b. True

Which of the following best describes Sprint Planning? a. What to do and who will do it b. What can be done and how to do it c. Who will be in the team this Sprint? d. What went wrong in the last Sprint and what to do about it

Which of the following best describes transparency? a. The whole process should be visible to stakeholders. b. Significant aspects of the process must be visible to those responsible for the outcome. c. The process should be visible, and understood by key stakeholders. d. The whole process should be visible to everyone.

Which of the following best describes transparency? a. The whole process should be visible to stakeholders. b. Significant aspects of the process must be visible to those responsible for the outcome. c. The whole process should be visible to everyone. d. The process should be visible, and understood by key stakeholders.

Which of the following describes the relationship between the Product Backlog and changes in the project environment? a. There's no effect on the Product Backlog. b. It evolves to reflect the changes c. The Product Backlog should be kept high-level enough to tolerate such changes. d. The old baselined Product Backlog would be saved, and a new one would be created for the rest of the project.

Which of the following is correct about the Product Owner role? a. Creates User Stories b. Orders the Product Backlog items c. Runs the Daily Scrum d. Prioritizes tasks in the Sprint Backlog

Which of the following is required by Scrum? a. Definition of Ready b. Having timeboxed events c. User Stories d. Burn-down charts

Which statement is NOT correct about Daily Scrums? a. Only the developers participate in the meeting. b. The Product Owner should attend the meeting. c. It's held at the same time and place every day. d. It's always a 15-minute timeboxed event, no matter how many developers there are, or how long the Sprint is.

Who estimates the size of the Product Backlog items? a. The Product Owner b. The Development Team c. The Scrum Master d. The Scrum Team

Who is accountable for ordering the Product Backlog items? a. The whole Scrum Team b. The Product Owner c. The Business Analyst d. The Project Manager e. The customer f. Stakeholders

Why are Daily Scrums held at the same time and same place? a. So that everyone will know where and when to find the developers b. To reduce complexity and wasted time c. To be able to book rooms upfront d. To make sure everyone has to be there

Which of the following should NOT change during the Sprint? a. Sprint Backlog b. Expected quality c. Product Backlog

B (b) The level of expected quality stays the same during the Sprint.

The Development Team has realized that one of the planned works in the Sprint Backlog is not needed anymore. What should they do? a. Keep it, but inform the Product Owner. b. Remove it if it's OK with the Product Owner. c. Ask the Product Owner to remove it. d. Inform the Product Owner, so that he/she can cancel the Sprint.

B (b) You don't even have to ask the Product Owner, if it's about a purely technical decision. Their consultation is needed when it's about functions/features. Think of it as a technical task in the Sprint Backlog. There are two elements in the Sprint Backlog: items selected from the Product Backlog and tasks created by decomposing those items. Tasks are always changing, and therefore, we can't say that Sprint Backlog doesn't change during the Sprint. The old-fashioned approach is to keep the items fixed, to avoid distractions, but Scrum.org doesn't believe in that anymore, so it's fine for them to change the items too.

Which statement does NOT explain when an item is considered complete? a. When everything is Done based on the Definition of Done b. When the customer approves its completeness c. When it's potentially usable for the end users, if it becomes part of the Increment d. When it can be part of a potentially releasable Increment

B (b) They can still miss something. On the other hand, if the test is focused on the unit, what about testing the integrated solution? It may break something.

Scaled Scrum is one that conforms to Scrum and uses more than one team for one or more Sprints. a. False b. True

B 1. Scaled Scrum conforms to Scrum; i.e. it's compatible with Scrum. 2. It's called Scaled Scrum when there are more than one team; however, it's not necessary to have more than one team in all Sprints; it can be for some of them.

What is a proper role of a PMO in a company that uses Scrum? a. The PMO will be responsible for making higher level decision in the project. b. Manage portfolios and programs and facilitate the application of techniques that complement Scrum. c. The PMO should manage and help the Scrum Masters.

B Remember that there are limits to the self-organization of the team, and the important thing is to have power within the borders of the project. However, each project is run in a wider organization with multiple levels of management that impact the project, and it's not possible or even acceptable to reject that structure, as long as it doesn't block internal self-organization of the team.

Which of the following can be considered a real output of the Sprint? a. New features that are ready for integration b. A potentially releasable piece of software c. A document that describes the architecture of the software and can be used by the developers in the rest of the project d. UML diagrams

B A real output is the Increment: a piece of working software that is Done based on the Definition of Done. From a wider perspective, you can also consider the feedback that is generated by the customer and the improvements you plan in the Sprint Retrospective as real outputs; but a question like this is focused on checking if you can distinguish DONE items from technical tasks; the former is valuable for us, while the latter is just the means.

Which statement is correct about the Product Backlog? a. It has all the details. b. It has just enough detail. c. It has no detail.

B Both Sprint Backlog and Product Backlog evolve during their lives, and the amount of information grows as time passes. So, at each point in time, they don't have as much detail as they will have in the future (also imaginary future). On the other hand, we never add all the details there. For example, it's common to say that a User Story doesn't provide all the information, but is an excuse for people involved in the project to have communications around a certain topic. The details are in those communications, and are not completely captured in the backlog.

Which statement is correct about the Sprint Backlog? a. It has all the details. b. It has just enough detail. c. It has no detail.

Which statement is NOT correct about Daily Scrums? a. Only the developers participate in the meeting. b. It's timeboxed for 2 minutes per developer. c. It's held at the same time and place every day. d. It's always a 15-minute timeboxed event, no matter how many developers there are, or how long the Sprint is.

B Did you notice the word "not" in the question?

Scrum Master is NOT a management role. a. True b. False

B Did you notice the word "not" in the question? The Scrum Master role is considered a management role, but they manage the process, not the people.

The Product Owner and Scrum Master should NOT be part of the Development Team. a. True b. False

B Did you notice the word "not" in the statement? OK, this is usually tricky! Think of it like this: is it correct to say that they should not be part of the Development Team? No, this is not correct (because they can be part of the team), therefore, the statement is false. What some people do is think about the opposite statement, and get confused. Note that the opposite of this statement is NOT "the Product Owner and Scrum Master should be part of the Development Team". The correct opposite of "should not" is "could" or "can" or "may", NOT "should". One person can have more than one role in Scrum (not recommended, but allowed).

The Product Owner should determine how many items should be selected for the Sprint Backlog. a. True b. False

B Done by the developers

During a Sprint, a Development Team determines that it will not be able to finish the complete forecast. Who should be present to review and adjust the Sprint work selected? A) The Scrum Master, the project manager and the Development Team. B) The Product Owner and the Development Team. C) The Product Owner and all stakeholders. D) The Development Team.

B During the Sprint, scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

What happens between two Sprints? a. Getting customer approval for the previous Increment b. Nothing! c. Refactoring the previous Increment d. Product Backlog Refinement

B Each Sprint starts immediately after the previous one; there's no space between the two.

When does the next Sprint begin? a. When the customer approves the previous Increment b. Immediately after the previous Sprint c. When the Product Owner authorizes d. When the Product Backlog is refined and items at the top are "ready"

B Each Sprint starts immediately after the previous one; there's no space between the two.

Which statement best describes the Sprint Review? A) It is a mechanism to control the Development Team's activities during a Sprint. B) It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. C) It is a demo at the end of the Sprint for everyone in the organization to check on the work done.

B Every event in Scrum, besides the Sprint which is a container for the other events, is an opportunity to Inspect AND Adapt.

The Scrum Master shouldn't allow the developers to start working without having the tasks identified and assigned. a. False b. True

B First of all, the Scrum Master doesn't order people to do something; the Scrum Master teaches them and coaches them to understand how it should work, and convinces them to do the right thing. The Product Owner can't order developers to do things either. Second, most of the tasks are identified and assigned gradually during the Sprint.

The Scrum Master shouldn't allow the developers to start working without having the tasks identified and assigned. a. True b. False

The Development Team is ready to start the first Sprint, but the Product Backlog is not ready yet. What should the Product Owner do? a. Ask the developers to help you refine the Product Backlog instead of starting the first Sprint. b. Let the team start the first Sprint, and continue refining the Product Backlog. c. Let the Sprint begin, but only with the goal of completing the Product Backlog.

B First, remember that the Product Backlog is never complete, and you don't have to wait until you have everything in the Product Backlog to start the first Sprint. However, this question says that the backlog is not "ready", which probably means that the items at the top are too large and/or unclear. Again, having unready items is not a reason to wait (still undesirable though); you can refine them during the Sprint.

The Development Team is ready to start the first Sprint, but the Product Backlog is not ready yet. What should the Product Owner do? a. Let the Sprint begin, but only with the goal of completing the Product Backlog. b. Let the team start the first Sprint, and continue refining the Product Backlog. c. Ask the developers to help you refine the Product Backlog instead of starting the first Sprint.

What is the main reason for the Scrum Master to be at the Daily Scrum? a. To get a report on progress of the Sprint. b. It's not necessary for them to be in the meeting. c. To track changes to the Sprint Backlog. d. To tell developers what to do.

B In general, Daily Scrum is for the Development Team, which means that only the developers "participate" (talk). Others can "attend" (watch), but they won't "participate" (talk). Well, unless it's about a Scrum Master facilitating the meeting (not so common), in which case they will talk a little ;) However, this contribution of the Scrum Master is about the context, not the content.

Scaled Scrum is one that conforms to Scrum and uses more than one team for all Sprints. a. True b. False

B It can be for only a few Sprints. 1. Scaled Scrum conforms to Scrum; i.e. it's compatible with Scrum. 2. It's called Scaled Scrum when there are more than one team; however, it's not necessary to have more than one team in all Sprints; it can be for some of them.

A 2x increase in the number of developers will double productivity. a. True b. False

B It can increase productivity in the long-term, but probably not linearly.

Each Scrum Team should have a Scrum Master and a Product Owner. a. False b. True

B It doesn't mean that those people cannot be the Product Owner or Scrum Masters of other teams. When there are multiple teams, multiple "people" can work as the Scrum Master, but they will all have one Product Owner. Still, the statement stays valid: there's one person you can identify as your Product Owner.

It's required to use User Stories in Scrum. a. True b. False

B It's a good idea to use User Stories to form the Product Backlog items, but it's not mandatory.

Sprint Review is an informal meeting. a. False b. True

B It's not a formal meeting, in the sense that you and the customer won't work on approval/acceptance of the product and exchanging signatures (that would block feedback generation). This may be confusing, because on the other hand, Sprint Review (and other events) are considered "formal opportunities for inspecting and adapting". The word "formal" has been used for two different meanings in the exam, the former is what we have in this question, and the latter simply means "serious"! So, make sure you understand the context of the question to interpret words such as "formal".

It's allowed to have Team Leaders when many developers are working on a complex project. a. True b. False

B It's not allowed to introduce new roles or titles in Scrum.

The Development Team should have a Team Leader to improve communications and collaboration. a. True b. False

B It's not allowed to introduce new roles or titles in Scrum.

When multiple teams are working on the same product, their Sprints should start and end at the same time. a. True b. False

B It's not mandatory in Scrum.org to start and end the Sprints at the same time. That makes it much more difficult to manage the whole project. It's not mandatory, because you may need it in certain cases; maybe some teams are working on parts of the project that need longer Sprints (four-week), while others need shorter ones (two-week) for shorter feedback loops.

Who is responsible for explaining the Product Backlog items? a. The Development Team is self-organized and has to talk to anyone necessary, and find out the meanings of items. b. Product Owner c. Customer d. Scrum Master e. User representative(s)

B It's one of the responsibilities of the Product Owner to explain the items and make sure that everyone has the right understanding

Cross-functional teams are optimized in a technical layer of a system. a. True b. False

B It's the opposite; being cross-functional means that you can work (as a team) comfortably on all technical layers of the system. A cross-functional team is one that has all types of expertise that is required to develop the product. Note that this is about the team as a whole, not individual team members.

A Product Owner who used to be a project manager in the past is using burn-up charts instead of burn-down charts. Is that acceptable? a. Burn-up charts are used in traditional methods, and they should be replaced by burn-down charts. b. There's nothing wrong with it.

B It's up to the Product Owner to decide how they want to measure and visualize performance.

When multiple teams are working on the same product, one person can be a member of more than one Development Team. a. False b. True

B None of the Scrum roles are necessarily full-time, and the person can occupy more than one role (e.g. both Scrum Master and developer), or be a developer in more than one team. E.g. there may be a special expertise that is needed in multiple teams, but its not needed in a full-time basis. So, one person can provide that special type of expertise to multiple teams.

The Product Owner can delegate some of their responsibilities to the developers. a. False b. True

B Product Owners are allowed to delegate some of their responsibilities to other team members. If they do, the Product Owner stays accountable.

What type of test should be done during the Sprint? a. All tests, except for user acceptance tests b. Every type of test c. Unit tests d. All tests, except for integration tests

B Remember that the Increment has to be "Done", and potentially releasable. It means that all tests should be done.

Who's responsible for quality? a. Testers b. All developers c. Team leaders

B There are no people "titled" as testers, because we don't have extra roles and titles in Scrum. However, there can be "developers" who are expert in testing. Remember that everyone in the Development Team is called a "developer".

Which statement is least accurate about the definition of "Done"?

Definition of Done is created by the Development Team

What's the role of a PMO in an organization that only uses Scrum for project delivery? a. The PMO should manage and help the Product Owners. b. Manage portfolios and programs and facilitate the application of techniques that complement Scrum. c. The PMO will be responsible for making higher level decision in the project. d. There's no place for a PMO in such an organization.

Scrum is a methodology for developing complex products. a. True b. False

B Scrum is "considered" a framework, not a methodology, process, techniques, etc. It can be used to develop new products or maintain/sustain existing ones.

Scrum is a process for developing complex products. a. True b. False

B Scrum is "considered" a framework, not a methodology, process, techniques, etc. It can be used to develop new products or maintain/sustain existing ones.

It's up to the self-organizing team to decide which Scrum artifacts are needed in the project. a. True b. False

B Self-organization is not unlimited; e.g. you should follow the Scrum framework.

It's up to the self-organizing team to decide which Scrum events are needed in the project. a. True b. False

B Self-organization is not unlimited; e.g. you should follow the Scrum framework.

What happens if we forecast that some of the work defined in the Sprint Backlog won't be done by the end of the Sprint? a. Outsource part of the work to other teams or parts of the organization. b. They will deliver as much as they can, and they learn more about how many items they can deliver in the next Sprints. c. Work overtime and try to complete all items. d. The remaining items will be moved to the next Sprint Backlog.

B Some people think that a successful team is one that can complete all the work in the Sprint Backlog, but this is not true. To the contrary, it probably means they are too conservative in the number of items they select for the Sprint, which in turn may reduce their productivity because of the Parkinson's Law and the Student Syndrome. Nothing bad happens if some items are not done by the end of the Sprint, and no one should blame the team; the Sprint Backlog is just a rough estimate of what they can do.

When does a Development Team member become the sole owner of a Sprint Backlog item? A) At the Sprint planning meeting. B) Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be implemented by an individual development team member. C) Whenever a team member can accommodate more work. D) During the Daily Scrum.

B Sprint Backlog and all of its items are collectively owned by the Development Team. No individual team member can claim ownership over an item as this would block communication and collaboration.

The time-box for the Sprint Planning meeting is? A) 4 hours. B) 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. C) Whenever it is done. D) Monthly.

B Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

The maximum length of the Sprint Review (its time-box) is: A) 2 hours. B) 4 hours for a monthly Sprint. For shorter Sprints it is usually shorter. C) As long as needed. D) 1 day. E) 4 hours and longer as needed.

B Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

Having the team members and a complete Product Backlog are the only things needed to start the project. a. True b. False

B The Product Backlog is never complete.

What is the main reason for the Scrum Master to be at the Daily Scrum? A) To make sure every team member answers the three questions. B) He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum. C) To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down. D) To gather status and progress information to report to management.

B The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.

The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. Based on this, which of the following is FALSE? A) The Product Owner can help clarify or optimize the Sprint when asked by the Development Team. B) The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint. C) As a decomposition of the selected Product Backlog Items, the Sprint Backlog changes and may grow as the work emerges. D) The Development Team may work with the Product Owner to remove or add work if it finds it has more or less capacity than it expected.

B The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

The Scrum Master should NOT allow the Sprint Planning meeting to start when the Sprint Goal is not ready. a. True b. False

B The Sprint Goal is prepared during the Sprint Planning meeting. Also, Scrum Masters don't order people, they teach and convince people to do the right thing.

How does the Product Owner determine the number of items for the Sprint Backlog? a. Based on a combination of velocity and team capacity b. They don't do it! c. Based on the feedback received from the customer in the previous Sprint Review d. Based on velocity

B The developers decide how many items to select for the Sprint Backlog, not the Product Owner.

The performance of the Sprint should be measured at least... a. Once a week b. Once a day c. Before or after each release d. Once per Sprint

B The performance of the project is measured at least once per Sprint, and the Sprint performance is measured daily.

It is mandatory that the product increment be released to production at the end of each Sprint. A) True B) False

B The product increment should be usable and releasable at the end of every Sprint, but it does not have to be released.

All Development Team members should be cross-functional. a. True b. False

B The team as a whole has to be cross-functional, not the individuals inside the team.

The Sprint Backlog is frozen after Sprint Planning. a. True b. False

B There are two elements in the Sprint Backlog: items selected from the Product Backlog and tasks created by decomposing those items. Tasks are always changing, and therefore, we can't say that Sprint Backlog doesn't change during the Sprint. The old-fashioned approach is to keep the items fixed, to avoid distractions, but Scrum.org doesn't believe in that anymore, so it's fine for them to change the items too.

The Sprint Backlog stays fixed after Sprint Planning. a. True b. False

The whole Sprint Backlog is defined in the Sprint Planning meeting. a. True b. False

Which role is the equivalent of project manager in Scrum? a. Scrum Master b. None of them c. Product Owner d. Development Team e. Team Leader

B There's no project manager role in Scrum, and it's not allowed to add new role to the existing three. Also, none of those three roles are the equivalent of a project manager; project management activities are distributed among all of them. This is only about the project level; you can always have higher management levels (e.g. program management), and those "can" be compatible with what you do in your Scrum projects.

The Development Team is free to change their engineering practices whenever they want. a. False b. True

B They are the technical people in the project, which makes them the best people to decide about engineering practices, and they are also self-organized.

There can be multiple Definitions of Done when multiple teams are working on the same product. a. False b. True

B They can have different Definitions of Done, as long as they are compatible with each other and capable of creating integrated Increments. Note: it may seem that the Scrum Guide says there's only one Definition of Done for multiple teams, but this is not the case. Having this flexibility can help, because, for example, one team may want to have extra tests. There's no harm in that, and yet, it impacts their Definition of Done.

Items on the Sprint Backlog are, on average, larger than those on the Product Backlog. a. True b. False

B This is how it works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at the top of the list, you have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of this way of refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint Backlog are, on average, smaller than items on the Product Backlog.

On average, items on the Sprint Backlog tend to be ______ a. The same size as those on the Product Backlog b. Smaller than those on the Product Backlog c. Larger than those on the Product Backlog

How many hours per day should a Development Team member work? a. Normally, 40 hours a week b. At a constant pace c. Between 6 and 16 hours, depending on the situation d. At least 6 ideal man-hours

B This is one of the 12 Agile principles.

At least one high-priority process improvement item exists in each Sprint Backlog. a. False b. True

B This is one of the statements added to the latest update of Scrum Guide: At least one high-priority process improvement item exists in each Sprint Backlog. It was a little unexpected, because it's mixing content related to the product with the content related to the process in the Sprint Backlog; but, well, that's how it is now.

Each Sprint Backlog contains an item about improving the way we work, instead of the features for the product. a. False b. True

The items selected from the Product Backlog for the Sprint Backlog should be "ready". a. True b. False

B We do have an idea of when items are ready to be selected for the Sprint, and it's considered in Product Backlog Refinement to make sure all items at the top of the Product Backlog are ready. However, a concept of Definition of Ready is not accepted in Scrum.org, because the practical implication may be that an item at the top of the Product Backlog will not be selected for the Sprint because it's not ready, while we always want to follow the order of items, and if something is not ready, we can still select it for the Sprint and then refine it during the Sprint.

Timeboxing helps everyone focus on the same problem at the same time. a. False b. True

B When an event is timeboxed, you don't have a lot of time to spend on fancy aspects of features, and you have to focus and help each other in order to to get as many items Done as possible.

One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily Scrum? (choose 2)

B) A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal E) New impediments for the Scrum Master to take care of

Which two of the following are true about the Scrum Master role?

B) The Scrum Master teaches the Development Team to keep the Scrum meeting to their timebox E) The Scrum Master helps outside the team interact with the Scrum Team

Why is the Daily Scrum held at the same time and same place?

B) The consistency reduces complexity.

What are two good ways to handle security concerns? a. Dedicate a certain portion of the team capacity to working on those concerns. b. Add them to the Product Backlog. c. Add them to the Definition of Done. d. Get help from responsible departments to ensure those concerns.

B, C

What are two good ways to handle security concerns? a. Have special Sprints that ensure those concerns. b. Add them to the Product Backlog. c. Add them to the Definition of Done. d. Dedicate a certain portion of the team capacity to working on those concerns.

B, C

Which two of the following should NOT change during the Sprint? a. Product Backlog b. Sprint Goal c. Composition of the team d. Sprint Backlog

B, C

Which two statements are correct about the Definition of Done? a. Describes what has to be done during the Sprint. b. Varies depending on the project. c. Used by the developers to forecast how many items they can pick for the Sprint. d. It defines when the Increment should be released.

B, C

Which two statements are correct about non-functional requirements? a. They will be in the Sprint Backlog, but not the Product Backlog. b. Some of them can be added to the Definition of Done. c. Some of them can be added to the Product Backlog. d. They can be added to a separate backlog to be used during all Sprints. e. Some of them can be controlled by the QA department of the organization.

B, C (b) E.g. security, scalability, maintainability (c) E.g. something related to performance of a certain part of the software

Which two of the following are mandatory elements in Scrum? a. Face-to-face communications b. Definition of Done c. Sprint Planning d. Planning Poker e. Value Points

B, C Only the roles, events, and artifacts (+ Definition of Done and progress measurement) are mandatory.

Which two of the following are formal opportunities for inspecting and adapting? a. Product Backlog Refinement b. Sprint Review c. Sprint Planning d. Burn-down chart

B, C Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are "formal opportunities for inspecting and adapting", and are considered "feedback loops".

Which two of the following may be done in the Sprint Retrospective meeting? a. Discuss the next Sprint goal b. Discuss the timeboxed duration of Sprints c. Discuss the composition of the team d. Discuss the Product Backlog items for the next Sprint e. Refining the Product Backlog

B, C Sprint Retrospective is about the way we work. It's about the things that affect the product, but we don't discuss the product directly. In general, it's about the context, not the content. For example, we can talk about the way Product Backlog is refined, but we won't refine the Product Backlog in the Sprint Retrospective meeting.

Which three statements show the result of changing Scrum terminology while implementing it in the organization? a. It's necessary to tailor Scrum to suit the project. b. Management may feel less enthusiastic about the change. c. The change might not be obvious to everyone, and therefore very little change actually happens. d. The change might not be obvious to everyone, and some benefits may be lost. e. They will get better results adopting Scrum this way.

B, C, D Scrum is a simple framework rather than a comprehensive methodology, and it contains only the necessary minimums that you need in every project. So, instead of a normal tailoring, you will follow everything that is described in Scrum, and suit it to your project by the practices and techniques that you add; e.g. Planning Poker, Pair-Programming, and Test-Driven Development. When it comes to terminology, Scrum.org believes that it's better if you don't change them, for the reasons that you see in the answers.

Which three of the following are feedback loops in Scrum? a. Product Backlog Refinement b. Daily Scrum c. Sprint Planning d. Release Planning e. Sprint Review

B, C, E Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are "formal opportunities for inspecting and adapting", and are considered "feedback loops".

Which three statements are correct when four teams are working on a product? a. There is only one Sprint Backlog each Sprint. b. There can be multiple Scrum Masters. c. There is only one Product Backlog. d. There is only one Definition of Done. e. There can be multiple Product Owners. f. There is only one Product Owner.

B, C, F When there are n teams in the project (working on one product), there are: 1 Product Backlog n Sprint Backlogs each Sprint one or more Definitions of Done, as long as they are compatible with each other 1 integrated Increment each Sprint 1 Product Owner n Scrum Master roles which can be occupied by 1 or more Scrum Masters

What are two good ways to handle security concerns? a. Dedicate a certain portion of the team capacity to working on those concerns. b. Add them to the Definition of Done. c. Get help from responsible departments to ensure those concerns. d. Add them to the Product Backlog.

B, D

Which two of the following actions may a Scrum Master take in starting up a project? a. Ask the team to work together and prepare a complete Product Backlog. b. Ask the Development Team members to introduce themselves to each other and tell about their skills and background. c. Ask the development managers to introduce their departments and capabilities. d. Ask the Development Team to discuss and identify the way they are going to develop the product. e. Ensure that team members have clear roles and responsibilities.

B, D

Which two of the following are benefits of self-organization? a. Increased cross-functionality b. Increased buy-in c. Increased respect d. Increased creativity e. Increased predictability

B, D

A Scrum Master is introducing Scum to a new Development Team. The Development Team has decided that a retrospective is unnecessary. What action should the Scrum Master take?

Being facilitating productive and useful retrospectives

Which two of the following can be considered real outputs of the Sprint? a. A plan for the next Sprints b. A few Done features that are added to the previous version of the software c. UML diagrams d. A piece of software that is usable by the end users

B, D A real output is the Increment: a piece of working software that is Done based on the Definition of Done. From a wider perspective, you can also consider the feedback that is generated by the customer and the improvements you plan in the Sprint Retrospective as real outputs; but a question like this is focused on checking if you can distinguish DONE items from technical tasks; the former is valuable for us, while the latter is just the means.

Which two of the following should NOT change during the Sprint? a. Product Backlog b. Expected quality c. Sprint Backlog d. Composition of the team

B, D Did you notice the word "not" in the question? Those that stay fixed during the Sprint are needed to avoid distractions, and create a more productive environment. After all, Sprints are not so long that they create problems.

Which two statements are correct about the number of Product Owners when there are three products being developed using Scrum? a. There should be one Product Owner for each product. b. There can be a single Product Owner for all products. c. There should be a single Product Owner for all products. d. There can be a different Product Owner for each product.

B, D The basic rule in Scrum.org is that when there is one product (=one project) you should have only one Product Backlog and one Product Owner, even if there are multiple teams working on the project. However, this question is about multiple products (=multiple projects). In this case, there are 3 Product Owner positions in these projects, which can be occupied by three different people, or two, or one, since Product Owners don't have to work full-time on one project.

Which three Scrum values are demonstrated by focusing on the most valuable items first? a. Adaptation b. Courage c. Trust d. Focus e. Respect

B, D, E Scrum values are commitment, courage, focus, openness, and respect.

The Product Owner is not collaborating with the developers during the Sprint. Which two of the following actions would you choose as the Scrum Master? a. Talk to the functional manager of the Product Owner. b. Bring up the issue in the next Sprint Retrospective. c. Nominate someone else as the proxy Product Owner. d. Cancel the Sprint and start training the Product Owner. e. Coach the Product Owner to understand why collaboration is important in Scrum and how it can affect the value of the product.

B, E

Which two of the following is correct about the length of Sprints? a. Sprint length is set during Sprint Planning, and is long enough to develop all items in the Sprint Backlog. b. It's preferred to have Sprints with the same length. c. Depends on the position of the stars ;) d. Sprint length is set during Sprint Planning, and is long enough for programming and testing all items, but not for integrating them. e. All Sprints must be one month or less.

B, E (b) We don't change the timeboxed duration of Sprints on an ad hoc basis; maybe just a few times, based on what we've learned from the project. (e) One month is the maximum timeboxed duration for Sprints in Scrum.

Which two of the following are timeboxed? a. Release Retrospective b. Sprint Retrospective c. Product Backlog Refinement d. Sprint testing e. Sprint Planning

B, E The events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective) are timeboxed.

Which three statements are correct when four teams are working on a product? a. There is only one Sprint Backlog each Sprint. b. There are multiple Sprint Backlogs each Sprint. c. There can be multiple Product Owners. d. There is only one Definition of Done. e. There is only one Product Backlog. f. There can be multiple Scrum Masters.

B, E, F

Which three of the following may be done in the Sprint Retrospective meeting? a. Calculate Velocity b. Discuss tools used to communicate with remote team members c. Discuss the Product Backlog items for the next Sprint d. Refining the Product Backlog e. Discuss the timeboxed duration of Sprints f. Discuss the Definition of Done

B, E, F Sprint Retrospective is about the way we work. It's about the things that affect the product, but we don't discuss the product directly. In general, it's about the context, not the content. For example, we can talk about the way Product Backlog is refined, but we won't refine the Product Backlog in the Sprint Retrospective meeting.

Which two statements are correct about Product Backlog Refinement? a. Normally, it doesn't take more than 10% of the Product Owner's time. b. Normally, it doesn't take more than 10% of the developers' time. c. It can take as much time as needed. d. Normally, it shouldn't take more than 10% of the Scrum Team's time. e. It should be timeboxed for 8 hours or less. f. Multiple teams may participate in it.

B, F

What is the recommended size of a Scrum Team? A. 7-11 B. 3-11 C. 5-9 D. 3-9

B. 3-11 Cette question comporte un piège. Le scrum Guide définie la taille de la Development Team (et non celle du Scrum team) entre 3-9. Si l'on considère que le PO et le SM pourraient faire partie de la Dev team (car contribuant à la fabrication du produit) alors le minimum est bien « 3 ». Par contre si l'on prend le le cas où le PO et le SM ne font pas partie de l'équipe de développement (Dev Team), le maximum pour une Scrum team serait de 9+2 = 11.

Which of the following best describes an increment of working software ? A. UML diagrams that describe how to deliver functionality in future iterations. B. Additional features in a useable state that complement those delivered in previous iterations. C. A new user interface design for functionality delivered in previous iterations. D. A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists. E. An automated test suite to verify functionality delivred in previous iterations.

B. Additional features in a useable state that complement those delivered in previous iterations.

Which two activities will a Product Owner engage in during a Sprint? A. Update the Sprint burndown chart. B. Answer questions from the Development Team about items in the current Sprint. C. Run the Daily Scrum. D. Prioritize the Development Team's work on the Sprint Backlog. E. Work with the stakeholders.

B. Answer questions from the Development Team about items in the current Sprint E. Work with the stakeholders.

Which of the following is NOT a mandatory element in Scrum? a. Timeboxing the events b. Sprint Retrospectives c. Burn-down charts d. Sprint Reviews

C Did you notice the word "not" in the question? Only the roles, events, and artifacts (+ Definition of Done and progress measurement) are mandatory.

How much work must a Development Team do to a Product Backlog item it selects for a Sprint? A. Analysis, design, programming, testing and documentation. B. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of done. C. As much as it can fit into the Sprint. D. The best it can do given that it is usually impossible for QA to finish all of the testing that is needed to prove shippability.

B. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of done.

The Development Team cannot forecast how much work they can do in the upcoming Sprint, because of uncertainties in the Product Backlog that the Product Owner is not able to overcome. What two actions should the Scrum Master recommend? a. Cancel the Sprint and start the next one when the items are clear. b. Invite everyone to discuss this problem in the next Sprint Retrospective and try to find a solution. c. Ask the developers to come up with their best guess and do not worry about the capacity. d. Extend the duration of Sprint Planning and ask them to discuss the items more and get into agreement. e. Cancel the Sprint Planning meeting, give them some time to prepare, and then hold another Sprint Planning.

B. C

Acceptance criteria is a requirement for every Product Backlog item to be « Ready » for development. A. True B. False

B. False La notion de critère d'acceptance est liée à la notion d'User Story. Or, un PBI n'est pas forcément une User Story car Scrum n'oblige pas l'utilisation des US (ce pourrait être d'autres techniques de représentation des exigences : Use Case, Technical Story, etc.)

Non-functional requirements (NFRs) must be captured in the Definition of Done. A. True B. False

B. False NFRs (security, performance, etc.) can either fall within the product's scope, or they can express aspects of product quality. If they are a matter of scope then they should be included on the Product Backlog. If they are reflections of product quality then they may be incorporated into the Definition of Done.

Which of the following best describes Sprint Review? a. A demo at the end of the Sprint for everyone in the organization to see the Increment. b. A formal meeting to receive approval of the customer for the Increment c. An inspection of the Increment to collect feedback and see what to do in the next Sprint d. It's a controlling mechanism for evaluating the work of the developers.

Which technique is the LEAST productive way for the Scrum Master to ensure that the Development Team communicates effectively with the Product Owner? A. Teach the Product Owner about the technologies employed during the Sprints. B. Monitor communications between them. C. Act as a go-between for them. D. Teach the Team to talk in terms of business needs and objectives.

B. Monitor communications between them.

The part of the Sprint Backlog used to create the Sprint Burndown chart is: A. Actual cost of work performed. B. Remaining time required to complete the work. C. Budgeted cost of work performed. D. Remaining number of Product Backlog items.

B. Remaining time required to complete the work

Which of the following are TRUE about the Sprint Review? A. The Scrum Master demonstrates the product B. Stakeholders may attend C. The Product Owner presents what backlog items are Done » D. It should be a formal presentation

B. Stakeholders may attend C. The Product Owner presents what backlog items are Done »

Who creates a Product Backlog item's estimate? A. The Development Team, alone. B. The Development Team after clarifying requirements with the Product Owner. C. The Product Owner with input from the Development Team. D. The most senior people in the organization, including architects and subject matter experts. E. The Scrum Master.

B. The Development Team after clarifying requirements with the Product Owner.

What should management consider when determining how to scale Scrum? A. All of the answers are correct. B. The frequency of releases and the techniques used to integrate work. C. The budget to maintain multiple teams. D. The open space available for a number of teams

B. The frequency of releases and the techniques used to integrate work.

A Scrum Master is introducing Scrum to a new Development Team. The Development Team has decided that a retrospective is unnecessary. What action should the Scrum Master take?

Begin facilitating productive and useful retrospective

Who is responsible for the Burn-down chart and Gantt chart in Scrum?

Burn-down chart and Gantt chart are not mandatory in Scrum

role of BA

Business analysis is a key part of this product owner team and also, as you rightly mention, within the development team. 1. During a Sprint, BAs work on analyzing requirements for the Sprint(s) to follow. They do however actively support the Scrum team in case of (business related) questions/misunderstandings, etc. in the current Sprint. 2. Thus, BAs are not part of the core Scrum team, but rather part of the project team as a whole. This is because they are not working on the same context/goal within a Sprint. They are doing analysis for future Sprint(s), while the Scrum team works on items that have already been analyzed earlier (if not fully, at least at a great extent). 3. BAs work in analyzing requirements for future Sprint(s) is facilitated by the so called "backlog grooming cycles" that take place in parallel to the "Sprint cycles". BA to PO 1. Help the sponsor and product owner define and articulate the business problem and product vision 2. Elicit requirements using a variety of techniques, including facilitating cross-functional requirements workshops 3. Assist the product owner in developing user stories and the associated acceptance criteria so the delivery team will know when they're done. These criteria need to be more complete than, for example, "the order has been placed." I have found that creating specific criterion tends to be difficult for product owners. Trace user stories to business objectives and the product vision and throughout the sprint to ensure it's actually been delivered as imagined. Model the "as-is" and "to-be" business processes. Model the expected system interactions, particularly when software is being developed. Look for gaps in data requirements between what is in place and what is needed. Model the data requirements or work with the appropriate people to ensure that the data will support the new solution. Create mock-ups of the new user interfaces. Support the product owner by discussing business and technical impacts of and dependencies related to priority decisions. Assess how ready the organization is to accept the change.

What is the primary way a Scrum Master keeps a Development Team working at its highest level of productivity?

By facilitating Development Team decisions and removing impediments

What is the primary way a Scrum Master keeps a Development Team working at its highest level of productivity?

By facilitating Development Team discussions and removing impediments.

By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.

How do changes in the project environment impact the Product Backlog? a. There's no effect on the Product Backlog. b. The old baselined Product Backlog would be saved, and a new one would be created for the rest of the project. c. It evolves to reflect the changes d. The Product Backlog should be kept high-level enough to tolerate such changes.

How is budgeting done in Scrum? a. Budgeting is done based on the initial Product Backlog. b. Usually every day c. Ideally revised each Sprint to ensure value is being delivered. d. Scrum doesn't need a budgeting system.

How many hours per day should a Development Team member work? a. At least 6 ideal man-hours b. Between 6 and 16 hours, depending on the situation c. At a constant pace d. As much as needed for realizing the Sprint Backlog items by the end of the Sprint

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.**The three pillars of empirical process control are: A) Respect For People, Kaizen, Eliminating Waste B) Planning, Demonstration, Retrospective C) Inspection, Transparency, Adaptation D) Planning, Inspection, Adaptation E) Transparency, Eliminating Waste, Kaizen

Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.**Development Team membership should change: A)Every Sprint to promote shared learning. B) Never, because it reduces productivity. C) As needed, while taking into account a short term reduction in productivity. D) As needed, with no special allowance for changes in productivity.

The Product Owner is not collaborating with the developers during the Sprint. What would you do as the Scrum Master? a. Cancel the Sprint and start training the Product Owner. b. Talk to the functional manager of the Product Owner. c. Bring up the issue in the next Sprint Retrospective. d. Nominate someone else as the proxy Product Owner.

The Sprint Backlog makes visible all the work that the _________ identifies as necessary to meet the Sprint Goal. a. Scrum Master b. Scrum Team c. Development Team d. Product Owner

What do we do with Done items when the Sprint is cancelled? a. They should be moved to the next Sprint Backlog. b. They should be moved back to the Product Backlog, and will be taken care of in future Sprints. c. They will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them.

What happens to the Done Product Backlog items when the Sprint is cancelled? a. They should be moved back to the Product Backlog, and will be taken care of in future Sprints. b. They should be moved to the next Sprint Backlog. c. They will be reviewed, and if they are potentially releasable, the Product Owner typically accepts them.

When does a Scrum Master cancel a Sprint? a. When the Sprint Goal becomes obsolete b. When the forecast shows that we can't finish many of the items in the Sprint Backlog c. The Scrum Master doesn't have the authority to cancel the Sprint. d. When not enough resources are available for the project

Which of the following best describes Sprint Review? a. It's a controlling mechanism for evaluating the work of the developers. b. A formal meeting to receive approval of the customer for the Increment c. An inspection of the Increment to collect feedback and see what to do in the next Sprint d. A demo at the end of the Sprint for everyone in the organization to see the Increment.

Which of the following best describes transparency? a. The whole process should be visible to everyone. b. The whole process should be visible to stakeholders. c. Significant aspects of the process must be visible to those responsible for the outcome. d. The process should be visible, and understood by key stakeholders.

Which of the following can be considered a real output of the Sprint? a. A user interface layout that is designed for the whole solution b. New features that are ready for integration c. An Increment of working software d. A document that describes the architecture of the software and can be used by the developers in the rest of the project

Which of the following is NOT correct about the Scrum Master role? a. Makes sure that the Development Team has Daily Scrums b. Helps the organization implement Scrum c. Decides about engineering and development methods d. Facilitates the meetings as required or requested

Which of the following is NOT required by Scrum? a. Having timeboxed events b. Sprint Retrospectives c. Burn-down charts d. Definition of Done

Which of the following may change during the Sprint? a. Composition of the team b. Sprint Goal c. Product Backlog d. Expected quality

Which statement best describes the Product Backlog? a. Contains only small and clear items. b. It's used to create the project plan. c. The customer's change requests are reflected in it. d. Provides just enough information to enable the developers to design the product.

Which statement does NOT explain when an item is considered complete? a. When it can be part of a potentially releasable Increment b. When everything is Done based on the Definition of Done c. When the customer approves its completeness d. When it's potentially usable for the end users, if it becomes part of the Increment

Who is responsible for maximizing the value of the product? a. The Solution Architect b. The Development Team c. The Product Owner d. The Team Leader e. The Project Manager f. The whole Scrum Team

Who owns the Product Backlog? a. The whole Scrum Team b. The Development Team c. The Product Owner d. The Scrum Master

Who owns the Sprint Backlog? a. The whole Scrum Team b. The Scrum Master c. The Development Team d. The Product Owner

Which of the following is correct about the whole Scrum Team role? a. Measures the performance of the Sprint b. Makes changes to the Definition of Done c. Is designed in a way to maximize flexibility d. Is responsible for maximizing the value of the product

C The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

When does a Development Team cancel a Sprint? a. When not enough information is available for the items in the Sprint Backlog b. When the Sprint Goal becomes obsolete c. The Development Team doesn't have the authority to cancel the Sprint. d. When not enough resources are available for the project

C It's done by the Product Owner.

Who estimates the Product Backlog items? a. Stakeholders b. The Team Leader c. The Development Team d. The Business Analyst e. The Solution Architect f. The Scrum Master

C "Estimate" is about estimating size, unless otherwise specified.

What should the developers do when they have trouble delivering an item, because they don't understand it? a. Complete as much of the item as possible, and use it in the Sprint Review meeting to create a better understanding of what is needed. b. Ask the Scrum Master to remove this impediment. c. Collaborate with the Product Owner to see what's possible and desirable. d. Defer the item to the next Sprint.

C (c) The Product Owner is responsible for explaining the items.

What's the role of the Scrum Master during Sprint Retrospective? a. Summarize and report the results of the meeting to stakeholders b. They should not participate in this meeting c. Participate as a Scrum Team member d. To answer questions of the developers

C All three roles participate in the Sprint Retrospective, and they work together to see how they can improve the way they work in the next Sprint.

What's the role of the Scrum Master during Sprint Retrospective? a. They should not participate in this meeting b. Summarize and report the results of the meeting to stakeholders c. Participate as a Scrum Team member d. To answer questions of the developers

C All three roles participate in the Sprint Retrospective, and they work together to see how they can improve the way they work in the next Sprint.

Which statement is correct about the Sprint Backlog? a. It has no detail. b. It has all the details. c. It has just enough detail.

C Both Sprint Backlog and Product Backlog evolve during their lives, and the amount of information grows as time passes. So, at each point in time, they don't have as much detail as they will have in the future (also imaginary future). On the other hand, we never add all the details there. For example, it's common to say that a User Story doesn't provide all the information, but is an excuse for people involved in the project to have communications around a certain topic. The details are in those communications, and are not completely captured in the backlog

Which of the following is LEAST likely to be used by a Scrum team? a. Digital camera, task board b. Large screen, Planning Poker cards c. WBS, Gantt Chart d. Wiki, online forum

C Did you notice the word "least" in the question? WBS and Gantt Chart are mainly used in planning predictive projects rather than adaptive (Agile) ones.

Which of the following is NOT a mandatory element in Scrum? a. Sprint Retrospectives b. Daily Scrums c. Face-to-face communications d. Progress measurement

C Did you notice the word "not" in the question? Only the roles, events, and artifacts (+ Definition of Done and progress measurement) are mandatory.

Which two (2) things does the Development Team do during the first Sprint?

Deliver an increment of releasable software. Develop and deliver at least one piece of functionality.

Which element is NOT an attribute of Product Backlog items? a. Description b. Estimate c. Owner d. Value

C Did you notice the word "not" in the question? There are 3 pieces of information in each Product Backlog item: the description (in the form of a User Story, or otherwise), value, and estimate (i.e. estimated size). The ownership of items is shared, therefore, there's no need to record it in the item.

Which of the following describes the relationship between the Product Backlog and changes in the project environment? a. The Product Backlog should be kept high-level enough to tolerate such changes. b. The old baselined Product Backlog would be saved, and a new one would be created for the rest of the project. c. It evolves to reflect the changes d. There's no effect on the Product Backlog.

C E.g. there's a new regulation, and you have to comply with it in your software. You investigate the regulation and create new items that cover it, and you may also change some of the existing items.

Who is responsible for engaging stakeholders? a. The Project Manager b. The Development Team c. The Product Owner d. The Scrum Master

C Engagement of stakeholders is mostly about and around the Product Backlog items, and at least indirectly, about the value created in the project. That's why this is mainly the responsibility of the Product Owner to keep them engaged.

The Development Team is ready to start the first Sprint, but the Product Backlog is not ready yet. What should the Product Owner do? a. Let the Sprint begin, but only with the goal of completing the Product Backlog. b. Ask the developers to help you refine the Product Backlog instead of starting the first Sprint. c. Let the team start the first Sprint, and continue refining the Product Backlog.

C First, remember that the Product Backlog is never complete, and you don't have to wait until you have everything in the Product Backlog to start the first Sprint. However, this question says that the backlog is not "ready", which probably means that the items at the top are too large and/or unclear. Again, having unready items is not a reason to wait (still undesirable though); you can refine them during the Sprint.

Who is responsible for explaining the Product Backlog items? a. The Development Team is self-organized and has to talk to anyone necessary, and find out the meanings of items. b. Scrum Master c. Product Owner d. Business Analyst e. Customer

C It's one of the responsibilities of the Product Owner to explain the items and make sure that everyone has the right understanding.

What is the role of Management in Scrum? A) Continually monitor staffing levels of the Development Team. B) Monitor the Development Team's productivity. C) Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software. D) Identify and remove people that aren't working hard enough.

C Management has no active role in the actual product development through Scrum. However, management external to the Scrum team is incredibly important in setting the vision and strategy to guide the overall direction of the organization.

Which of the following is not allowed in Scrum? a. Release Planning b. Using User Stories c. Sprint Zero d. Using Story Points

C Not allowed; preparing the tools and infrastructure is done gradually during normal Sprints. Otherwise, it will block adaptation and generation of value.

Who decides when to release the product? a. The Customer b. The Scrum Master c. The Product Owner d. The Development Team

C Others, including the customer, have a say in this, but the main responsibility belongs to the Product Owner.

How much time is needed between a Sprint Retrospective and the next Sprint Planning to prepare the Product Backlog? a. As much as the Product Owner finds necessary b. Maximum 10% of the duration of Sprints c. Nothing d. 8 hours in a one-month Sprint

C Product Backlog Refinement happens continuously, and each Sprint begins immediately after the previous one. Each Sprint starts immediately after the previous one; there's no space between the two.

What type of test should be done during the Sprint? a. All tests, except for user acceptance tests b. Unit tests c. Every type of test d. All tests, except for integration tests

C Remember that the Increment has to be "Done", and potentially releasable. It means that all tests should be done.

What type of test should be done during the Sprint? a. Unit tests b. All tests, except for user acceptance tests c. Every type of test d. All tests, except for integration tests

C Remember that the Increment has to be "Done", and potentially releasable. It means that all tests should be done.

What is a proper role of a PMO in a company that uses Scrum? a. The PMO will be responsible for making higher level decision in the project. b. The PMO should manage and help the Product Owners. c. Manage portfolios and programs and facilitate the application of techniques that complement Scrum.

C Remember that there are limits to the self-organization of the team, and the important thing is to have power within the borders of the project. However, each project is run in a wider organization with multiple levels of management that impact the project, and it's not possible or even acceptable to reject that structure, as long as it doesn't block internal self-organization of the team.

Which two statements are correct about Daily Scrums? a. It's facilitated by the Scrum Master. b. Developers must answer the 3 standard questions during the meeting. c. It's held at the same time and place every day. d. Only the developers participate in the meeting. e. The Product Owner should attend the meeting.

C, D

Which two statements explain the benefits of having tests in the Definition of Done? a. It defines when the Increment should be released. b. It makes reporting easier for the Project Manager. c. Increments would be closer to potentially releasable. d. Increases transparency of the Increments.

C, D

The Development Team realizes that they have over-committed themselves for the Sprint. How should they review and adjust the work? a. They shouldn't make any changes to the Sprint Backlog. b. They should ask the Product Owner to cancel the Sprint. c. They can get help from the Product Owner to adjust the Sprint Backlog. d. They can make any adjustments by themselves, because they own the Sprint Backlog.

C Some people think that a successful team is one that can complete all the work in the Sprint Backlog, but this is not true. To the contrary, it probably means they are too conservative in the number of items they select for the Sprint, which in turn may reduce their productivity because of the Parkinson's Law and the Student Syndrome. Nothing bad happens if some items are not done by the end of the Sprint, and no one should blame the team; the Sprint Backlog is just a rough estimate of what they can do.

How often should the composition of the team change? a. As needed, without a need to be concerned about changes in productivity b. Every Sprint, to encourage creativity and openness c. As needed, considering that it will have a short-term reduction in productivity d. Never, because it reduces productivity

C Sometimes you will see questions like this in the exam. You may know that the composition of the team should not change during the Sprint, yet, the correct choice here may imply that. Well, it is up to you to interpret it in a way that it doesn't mean such a thing! So, the precise statement would be "As needed, so long as it's not in the middle of the Sprint, and we consider that it may have a short-term reduction in productivity".

Which of the following may be done in the Sprint Retrospective meeting? a. Refining the Product Backlog b. Calculate Velocity c. Discuss the timeboxed duration of Sprints d. Discuss the Product Backlog items for the next Sprint

C Sprint Retrospective is about the way we work. It's about the things that affect the product, but we don't discuss the product directly. In general, it's about the context, not the content. For example, we can talk about the way Product Backlog is refined, but we won't refine the Product Backlog in the Sprint Retrospective meeting.

The customer goes to the Development Team in the middle of a Sprint, and asks them to add an important item to the Sprint Backlog. What should they do? a. Add the item to the current Sprint Backlog. b. Replace one of the existing items in the Sprint Backlog with the new one. c. Refer the customer to the Product Owner. d. Reject the request.

C The Product Owner is the person responsible for the items and the order in which they are developed.

Which role is the equivalent of project manager in Scrum? a. Product Owner b. Team Leader c. None of them d. Scrum Master e. Development Team

C There's no project manager role in Scrum, and it's not allowed to add new role to the existing three. Also, none of those three roles are the equivalent of a project manager; project management activities are distributed among all of them. This is only about the project level; you can always have higher management levels (e.g. program management), and those "can" be compatible with what you do in your Scrum projects.

On average, items on the Product Backlog tend to be _____ a. Smaller than those on the Sprint Backlog b. The same size as those on the Sprint Backlog c. Larger than those on the Sprint Backlog

C This is how it works: When you first add the items in the Product Backlog, you don't have to break them down into very small and clear items, because it's a form of upfront planning. Some of them may be very large. When you order the items, if they are at the top of the list, you have to make them clear, and make sure they can fit into one Sprint; therefore, you will break them down into smaller items. Some of those child items may remain at the top, and some may go down. Nevertheless, because of this way of refining, the items at the top of the Product Backlog are on average smaller than those at the bottom. On the other hand, items in the Sprint Backlog come from the top of the Product Backlog, therefore, we can say that the items in the Sprint Backlog are, on average, smaller than items on the Product Backlog.

When is it time to integrate the code? a. At the end of each Sprint b. At the end of the project c. Frequently, during the Sprint d. Before each release

C You can't know if the code will work properly, unless you integrate it with the rest of the code. That's why we have continuous integration in Agile, which can happen multiple times a day.

Which statement best describes Scrum? A) A complete methodology that defines how to develop software. B) A cookbook that defines best practices for software development. C) A framework within which complex products in complex environments are developed. D) A defined and predictive process that conforms to the principles of Scientific Management.

C Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.

The Development Team should have all the skills needed to: A) Complete the project as estimated when the date and cost are committed to the Product Owner. B) Do all of the development work, except for specialized testing that requires additional tools and environments. C) Turn the Product Backlog items it selects into an increment of potentially releasable product functionality.

C The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint. Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment.

Which two of the following are correct about the Scrum Master role? a. Estimates the Product Backlog items b. Is cross-functional c. Removes impediments d. Helps the organization implement Scrum e. May add new work to the Sprint Backlog during the Sprint

C, D

Which two of the following are outputs of the Sprint Planning meeting? a. Estimations for the sizes of items b. Resource assignment c. Tasks d. Items selected from the Product Backlog e. Order of items in the Product Backlog

C, D

Which two of the following are required by Scrum? a. Having full-time developers b. Story Points c. Having timeboxed events d. Definition of Done e. Release planning

C, D

Which two of the following should be considered in setting the timeboxed duration of Sprints? a. It should be longer in bigger projects. b. It should be shorter when there are more developers. c. It shouldn't be longer than one month. d. It's better to have shorter Sprints when the project is riskier. e. It shouldn't be longer than 6 weeks.

C, D

Who is responsible for the change management in Scrum projects? A. Project Manager B. Scrum Master C. Product Owner D. Project Sponsor

C. Product Owner

Which two statements are correct about an item that is in-progress at the end of the Sprint? a. Put it in the next Sprint Backlog. b. It can be added to the Increment if the customer accepts it. c. Do not include it in the Increment. d. Move it back to the Product Backlog. e. Consider the complete part of the item in velocity calculation and then create a new item in the Product Backlog for the remaining work

C, D (c) Everything in the Increment must be Done; i.e. 100% DONE!

Which two of the following are outputs of the Sprint Planning meeting? a. Estimations for the sizes of items b. Resource assignment c. Tasks d. Sprint Goal e. Order of items in the Product Backlog

C, D (c) Remember that only some of the tasks are created during Sprint Planning, the rest are created during the Sprint.

The Development Team cannot forecast how much work they can do in the upcoming Sprint, because of uncertainties in the Product Backlog that the Product Owner is not able to overcome. What two actions should the Scrum Master recommend? a. Cancel the Sprint Planning meeting, give them some time to prepare, and then hold another Sprint Planning. b. Cancel the Sprint and start the next one when the items are clear. c. Invite everyone to discuss this problem in the next Sprint Retrospective and try to find a solution. d. Ask the developers to come up with their best guess and do not worry about the capacity. e. Extend the duration of Sprint Planning and ask them to discuss the items more and get into agreement.

C, D It's fine! You just pick a number of items. If it was not enough, you can pick more later. If it was too many, you will just deliver as many as you can. Nothing bad happens if you don't deliver all items in the Sprint Backlog. The goal is to generate value, not to develop all items in the backlog.

Which two of the following are formal opportunities for inspecting and adapting? a. Release Planning b. Burn-down chart c. Sprint Planning d. Daily Scrum

C, D Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are "formal opportunities for inspecting and adapting", and are considered "feedback loops".

Which three statements are correct when four teams are working on a product? a. There is only one Sprint Backlog each Sprint. b. There can be multiple Product Backlogs. c. There can be multiple Definitions of Done. d. There are multiple Sprint Backlogs each Sprint. e. There is only one Product Backlog. f. There can be multiple Product Owners.

C, D, E When there are n teams in the project (working on one product), there are: 1 Product Backlog n Sprint Backlogs each Sprint one or more Definitions of Done, as long as they are compatible with each other 1 integrated Increment each Sprint 1 Product Owner n Scrum Master roles which can be occupied by 1 or more Scrum Masters

Which two statements are correct about an item that is in-progress at the end of the Sprint? a. Demonstrate it in the Sprint Review meeting, if the item is presentable in its current state. b. It can be added to the Increment if the customer accepts it. c. Do not include it in the Increment. d. It can be added to the Increment if the user acceptance tests are done. e. Move it back to the Product Backlog.

C, E

Which two statements are correct about an item that is in-progress at the end of the Sprint? a. The Sprint will be extended until we complete the item. b. Put it in the next Sprint Backlog. c. Move it back to the Product Backlog. d. It can be added to the Increment if the customer accepts it. e. Do not include it in the Increment.

C, E

What are the three questions of the Daily Scrum? a. What problems did I have yesterday? b. Are we able to deliver all Sprint Backlog items by the end of the Sprint? c. What work am I going to do today to help the team achieve its goal? d. How many hours did I spend on the project yesterday? e. What impediments are in my way or in the way of the team? f. What work did I do yesterday to help the team achieve its goal?

C, E, F It's not mandatory to use these questions, but very common and recommended.

High-performing teams feature which of the following sets of characteristics? A. Consensus-driven, empowered, plan-driven. B. Consensus-driven, empowered, low trust. C. Constructive disagreement, empowered, self-organizing. D. Self-organizing, plan-driven, empowered.

C. Constructive disagreement, empowered, self-organizing.

When a Development Team is having trouble delivering a working Increment because they don't understand a functional requirement, what should they do?

Collaborate with the Product Owner to determine what is possible and acceptable

When the Development Team is having trouble delivering a working increment because they don't understand a functional requirement, what should they do?

Collaborate with the Product Owner to determine what is possible and acceptable.

When was Scrum first introduced? A. In 2000 along with Extreme Programming B. At General Electric as part of a Lean approach C. In 1995 at a conference presentation D. In 2001 with the Agile Manifesto

C. In 1995 at a conference presentation

Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose 2 answers) A. How the team does its work B. Team relations C. Sprint Backlog for the next Sprint D. The value of work currently represented in the Product Backlog E. Definition of « Done »

C. Sprint Backlog for the next Sprint D. The value of work currently represented in the Product Backlog

What happens when the Sprint is cancelled? A. The Scrum Team disbands immediately. B. The completed Sprint Backlog items are evaluated for a release and incomplete items are discarded. C. The completed Sprint Backlog items are evaluated for a release and incomplete items are put back to the Product Backlog. D. The complete Sprint Backlog is put back to the Product Backlog.

C. The completed Sprint Backlog items are evaluated for a release and incomplete items are put back to the Product Backlog.

3 C's of agile

Card - write a story card Conversation - collaboration meetings to get more understanding of the cards Conformation - wrting dod and acc criteria

Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the order teams. What should the Scrum Master do?

Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.

How does an organization know that a product built through Scrum is successful? (choose 2 answers)

Customer and end-user satisfaction is important. It's not an abstract measure as in the case of lines of code or velocity. There can be some KPIs for measuring the value of the releases, and when improved, will show our success. Increased velocity is desired, but it's not directly connected to value and can be misleading. This is the same with production cost. It's mandatory to deliver an Increment every Sprint.

How can the success of the project be evaluated? (choose 2 answers)

Customer and end-user satisfaction is important. It's not an abstract measure like lines of code or velocity. There can be some KPIs for measuring the value of the releases, and when improved, will show our success. Increased velocity is desired, but it's not directly connected to value and can be misleading. That's the same with production cost. It's also mandatory to deliver an Increment every Sprint.

A Scrum project is supposed to have two releases: one in the middle and the other at the end of the project. Which of the following statements is correct? a. Increments that are created before each release should be releasable. b. Increments are created for investigation and adaptation; they don't have to be releasable. c. It depends on the operations' preference. d. All increments should be releasable.

A Sprint can be cancelled before the Sprint time-box is over. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change.**When might a Sprint be abnormally cancelled? A) When it becomes clear that not everything will be finished by the end of the Sprint. B) When the Development Team feels that the work is too hard. C) When the sales department has an important new opportunity. D) When the Sprint Goal becomes obsolete.

A new Sprint starts immediately after the conclusion of the previous Sprint.**When does the next Sprint begin? A) Next Monday. B) Immediately following the next Sprint Planning. C) When the Product Owner is ready. D) Immediately after the conclusion of the previous Sprint.

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done? A) Without a new vocabulary as a reminder of the change, very little change may actually happen. B) The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. C) Management may feel less anxious. D) All answers apply.

The Product Owner is the sole person responsible for managing the Product Backlog.**Who has the final say on the order of the Product Backlog? A)The Stakeholders B)The Development Team C)The Scrum Master D)The Product Owner E)The CEO

What does a trend line through a release burn-down chart indicate? a. When the project will likely finish, if the team develops with a speed equal to the last Sprint b. When the remaining work is supposed to be finished c. The budgeted cost of the project d. When the remaining work will likely be completed if nothing changes in the Product Backlog or the Development Team

When does a Product Owner cancel a Sprint? a. When there's an unsolved technical dependency b. When not enough information is available for the items in the Sprint Backlog c. When not enough resources are available for the project d. When the Sprint Goal becomes obsolete

When does a customer cancel a Sprint? a. When not enough information is available for the items in the Sprint Backlog b. When there's an unsolved technical dependency c. When not enough resources are available for the project d. The customer doesn't have the authority to cancel the Sprint.

Which Scrum value is demonstrated when we continuously show the correct performance on a burn-down chart that everyone can see? a. Inspection b. Earned Value c. Cross-functionality d. Openness

Which of the following best describes Sprint Review? a. It's a celebration at the end of the Sprint to appreciate the work of the developers. b. A demo at the end of the Sprint for everyone in the organization to see the Increment. c. It's a controlling mechanism for evaluating the work of the developers. d. An inspection of the Increment to collect feedback and see what to do in the next Sprint

Which of the following can be considered a real output of the Sprint? a. A plan for the next Sprints b. A user interface layout that is designed for the whole solution c. New features that are ready for integration d. A piece of software that is usable by the end users

Which output of Sprint Planning provides overall direction for the Sprint? YoursExpected a. Product Vision b. Sprint Backlog c. Release Plan d. Sprint Goal

Who is responsible for engaging stakeholders? a. The Project Manager b. The Development Team c. The Scrum Master d. The Product Owner

Who's normally involved in Product Backlog Refinement? a. Product Owner b. Development Team and customer c. Scrum Master and Development Team d. Product Owner and Development Team

How much time does the Product Owner spend on Product Backlog Refinement? a. Usually not more than 10% of their time b. Not more than 30% of their time c. Usually not more than 5% of their time d. As much as needed

D (a) Remember that it's the developers who usually spend not more than 10% of their time on refining the backlog; the Product Owner usually spends more time on that.

Which of the following may be done when the team becomes mature enough during the project? a. They may not need a Scrum Master anymore. b. They can release every Sprint. c. They will need longer Sprint Retrospectives. d. Their velocity may increase.

D (d) E.g. they become more comfortable communicating with the customer.

Which statement does NOT explain when an item is considered complete? a. When it can be part of a potentially releasable Increment b. When it's potentially usable for the end users, if it becomes part of the Increment c. When everything is Done based on the Definition of Done d. When the Scrum Master approves it

D (d) Scrum Masters are focused on the context, not the content. Did you notice the word "not" in the question?

All of the following are inputs to Sprint Planning, EXCEPT: a. Velocity b. Previous Increment c. Product Backlog d. Sprint Goal

D (d) The Sprint Goal is created during the Sprint Planning meeting, and therefore, cannot be an input for it. Did you notice the word "except" in the question?

The length of a Sprint should be: A) Short enough to keep the business risk acceptable to the Product Owner. B) Short enough to be able to synchronize the development work with other business events. C) No more than one month. D) All of these answers are correct.

D All of these choices are appropriate considerations in determining the length of a Sprint.

Which element is NOT an attribute of Product Backlog items? a. Value b. Estimate c. Description d. Owner

D Did you notice the word "not" in the question? There are 3 pieces of information in each Product Backlog item: the description (in the form of a User Story, or otherwise), value, and estimate (i.e. estimated size). The ownership of items is shared, therefore, there's no need to record it in the item.

At the end of the Sprint, all items are done except for one that is almost done. What should be done with this item? a. It can be added to the Increment if the customer accepts it. b. Put it in the next Sprint Backlog. c. It can be added to the Increment if the user acceptance tests are done. d. Do not include it in the Increment.

D Everything in the Increment must be Done; i.e. 100% DONE!

What's the main reason for the Product Owner to be at the Daily Scrum? a. To participate as a Scrum Team member b. To track changes to the Sprint Backlog. c. To tell developers what to do. d. It's not necessary for them to be in the meeting.

D In general, Daily Scrum is for the Development Team, which means that only the developers "participate" (talk). Others can "attend" (watch), but they won't "participate" (talk). Well, unless it's about a Scrum Master facilitating the meeting (not so common), in which case they will talk a little ;) However, this contribution of the Scrum Master is about the context, not the content.

Who owns the items in the Sprint Backlog? a. The whole Scrum Team b. The Product Owner c. The Scrum Master d. The Development Team e. Individual developers who are working on the item

D Individual developers take responsibility for doing an item, but all developers stay accountable (own).

When is the Sprint over? a. When the Product Owner announces the end of the Sprint b. When all Sprint Backlog items are done c. When the Scrum Master announces the end of the Sprint d. When the timeboxed duration is over

D It's a simple question: you need to know what timeboxing means, and that Sprints are timeboxed. Other than the normal ends of Sprints, the Product Owner also has the authority to cancel a Sprint.

When does a Scrum Master cancel a Sprint? a. When there's an unsolved technical dependency b. When not enough resources are available for the project c. When the Sprint doesn't make sense anymore d. The Scrum Master doesn't have the authority to cancel the Sprint.

D It's done by the Product Owner.

Who is responsible for explaining the Product Backlog items? a. Customer b. The Development Team is self-organized and has to talk to anyone necessary, and find out the meanings of items. c. Business Analyst d. Product Owner e. User representative(s)

D It's one of the responsibilities of the Product Owner to explain the items and make sure that everyone has the right understanding.

Which of the following are correct about the length of Sprints? a. Sprint length is set during Sprint Planning, and is long enough to develop all items in the Sprint Backlog. b. Sprint length is set during Sprint Planning, and is long enough for programming and testing all items, but not for integrating them. c. Depends on the position of the stars ;) d. All Sprints must be one month or less.

D One month is the maximum timeboxed duration for Sprints in Scrum.

Which of the following best describes the way a Product Owner can order the items in the Product Backlog? a. Based on risk; riskier items at the top b. Based on what the customer asks for c. Based on size; larger items at the top d. Based on value; more valuable items at the top

D Recently, Scrum.org considered ordering based on value, priority, risks, and dependencies. However, if you don't have such a choice, the next best answer (the old-fashioned one) is "based on value". Note: priority is different from order; it's something like "high, medium, low", or "must-have, should-have, could-have".

Which of the following best describes the way a Product Owner can order the items in the Product Backlog? a. Based on size; larger items at the top b. Based on what the customer asks for c. Based on size; smaller items at the top d. Based on value; more valuable items at the top

How much time do the developers spend on Product Backlog Refinement? a. As much as needed b. Usually not more than 20% of their time c. Usually not more than 5% of their time d. Usually not more than 10% of their time

D Remember that it's the developers who usually spend not more than 10% of their time on refining the backlog; the Product Owner usually spends more time on that.

How often should the composition of the team change? a. As needed, without a need to be concerned about changes in productivity b. Every Sprint, to encourage creativity and openness c. Never, because it reduces productivity d. As needed, considering that it will have a short-term reduction in productivity

D Sometimes you will see questions like this in the exam. You may know that the composition of the team should not change during the Sprint, yet, the correct choice here may imply that. Well, it is up to you to interpret it in a way that it doesn't mean such a thing! So, the precise statement would be "As needed, so long as it's not in the middle of the Sprint, and we consider that it may have a short-term reduction in productivity".

Which of the following has the most to do with capturing and using lessons learned? a. Product Backlog Refinement b. Sprint Review c. Sprint Planning d. Sprint Retrospective

D Sprint Retrospective is about discussing the way work was done and finding ways to improve it next time; this is mainly about lessons learned.

Which of the following has the most to do with capturing and using lessons learned? a. Sprint Planning b. Sprint Review c. Product Backlog Refinement d. Sprint Retrospective

D Sprint Retrospective is about discussing the way work was done and finding ways to improve it next time; this is mainly about lessons learned.

Who does all the work required for Product Backlog items, to make sure they are potentially releasable? a. The customer b. The Solution Architect c. The whole Scrum Team d. The Development Team e. The Project Manager f. The Development Team and the Product Owner

D The Development Team is cross-functional and does all the work; i.e. they don't need help from people and departments outside the project.

What's the timeboxed duration of Sprint Planning? a. 8 hours b. Maximum 3 hours c. 3 hours d. Maximum 8 hours

D The timeboxed duration of events is as follows: Sprint - Maximum 1 month Daily Scrum - 15 minutes Sprint Planning - 8 hours in a one-month Sprint, and shorter proportionally Sprint Review - 4 hours in a one-month Sprint, and shorter proportionally Sprint Retrospective - 3 hours in a one-month Sprint, and shorter proportionally

How should the Product Owner forecast the completion date? a. It is the responsibility of the Scrum Master to forecast the completion date. b. By using a trend line in the burn-down chart c. By dividing the remaining amount of work in the Product Backlog to the latest calculated velocity d. By any method they find appropriate

D There are different things that can help them in this forecast, but they are all simplified, and the Product Owner has to consider everything and adjust the forecast before presenting it to the stakeholders.

Which role is the equivalent of project manager in Scrum? a. Product Owner b. Team Leader c. Scrum Master d. None of them e. Development Team

D There's no project manager role in Scrum, and it's not allowed to add new role to the existing three. Also, none of those three roles are the equivalent of a project manager; project management activities are distributed among all of them. This is only about the project level; you can always have higher management levels (e.g. program management), and those "can" be compatible with what you do in your Scrum projects.

When do Development Team members become the exclusive owner of a Sprint Backlog item?

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual development team member.

What does it mean to say that an event has a time-box? A) The event must happen at a set time. B) The event must happen by a given time. C) The event must take at least a minimum amount of time. D) The event can take no more than a maximum amount of time.

D Time-boxed events are events that have a maximum duration.

When is it time to integrate the code? a. Before each release b. At the end of the project c. At the end of each Sprint d. Frequently, during the Sprint

D You can't know if the code will work properly, unless you integrate it with the rest of the code. That's why we have continuous integration in Agile, which can happen multiple times a day.

What is a benefit of having tests in the Definition of Done? a. There's no need to describe tests in the Definition of Done. b. It defines when the Increment should be released. c. It makes it easier for the Scrum Master to measure performance and report progress. d. Increments would be closer to potentially releasable.

D You can't release it unless you've tested the output and are sure it won't create problems in production

The time-box for a Daily Scrum is? A) The same time of day every day. B) Two minutes per person. C) 4 hours. D) 15 minutes. E) 15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.

D The length of a daily Scrum is time-boxed at 15 minutes, it does not change with the length of a Sprint.

Which two of the following are NOT allowed in Scrum? a. Refactoring b. Release Planning c. Using Planning Poker d. Hardening Sprints e. Release Sprints

D, E

Which two of the following are timeboxed? a. Sprint Zero b. Release Retrospective c. Release Planning d. Sprint Review e. Daily Scrum

D, E

Which two statements are correct about Daily Scrums? a. The Product Owner should attend the meeting. b. It's facilitated by the Scrum Master. c. No one other than the Development Team is allowed to be there. d. It's always a 15-minute timeboxed event, no matter how many developers there are, or how long the Sprint is. e. It's held at the same time and place every day.

D, E

Which two of the following are mandatory elements in Scrum? a. Story Points b. Face-to-face communications c. Burn-down charts d. Daily Scrums e. Product Owner

D, E Only the roles, events, and artifacts (+ Definition of Done and progress measurement) are mandatory.

Which three of the following are pillars of Scrum? a. Value optimization b. Sustainable pace c. Creativity d. Inspection e. Adaptation f. Transparency

D, E, F

A Scrum Master is keeping a list of open impediments, but it is growing and he/she has been able to resolve a small portion of the impediments. Which three techniques would be most helpful in this situation? A. Arrange a triage meeting with all other projects managers. B. Tell the Product Owner that Scrum isn't working. C. Discuss the absence of management support with the Development Team. D. Alert management to the impediments and their impact. E. Prioritize the list and work on them in order. F. Consult with the Development Team

D. Alert management to the impediments and their impact. E. Prioritize the list and work on them in order. F. Consult with the Development Team

When does a Development Team member become the sole owner of a Sprint Backlog item?

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be implemented by an individual development team member.

Which statement best describes the Sprint Review? A. It is used to congratulate the Development Team if it did what it committed to doing, or to punish the Development Team if it failed to meet its commitments. B. It is a demo at the end of the Sprint for everyone in the organization to provide feedback on the work done. C. It is a review of the team's activities during the Sprint. D. It is when the Scrum Team and stakeholders inspect the outcome of the Sprint and figure out what to do in the upcoming Sprint.

D. It is when the Scrum Team and stakeholders inspect the outcome of the Sprint and figure out what to do in the upcoming Sprint. Every event in Scrum, besides the Sprint which is a container for the other events, is an opportunity to Inspect AND Adapt.

If the Development Team doesn't like the time of the daily Scrum, what should the Scrum Master do? A. Find a time that is open on everyone's calendar B. Ask the Team to try the existing time for one Sprint C. Tell them that Scrum is immutable and that they need to stick to it D. Let the Development Team come up with a new time

D. Let the Development Team come up with a new time Let the Development Team come up with a new time since they are self-organized

Selforganizing teams are characterized by their ability to: A. Make project-based decisions B. Sit where they like C. Do their own filing D. Make local decisions

D. Make local decisions

Pick 3 activities that are the accountability of the Development Team

Which two things does the Development Team do during the first Sprint? (choose the best two answers)

Develop and deliver at least one piece of functionality. (1) Develop and deliver at least one piece of functionality. (2) Deliver an increment of potentially releasable software.

During the Daily Scrum, a team member says he doesn't know when his task will be complete

Development Teams have the following characteristic: - They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality

self organizing and cross functional

Development team are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality cross-functional means that the team has all the skills necessary to turn Product Backlog Items into a done Increment. It does not mean that each member has all these skills. So your description seems to meet that minimal requirement.(jack of all, master of some) The idea of Scrum is not to force someone into coding who has been testing all his life It is rather to encourage teams to overcome silos of traditional disciplines, learn more and be more robust against unexpected changes (like a tester getting sick). In the example of "developers" and "QAs" you might notice that the time between a bug emerging and a bug fixed will be reduced drastically.

Which of the following are ways for the stakeholders to interact with the Development Team? (choose 2 answers)

Direct interactions with the customer are limited to the Sprint Review, or via the Product Owner. However, this doesn't mean that it is prohibited to meet with stakeholders in another (non-Scrum) events such as Backlog Refinement, etc

When is it most appropriate for a Development Team to change the definition of "Done"?

During Sprint Planning.

Definition of Done can be reviewed and adapted during each Sprint Retrospective. True or False?

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done", if appropriate and not in conflict with product or organizational standards.

When is the Sprint Backlog created?

During the Sprint Planning meeting

When is it most appropriate for a Development Team to change the definition of "Done"?

During the Sprint Retrospective.

When is it most appropriate for a Development Team to change the definition of Done?

During the Sprint Retrospective.

Which statement is correct when the developers are working in the middle of the Sprint?

What happens during the Sprint? Select three answers. 1) No changes are made that would endanger the Sprint Goal 2) Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned 3) Quality goals do not decrease 4) Sprint scope is defined at the Sprint Planning and cannot be changed 5) The Sprint Goal is changed frequently to reflect the status of the remaining work

During the Sprint: ◦ No changes are made that would endanger the Sprint Goal; ◦ Quality goals do not decrease; and, ◦ Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

Which statement is right during the Sprint?

During the Sprint: "No changes are made that would endanger the Sprint Goal;" "Quality goals do not decrease;" The scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

Definition of "Done" is created during the first Sprint and remains unchanged until the Product release. True or False?

False. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.

What happens during the Sprint? Select three answers. 1) Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned 2) Quality goals do not decrease 3) The Sprint Goal is changed frequently to reflect the status of the remaining work 4) Sprint scope is defined at the Sprint Planning and cannot be changed 5) No changes are made that would endanger the Sprint Goal

During the Sprint: - No changes are made that would endanger the Sprint Goal; - Quality goals do not decrease; and, - Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

A Product Owner is essentially the same role as a traditional Project Manager?

Duties of a Project Manager are distributed to Product Owners, Scrum Masters and the rest of the Teams. The first group from this list is responsible for maximizing the value of a Sprint through a Development Team.

Who decides about engineering methods? a. The Project Manager b. The customer c. The whole Scrum Team d. The Scrum Master e. The Development Team f. The Solution Architect

Which item is NOT an attribute of the Product Backlog?

Each Product Backlog has a description (e.g. in the "user story" format), a business value used for ordering, and an estimate of the amount of effort.

When more Scrum Teams are added to a project that works on one single product, the productivity of the original Scrum Teams mostly likely will increase

Each Scrum Team needs to mutually define their definition of "Done" so their combined work will be potentially releasable. This involves some overhead work in syncing up, and hence the impact to productivity

If there are 60 developers for a Scrum project, how should they be divided into teams?

Each Scrum team should (not must) have a maximum of 9 members. When more developers are required, multiple teams can work on the same product and it will be called Scaled Scrum. The developers are self-organized and decide how to form the teams.

Scrum does not scale to large teams

Each Scrum team should have a maximum of 9 members (optimal). When more developers are required, multiple teams can work on the same product and it will be called Scaled Scrum. The developers are self-organized and decide how to form the teams.

The maximum duration of one Sprint may be more than one month

Each Sprint may be considered a project with no more than a one-month horizon. Like projects, Sprints are used to accomplish something. Each Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment.

How should multiple Scrum Teams deliver a done, potentially shippable Increment in a Sprint?

Each Sprint, all Scrum Teams have a done Increment that integrates with all of the other done Increments from all other Scrum Teams on the initiative. The sum of all Increments is the Increment for that product

How much of the Sprint Backlog must be defined during the Sprint Planning event?

Enough so the Development Team can create its best forecast of what is can do, and to start the first several days of the Sprint.

How should a Development Team deal with non-functional requirements?

Ensure every Increment meets them.

How should a Development Team deal with non-functional requirements?

Ensure every increment meets them.

There should be a release for every Sprint.

Every Increment should be potentially releasable, but you don't have to release it every Sprint

No one attends the Sprint Planning but the Scrum Team.

Everyone is free to "attend" the meetings, as long as they don't "participate"

Which of the following is the single source of requirements for all changes to the product?

Everything we might want to apply to the product, including changes, are reflected in the Product Backlog. It's high-level but contains everything. The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.

All the Scrum Teams working on the same product should have the same Sprint length.

False. Scrum does not require having aligned Sprints for multiple teams.

The Daily Scrum time-box depends on the size of the Development team. True or False?

False. The Daily Scrum is a 15-minute time-boxed event for the Development Team of any size.

When do Development Team members take ownership of a Sprint Backlog item?

Never. All Sprint Backlog Items are co-owned by the entire Development Team, even though each one may be done by an individual Development Team member.

Which of the following is the shortest timebox in a two-week Sprint?

Sprint Retrospective is the shortest event in Scrum for all team members

The best description of a Sprint Backlog is:

Explanation of the answer is in the answer: The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realising the Sprint Goal. This is definitely the best description of the Sprint Backlog and as we think (based on user answers) almost the same answer you will see at exam.

A Scrum Team is only allowed to meet with stakeholders during the Sprint Review?

FALSE

Sprints lengths can vary each Sprint as long as they don't exceed a month.

FALSE

The Product Owner determines how many Product Backlog items the Development Team selects for a Sprint. T or F?

FALSE

The Product Owner makes sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders.

FALSE

The Scrum Team and Development Team are the same thing.

FALSE

The Sprint Review is the only time at which stakeholder feedback is taken into account.

FALSE

Using Scrum ensures that adding more resources to a project proportionally increases the value delivered.

FALSE

When multiple teams work together on the same product, each team should maintain a separate Product Backlog.

FALSE

FDD Vs Scrum

FDD and Scrum Similarities Collaborative. Improved communication Completely developed and tested features in short iterations Progress can be tracked at different granularities Emphasis producing quality components FDD and Scrum Differences Scrum: Does not specify any particular engineering practice although parts of XP are frequently adopted. Focus on producing vertical slices of functionality acceptable to product owner. Shorter feedback loops Self-organizing teams Shared code ownership FDD: -Specific engineering practices i.e. design/code inspections, tests -Domain driven -Longer feedback loop -Feature team have recognized roles i.e. Project Manager, Chief Architect, Development Manager, Chief Programmer, Class Owner, and Domain Expert -Class ownership

Scrum Planning Meeting

Facilitator - SM Members- Team, PO, SM Time - 4 hrs Purpose- Basically 2 parts 1. for committing to PBIs 2. to come up with tasks these 2 parts are combined when only 1 team and PO available for whole meeting 1. they ll agree to sprint goals 2. negotiate which PBIs will be committed to Sprint backlog 3. come up with the tasks (40% tasks identified here, 60% identified during execution phase) which are necessary to complete the committed PBIs (wont be able to identify all of them) "who will do what" is not decided here, bt during execution. if now they commit and then dont do it, problem Result - Sprint Backlog

A Scrum of Scrums should be attended by Scrum Masters from accross the organization.

False

A product Increment must be released to production at the end of each Sprint.

False

A product increment must be released to production at the end of each Sprint.

False

Scrum has a role called "Project Manager".

False

The Scrum Team should choose at least one high priority process improvement, identified during the Sprint Retrospective, and place it in the Product Backlog.

False

To truly adopt Scrum, you must pick and choose what roles, artifacts, events, and rules are right for your organization.

False

True or False: When multiple teams work together on the same product, each team should maintain a separate Product Backlog

False

True or False: a propely functioning Scrum Team will have at least one release Sprint and may well have several.

False

When multiple teams ate working together on the same product, each team should maintain a separate Product Backlog.

False

When multiple teams work together on the same product, each team should maintain a separate Product Backlog.

False

True or False: The Scrum Team should choose at least one high priority process improvement, identified during the Sprint Retrospective, and place it in the Product Backlog.

False, to ensure continuous improvement, the Sprint Backlog rather than the Product Backlog includes at least one high priority process improvement identified in the previous Sprint Retrospective meeting.

The Daily Scrum always should take exactly 15 minutes. For example, if your team managed doing it in 5 minutes, you should spend 10 more minutes on some useful team activity like Product Backlog refinement, but not more. True or False?

False. All events in Scrum are time-boxed. It means that every event has a maximum duration. However, the Scrum Guide does not require a minimal duration for any event. As Scrum Teams mature, they can do some events faster (e.g. the Sprint Planning or the Sprint Retrospective).

The structure of the Daily Scrum is well-defined and constant. Every team member should answer the three main questions: - What did I do yesterday? - What will I do today? - Do I see any impediment? True or False?

False. There is no any prescribed structure. The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. It is still perfectly fine to use the questions, but other ways of conducting the meeting are also possible.

Scrum recommends using only those Scrum components and rules which suit most for a particular project. True or false?

False: Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.

The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team. True or false?

False? The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, the Development Team adds it to the Sprint Backlog.

During a Sprint Review, the stakeholders notice that the product development progress is not very visible and lacked transparency. Moreover, they are not able to understand the next steps. Who is responsible for this?

From the Scrum Guide: The PO is ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next The Product Owner is the Lead Facilitator of Key Stakeholder Involvement. The PO is responsible for identifying the key stakeholders for the product and involving them as necessary throughout the development effort. We will change the explanation to make it more clear.

The Product Backlog is ordered by:

Higher priority items are at the top.

Technical systems can be decomposed to composite elements, from the large to the small. Basic components may be represented as activities, workflows, functions, features, capabilities, and other similar nomenclature. How does this system decomposition affect Scrum Teams on scaled projects?

How the organization discusses and plans the work of creating software will be reflected in the implementation of that software.

At the end of the Sprint, Product Backlog items worked on during the Sprint, does not meet the definition of "Done". What two things should happen with the undone Product Backlog items?

If there are undone Product Backlog items in Sprint the team must: -Put it on the Product Backlog for the Product Owner to decide what to do with it. - Do not include the item in the Increment of this Sprint

If it's not possible to complete the Sprint Backlog, who would try to resolve it?

If this situation is happening the Product Owner and the Development team should discuss how they can resolve the issue.

When does the next Sprint begin?

Immediately after the conclusion of the previous Sprint.

How should a Product Backlog item be refined before its development begins? (choose 2 answers)

In a way that it's clear enough for the developers. In a way that it can be "Done" in the timeboxed duration of one Sprint. "Items at the top of the Product Backlog need to be small enough to fit into one Sprint. They also need to be clear and detailed enough; but not too detailed (e.g. not with all the tasks identified), as it would be upfront planning. Tasks are created gradually during the Sprint." Product Backlog items require multiple expertise, and usually done by multiple developers. Therefore, they are not assigned. Tasks, however, are assigned to the individual developers, while everyone stays accountable.

When do Development Team members become the exclusive owner of a Sprint Backlog item?

Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do?

Inform the Product Owner so he/she can work with the CEO.

When can a Development Team cancel a Sprint?

It can't. Only Product Owners can cancel Sprints.

Teams 1 and 2 work on two different projects. Team 1 has 5 members, and a velocity of 450. Team B has 9 members, and a velocity of 700. Which team has a higher performance?

It depends on another factor. Velocity is not equal to value. The provided information is not enough. Velocity is defined locally, and it's not possible to compare one team's velocity with another.

Which statement best describes the Sprint Review?

It gives stakeholders an opportunity to inspect the product increment and progress and provide feedback on next steps.

When multiple teams are working on the same product, who should make sure that their outputs can be integrated into one Increment?

It's up to the developers to find their way and ensure that their outputs will create an integrated Increment that is potentially releasable.

What should the Product Owner do in the middle of the Sprint, when the Development Team realises they are not able to finish all the Sprint Backlog items?

It is OK if some of the items are not done by the end of the Sprint. What we have in the Sprint Backlog is our best guess on what we can deliver. If there's pressure on the developers to finish everything, they will start adding margins to their estimates, which turns into less productivity because of Parkinson's law. "When the Development Team realizes they cannot finish everything, they get help from the Product Owner to adjust their work (tasks), to ensure they will deliver maximum value by the end of the Sprint. Remember that they get help from the Product Owner to make better decisions; the Product Owner doesn't make the adjustments directly."

17 Which statement best describes the Sprint Backlog as outcome of the Sprint Planning?

It is a complete list of all work to be done in a Sprint

How important is it for a Product Owner to order Product Backlog items by value points?

It is a good practice, keeping in mind that market reception is the best measure of value.

What is a Product Backlog?

It is a living artifact of product requirements that exists and evolves as long as a product exists.

Which best describes the Product Backlog?

It is allowed to grow and change as more is learned about the product and its customers.

Must the Product Owner be present at the Sprint Retrospective?

It is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess its performance and improve itself.

It is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release. True or False?

It is not normal. Development Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only "Done" functionality that could be released immediately.

The Product Owner and the Scrum Master can't be part of the Development Team

It is ok for the Scrum Master or for the Product Owner to be also a member of the Development Team.

Within every Sprint, the working Increment should be tested progressively starting from unit testing, then integration testing and then finally user acceptance testing

It is only up to the Team to find the best approach to achieve this

When multiple Scrum teams are working on the same product, should their Sprint length be the same?

It is possible for the teams in a Scaled Scrum to have different Sprint length, so long as the shorter length are evenly divisible into the longest one. Aligning the Sprint boundaries across the Scaled Scrum may help teams to take attention on delivering an integrated increment. Some of the teams can make partial progress in their own Sprint cycles, but the entire Scaled Scrum must deliver a working increment so that the organization can see whether it is making progress toward its delivery goal.

Which of the following is not allowed is Scrum?

It is possible to harden Sprint, but it will not be Scrum.Scrum is free and offered in this Guide. Scrum's roles, events, artefacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.

It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality. True or False?

It is prohibited. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done."

Which statement best describes the Sprint Backlog as outcome of the Sprint Planning?

It is the Development Team's plan for the Sprint.

The Product Owner is using burn-up charts instead of burn-down charts. What would be your response as the Scrum Master?

It is the Product Owner's decision which type of diagram to use

Which role is responsible for determining when a release can occur?

It is the responsibility only of Product Owner

The customer wants a new feature to be added in the current Sprint. How should the Development Team respond?

It is up to the Product Owner to reject this request, rather than the developers. So, they should just refer the customer to the Product Owner.In very special cases, the new feature might be so special, and the project environment so influenced, that the introduction of the new feature makes the current Sprint Goal invalid, and therefore the Product Owner will cancel the Sprint. Remember, this doesn't happen often.

Which statement best describes the Sprint Review?

It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

The Product Owner and Scrum Master may be the part of the Development Team

It's OK for the Product Owner and the Scrum Master to be in the Development Team

Scrum mandates the use of burn-down charts.

It's common and recommended to use burn-down charts, but it is not mandatory.

The Product Owner does not have to be one person, and the role can be played by a committee.

It's possible to have a committee responsible for product ownership, but only a representative of that committee would be called the Product Owner. There's always one Product Owner for a product, even if there are multiple teams.

Which of the following are responsibilities of a self-organising team? (choose 3 answers)

It's the responsibility of the Development Team to estimate the amount of work of Product Backlog items and to select an appropriate number of them for each Sprint. They also break down the items into tasks during the Sprint. Measuring the project performance is the responsibility of the Product Owner while measuring the Sprint performance is done by the Development Team. Creating new Product Backlog items, ordering them (prioritization), and making sure that everyone has a clear understanding of them is the responsibility of the Product Owner.

It is OK for the items at the bottom of the Product Backlog to have less detail compared to those at the top.

Items at the bottom of the Product Backlog won't be developed soon, and therefore, we don't need to spend too much time on them. Otherwise, it would be a form of upfront planning. Items at the bottom of the Product Backlog won't be developed soon, and therefore, we don't need to spend too much time on them. Otherwise, it would be a form of upfront planning

Which of the following is the most important opportunity for capturing lessons learned?

Lessons learned are always captured, but the main purpose of Sprint Retrospective is capturing and planning for lessons learned. The purpose of the Sprint Retrospective is to: "Inspect how the last Sprint went with regards to people, relationships, process, and tools;" "Identify and order the major items that went well and potential improvements;" Create a plan for implementing improvements to the way the Scrum Team does its work.

What is the role of Management in Scrum?

Management should support the Product Owner with insights and information into the high-value product and system capabilities. Setting the vision and strategy to guide the overall direction of the organization

Sprint Review Meeting

Members- Team, PO, SM, stakeholders also allowed purpose- 1. live demo of potentially shippable product increment given, no reports 2. PO declares if PBIs meet acceptance criteria or not 3. PO declare if sprint goals met or not 4. stakeholders feedback is taken. -after which new PBIs are discovered and existing ones re prioritized by PO -considered done only if PBI meets acceptance criteria and definition of done, -not done or partially done are moved back to Product backlog so that they can be done in future sprints -even if a PBI is done and not tested its declared not done cz its not shippable when PO declares PIBs as done they are used to measure *velocity* with help of assigned story points(efforts) to those PBIs (useful for PO to forecast) Iterative development, a value-driven approach, allows the creation of products that couldn't have been specified up front in a plan-driven approach. after review PB gets bigger n bigger after sprints so to meet deadlines of release date its imp to constantly re prioritize the PBIs n get high prior on top

Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?

Monitor communications between them and facilitate direct collaboration.

Kanban

More focus is on quality rather than quantity. Scrum, which focuses on constant communication between team members via frequent short ceremonies. I've often seen Scrum used as the framework for an agile process, with a Kanban board used as the primary tool to communicate progress to people outside the team. Kanban, which focuses around the Kanban board (at least in my experience). The board holds the tasks agreed on for an iteration, and team members choose tasks move them to the different state columns as they work. There are other agile methodologies, but the Scrum/Kanban combination is one of the more common varieties.

"Sprint Refinement meeting" aka "backlog grooming" aka "backlog maintenance" aka "story time"

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. Facilitator - SM Members- Team, PO, SM Time - 4 hrs Purpose- 1. Clarification of requirements 2. Decomposition of PBIs into smaller ones (epics to user stories) 3. Estimation of efforts (Various techniques:Estimation cards) 4. prioritization of PBIs (by PO) 5. comes up with acceptance criteria and definition of done(proper testing and refactoring) -no commitments are made in this meeting so everyone is given estimation card and they all reveal it at the same time and give justification after which PO clarifies what exactly is he/she is expecting.(reveals things which she didnt think of earlier) after listening to his exact requirement re voting is done to re estimate efforts PO is responsible for setting the priorities based on discussion with the team. re prioritization done throughout Result- prioritized list of PBIs

The Product Owner wants to be informed of the progress in the middle of the Sprint. How can she or he get this option? (select all that apply)

No one should not report to the Product Owner the status of the Sprint. So, if the Product Owner wants to know to be informed about the Sprint works, he or she should at least attend the Daily Scrum or check the task board

Is it allowed to skip the Daily Scrum if there is nothing interesting to talk about?

No. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.

How should developers deal with non-functional features?

Non-functional features are usually part of the Definition of Done and should be considered for every Product Backlog item and every Increment. Sometimes, some non-functional features that address a very particular part of the software can be added as separate items in the Product Backlog.All Sprints are the same. There's no Sprint zero, hardening Sprint, release Sprint, integration Sprint, etc.

How much time is required after a Sprint to prepare for the next Sprint?

None. A new Sprint starts immediately following the end of the previous Sprint

How much time is required after a Sprint to prepare for the next Sprint?

None. A new Sprint starts immediately following the end of the previous Sprint.

Each new Sprint starts immediately after the conclusion of the previous Sprint.

Nothing happens between two Sprints - the next one starts immediately after the conclusion of the previous.

The Product Owner's authority to change and update the Product Backlog is unlimited, except for:

Nothing. The entire organization must respect a Product Owner's decisions.

The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What would consider an appropriate action for the Scrum Master to take?

Offer the Product Owner help in ordering the Product Backlog from an understanding that the goal is to maximize value

The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What would you consider an appropriate action for Scrum Master to take?

Offer the Product Owner helps in ordering the Product Backlog from an understanding that the goal is to maximize value

How can the size of items on the Sprint Backlog be compared to the average size of Product Backlog items?

Often (In most cases) Product Backlog Items are split and get smaller over time before they reach the Sprint Backlog. Due to this, in general Sprint Backlog items are smaller than Product Backlog items. "However, a Sprint Backlog Item can be seen as a Product Backlog Item plus a plan for implementing it. In that sense it is additive to, and thus ""larger"" than, the selected Product Backlog Items." But, as we think the first case is related to PSM 1 exam.

There are separate Product Backlogs in multiple Scrum Teams with a single product

One Product = One Product Backlog = One Product Owner even for multiple Scrum Team

How many Product Owners do 3 teams need if there is one product for all teams?

One Product Backlog = One Product Owner

Since the Product Owner is responsible for making the Product Backlog items clear to the developers when many Development Teams are working on the same product, one person won't be enough, and it might require having multiple Product Owners.

One Product Backlog = one Product Owner

why Fibonacci series

One main reason is to not have debates/estimates like: 19,20, 21, 23 Story Points. In agile estimation is usually about comparing relative size, it's clear that 1 Story Point is significantly smaller than 10 Story Points, but 10 SP vs 9 SP is not much different. You want to make sure that bigger numbers are rough estimates and you're not sending to your stakeholders message that you know exactly how big item is. BTW: That's the reason you have 20 instead of 21 which is valid Fibonnaci sequence number. The Fibonacci series also better represents the fact that uncertainty grows proportionally with the size of the story. The differences between 1, 2 and 3 point stories are probably better understood than the differences between a 20 and a 40. This is reflected in the distance between story sizes.

An important executive wants the Development Team to take in a highly critical feature in the current Sprint. The Development Team

One of the Scrum Teams chose to have a Development Team member also playing the role of Scrum Master

A Servant leadership role includes

One of the ways that the Scrum Master, as a servant leader, protects the team is by shielding it from interruptions.

Which statements are correct about a Sprint Backlog item that was not finished until the end of the Sprint? (choose 2 answers)

Only the 100% complete items are demonstrated, to avoid confusion. When something is not complete, it will be moved back to the Product Backlog. If it's still on the top of the Product Backlog, development will continue in the next Sprint

What belongs solely to the Development Team? 1) The Definition of Done 2) The Sprint Backlog 3) The Product Backlog 4) The Increment

Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.

Only the Product Owner has the authority to cancel a Sprint. However, the Development Team is trying to convince the Product Owner that the Sprint should be cancelled. What's the right response from the Scrum Master?

Only the Product Owner has the authority to cancel a Sprint, and the final decision belongs to her/him. However, this decision can be influenced by the customer (incl. stakeholders) or/and developers or/and Scrum Master.

The optimal size of the Development Team is:

Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and result in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful. The Product Owner and the Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.

agile methodology

P.S. => these notes were written by me and after discussing all these things with my mentor she asked me to make changes which i have in my mind but never got time to make those changes here so plz reconfirm things before presenting to your mentors. group of methodologies based on certain principles..iterative development

During a Sprint Retrospective, for what is the Scrum Master responsible?

Participating as a Scrum team member and facilitation as requested or needed

How can we ensure that the performance requirements are addressed in the solution? (Choose 2 answers)

Performance, like security, scalability, and maintainability, is a non-functional feature. Non-functional features are normally added to the definition of "Done" because they apply to all functional features.For some non-functional features, such as performance, it's possible to create non-technical, independent items in the Product Backlog. This is usually done when we have to make an improvement in the previously done features.

Which of the following is not a prioritisation technique?

Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used to estimate effort or relative size of development goals in software development. In planning poker, members of the group make estimates by placing numbered cards face-down on the table, instead of saying them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates. Planning Poker is not a prioritisation technique

The Product Backlog is baselined at the start of the project and not changed for at least three Sprints

Product Backlog cannot be baselined in Scrum

Which of the following does not happen in the first Sprint? (choose 2 answers)

Product Backlog cannot be completed in Scrum as a product exists. Also the architecture can not completed on the first Sprint

When can the Product Backlog be refined?

Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.

These 2 activities are typical works for a Product Owner between the end of the Sprint Planning and before the Sprint Review

Product Backlog refinement is continuous and can happen anytime. Besides that, the Product Owner is constantly in contact with the developers to make sure everything is clear. They are also in contact with the customer to understand their new requirements.Assignments and Sprint performance measurement are done by the developers, and only the developers participate in the Daily Scrums.

Product Backlog refinement is the act of ... to the items in the Product Backlog.

Product Backlog refinement is defined in the Scrum Guide as the act of adding detail, estimates, and order to the Product Backlog items. Remember that Product Backlog refinement is an ongoing activity, and is not timeboxed. The rule is that it shouldn't take more than 10% of the developers' time

The Product Backlog is only refined during the Sprint Planning and Sprint Review.

Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.

What is Agile planning artefact that updated minimally once a year by the Product Owner?

Product Vision is updated by Product Owner at least once a year

The benefits of having a solid product vision is (choose 3 answers)

Product vision is not explained in the Scrum Guide and is not a mandatory part of the framework. However, it's recommended to have one, and use it to help align the decisions and development with the expected outcome of the project

If two Scrum Teams are added to a project that previously had only one Scrum Team, what will be the immediate impact on the first Scrum Team's productivity

Productivity will stay the same.

The Product Backlog is updated only during Backlog refinement and Sprint Planning

Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.

The Product Backlog refinement shouldn't take more than 10% of the Product Owner's time.

Which of the following is a valid service from the Scrum Master to the Product Owner?

Scrum Master Service to the Product Owner The Scrum Master serves the Product Owner in several ways, including: "Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;" "Finding techniques for effective Product Backlog management;" "Helping the Scrum Team understand the need for clear and concise Product Backlog items;" "Understanding product planning in an empirical environment;" "Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;" "Understanding and practicing agility;" Facilitating Scrum events as requested or needed.

One of the Scrum Teams chose to have a Development Team member also playing the role of Scrum Master. A Development Team member cannot also play Scrum Master's role

Scrum Master or even Product Owner may be, at the same time, the member of the Development Team

The Scrum Master as a Servant Leader is in service to which of the following?

Scrum Masters are servant leaders and coaches for an Agile Team and for an organization. They help educate the team in Scrum, Extreme Programming (XP), Kanban, and SAFe, ensuring that the agreed Agile process is being followed. They also help remove impediments and foster an environment for high-performing team dynamics, continuous flow, and relentless improvement.

Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

It is forecasted that the project will be finished in 3 Sprints. The Product Owner wants to design acceptance tests for all items. What's the best response from the Scrum Master?

Scrum doesn't use upfront planning and design, and what described in this question is a form of upfront preparation.

Which of the following might be discussed in a Sprint Retrospective?

Sprint Retrospective is used for planning for improvements. One of them is improving the definition of "Done"

An organisation has decided to adopt Scrum. What happens if they tailor the Scrum terminology to match their current environment? (Choose 3 answers)

Scrum is a framework rather than a methodology. It's very lightweight and only contains the essential required aspects. Therefore, it shouldn't be tailored like methodologies

Which two of the following are true about Scrum?

Scrum is a framework, not a methodology or body of knowledge. Scrum is empirical, rather than theoretical. Scrum is more about project delivery rather than project management. Scrum is adaptive, rather than predictive (it's more than just using Sprints and related artefacts). Scrum should be used entirely (we do not tailor it)

Scrum is container for other techniques and methodologies

Scrum is a process framework that has been used to manage work on complex products since the early 1990s. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

Scrum is software development methodology

What type of process control is Scrum?

Scrum is founded on empirical process control theory or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

Scrum is founded on: 1) Empiricism 2) Empirical criticism 3) Common sense 4) Kanban system

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

Select all that apply, Empiricism provides

Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

Three pillars of scrum are:

Which of the following does not describe Scrum?

Scrum is not a software development process

Scrum is a lightweight development methodology.

Scrum is referred to as a "framework", rather than a "methodology".

Which of the following is not a Scrum Event?

Scrum prescribes four formal events for inspection and adaptation, as described in the Scrum Events section of this document: - Sprint Planning - Daily Scrum - Sprint Review - Sprint Retrospective

Scrum Team uses the information of Scrum artefacts to make ongoing decisions. The soundness of these decisions depends on

Scrum relies on transparency. Decisions to optimize value and control risk are made based on the perceived state of the artefacts. To the extent that transparency is complete, these decisions have a sound basis. To the extent that the artefacts are incompletely transparent, these decisions can be flawed, value may diminish and risk may increase.

How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal? 1) As frequently as possible 2) At the Sprint Review 3) Frequently, but it should not get in the way of the work 4) After the Daily Scrum

What should be the frequency of Inspection in Scrum? Select all that apply

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work. Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something.

Which is NOT a Development Team responsibility?

Selecting the Product Owner.

Set up the meeting and tell the development team that this is how it will be done

Which of the following is required by Scrum? (Choose all that apply.)

Sprint Retrospective.

Which three of the following are feedback loops in Scrum?

Sprint Review Refinement Meeting Sprint Retrospective

For one month Sprint, what is the recommended duration of the Sprint Review?

Sprint Review is a four-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

Is Sprint Review a formal meeting?

Sprint review is a formal event, but informal meeting

Stretch goal

Some teams prefer to leave plenty of excess capacity in each sprint, perhaps so there is time for emergent needs or experimentation. Other teams prefer to fill the sprint to the best of their ability to forecast their capacity. Still other teams like to take on a "stretch goal" each sprint, which is kind of a product backlog item that is not quite in the sprint, but is one the team hopes to complete if the sprint goes well.

Spike

Spikes are an invention of Extreme Programming (XP), are a special type of story that is used to mitigate risk and uncertainty in a user story at an early stage OR A story or task aimed at answering a question or gathering information, rather than at producing shippable product. 2 types 1. Functional spikes 2. Technical spikes There are two other characteristics that spikes should have: 1. Have clear objectives and outcomes for the spike, estimable, demonstrable, acceptable 2. Be timeboxed 3. exception, not the rule Some user stories may require both types of spikes: eg As a consumer, I want to see my daily energy use in a histogram, so that I can quickly understand my past, current, and likely near term, future energy consumption. In this case, a team might create two spikes: Technical Spike: Research how long it takes to update a customer display to current usage, determining communication requirements, bandwidth, and whether to push or pull the data. Functional Spike: Prototype a histogram in the web portal and get some user feedback on presentation size, style, and charting attributes. Prototypes, Proof of Concepts (PoC), and story boards, Wireframes all fall into the classification of Spikes. Indications for Spike's necessity: 1. Trouble shooting: Teams failure to estimate the stories effectively. Disagreement in on how big the stories are. 2. High-Points estimates: Teams story points are high for a story that a Product Owner estimates low. This could be an indication that there is technical debt the team is working on deliver a story. 3. Patterns of difficulty: There could be a certain type of stories the team is facing a lot of trouble. There are a lot of bugs and QA items from some stories. The feedback from the retrospective shows that are difficulties in implementing the technology 4. Team speaks out: about difficulties and technical creep issues.

Which of the following two items are not topics of discussion within a Sprint Retrospective ?

Sprint Backlog for the next Sprint and the functionality implemented as a result of the Sprint are not a part of Sprint Retrospective topic

What are the questions the Sprint Planning answers? Select two. 1) Who will be responsible for each item in the Sprint Backlog? 2) What is the size of the Technical Debt and how it could be removed? 3) What new technologies could be used to speed up the Development Team velocity? 4) How will the work needed to deliver the Increment be achieved? 5) What can be delivered in the Increment resulting from the upcoming Sprint?

Sprint Planning answers the following: - What can be delivered in the Increment resulting from the upcoming Sprint? - How will the work needed to deliver the Increment be achieved?

What are the questions the Sprint Planning answers? Select two. 1) What can be delivered in the Increment resulting from the upcoming Sprint? 2) What new technologies could be used to speed up the Development Team velocity? 3) How will the work needed to deliver the Increment be achieved? 4) Who will be responsible for each item in the Sprint Backlog? 5) What is the size of the Technical Debt and how it could be removed?

Sprint Planning answers the following: ◦ What can be delivered in the Increment resulting from the upcoming Sprint? ◦ How will the work needed to deliver the Increment be achieved?

How long the Sprint Planning takes in a project with three-week Sprints?

Sprint Planning is 8 hours for a one-month Sprint, and usually shorter proportionally for shorter Sprints.

How much time does the Sprint Planning take? 1) Not more than 4 hours 2) Not more than 8 hours 3) As much as it is necessary to make task break-down and estimations for all items in the Sprint Backlog 4) From 4 to 8 hours

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.

What's the maximum duration of the Sprint Planning when the Product Backlog is not clear?

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.

The maximum duration of Sprint Planning is:

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Which topics should be discussed in the Sprint Review?

Sprint Results

What is the responsibility of the project manager in Scrum?

There is no project manager role in Scrum

What is the role of Management in Scrum?

Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software.

invisible gun effect

THE INVISIBLE GUN EFFECT HAPPENS EVEN WITH THE NICEST BOSS IN THE WORLD. It's not caused by the boss's actual actions, it's caused by the way subordinate behavior is naturally distorted around bosses. It's normal human nature, not something Scrum Masters can "fix" any more than they can fix gravity. It's most visible to the lower-status people (which might include newhires, people with less impressive job titles, etc.), less visible to higher-status people (perhaps including senior developers, socially confident people, people with better technical skills than social perception skills, and Scrum consultants), and practically invisible to bosses who haven't done an A/B test yet.

A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place.

TRUE

Multiple Scrum Teams working on the same project must have the same Sprint start date.

TRUE

The Product Owner is the sole person responsible for managing the Product Backlog.

TRUE

The Scrum Master is a participant in the Sprint Retrospective.

TRUE

The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog

TRUE

The purpose of a Sprint is to produce a done increment of the Product.

TRUE

The Development Team informs the Scrum Master that the IT manager has asked for a status report during the Sprint. The Scrum Master will:

Talk to the IT manager and explain that progress in Scrum comes from inspecting an increment at the Sprint Review.

Fite new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the other teams. What should the Scrum Master do?

Teach team that it is their responsibility to work with the other teams to create an integrated increment.

During the Daily Scrum, the Scrum Master's role is to:

Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.

Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum?

Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.

Why is the technical debt important for Product Owners?

Technical debt is shortcomings in the code that makes it less than "good enough", and therefore creates risks in the future. It usually decreases velocity in the future (because the team has to fix the shortcomings), and as some of the debt might remain in the final product, the maintenance cost will increase as well.The total cost of ownership is a combination of the project cost and maintenance cost.

During which meeting do team members synchronise their work and report impediments for removal

The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. during this, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day so as to reduce complexity.

Who is responsible for tracking the remaining work of the Sprint?

The Development Team

Who is responsible for training the remaining work of the Sprint?

The Development Team

Who owns the Sprint Backlog?

The Development Team

Who should make sure everyone does his or her tasks for the Sprint?

The Development Team

Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

The Development Team

Who writes tests in a Scrum Team

The Development Team

Who creates a Product Backlog item's estimate?

The Development Team after clarifying requirements with the Product Owner.

Who supports the Scrum Master in removing impediments? (Choose 2 answers)

The Development Team can help the Scrum Master because of their understanding of how the work is done. Some impediments are rooted in external causes, and that's why the Scrum Master might need to have the senior management's support in removing them

How do you know that a Development Team is cross-functional?

The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software

What does it mean for a Development Team to be cross-functional?

The Development Team includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software

Self-organizing teams are characterised by their ability to ...

The Development Team is focused on creating Increments during Sprints, and are self-organized to find out how best to accomplish it. Higher-level decisions for the project are done by the Product Owner and other stakeholders.

The Scrum Team and the Development Team are the same teams

The Development Team is part of the entire Scrum Team. But definitely not the same as a Scrum Team

The Product Owner and the Scrum Master cannot tell the Development Team how to build the product.

The Development Team is self-organized and finds its own way instead of receiving orders.

Who is responsible for managing the Development Team?

The Development Team is self-organized, and manages itself, instead of receiving orders. Development Teams have the following characteristics: "They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;"

Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint. Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. TheDevelopment Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.A good way to continue is:

The Development Team makes sure that all of the selected scope per Sprint is as Done as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn't mess up the Product Backlog.

A Development Team member should own each Sprint Backlog item.

The Development Team owns the Sprint Backlog, not separate members of the team.

How is management external to the Scrum Team involved in the Daily Scrum?

The Development Team self-manages and is the only management required at the Daily Scrum.

The Scrum Team gathers for the Sprint Planning meeting. The Product Owner has some stories but the team finds that the stories do not provide enough information to make a forecast. The next immediate step is

The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint. The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team. The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.

Who is required to attend the Daily Scrum?

The Development Team.

Who is responsible for forecasting the work estimates during a Sprint?

The Development Team.

Who is responsible for tracking the remaining work of the Sprint?

The Development Team.

Who must attend the Daily Scrum?

The Development Team.

Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

The Development Team.

The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?

The Development Team. As a collective, they have a complete view of the work needed to transform Product Backlog items into Increments of product

complete the Product Backlog items?

The Development Team. As a collective, they have a complete view of the work needed to transform Product Backlog items into Increments of product.

How are Product Backlog items selected in scaled Scrum?

The Development Teams are self-organized and it's their responsibility to select items from the Product Backlog. When there are multiple teams, all of them should do it together. They should also seek the acceptance of the Product Owner, since s/he should be able to have a history of items.

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

The Development Teams pull in work in agreement with the Product Owner.

What is the Increment? 1) All "Done" items in the Sprint Backlog 2) The sum of all the Product Backlog items completed during the Sprint 3) All items in the Sprint Backlog that could be released regardless of whether the Product Owner decides to actually do it 4) The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints

The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

Who is responsible for a definition of "Done" that can be applied to the Integrated Increment?

The Nexus Integration Team is responsible for a definition of "Done" that can be applied to the Integrated Increment developed each Sprint. All Scrum Teams of a Nexus adhere to this definition of "Done".

Portfolio Level

The Portfolio level is where the strategies that drive your enterprise initiatives are determined and where value stream funding and epic-level decision making occurs.

Who is responsible for managing the Product Backlog in Scrum?

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

What could be a source of requirements for any changes to be made to the product? 1) The Product Backlog 2) The Key Stakeholders 3) The CEO of the Organization

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.

Select 2 statements that are true about the Product Owner

The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: "- Clearly expressing Product Backlog items;" "- Ordering the items in the Product Backlog to best achieve goals and missions;" "- Optimizing the value of the work the Development Team performs;" "- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next;" - Ensuring the Development Team understands items in the Product Backlog to the level needed.

Who's responsible for ordering the Product Backlog?

The Product Owner is responsible for ordering the Product Backlog and has the final say about it. Product Owner's decisions about the Product Backlog should be respected by everyone: no one can override his/her decisions.The Product Owner's decisions can be influenced by any stakeholder, but the last say still belongs to the Product Owner.

The customer goes to the Development Team in the middle of a Sprint, and asks them to add an important item to the Sprint Backlog. What should they do? a. Add the item to the current Sprint Backlog. b. Refer the customer to the Product Owner. c. Reject the request. d. Add the item to the next Sprint Backlog.

The Product Owner is the person responsible for the items and the order in which they are developed.

In Scrum, the Product Owner is accountable for .....

The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: "- Clearly expressing Product Backlog items;" "- Ordering the items in the Product Backlog to best achieve goals and missions;" "- Optimizing the value of the work the Development Team performs;" "- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next;" - Ensuring the Development Team understands items in the Product Backlog to the level needed.

The Product Owner can delegate some of his/her responsibilities to the Development Team.

The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: "Clearly expressing Product Backlog items;" "Ordering the items in the Product Backlog to best achieve goals and missions;" "Optimizing the value of the work the Development Team performs;" "Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next;" Ensuring the Development Team understands items in the Product Backlog to the level needed. The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

The Product Owner can ask the developers to order the Product Backlog items instead of him/her.

The Product Owner "owns" the Product Backlog.

The Product Owner is the sole responsible person, and they even "own" the Product Backlog. "Remember that the Sprint Backlog is owned by the Development Team. This is not in contrast to the fact that the Product Backlog items are estimated by the developers; they provide this information to the Product Owner to be included in the Product Backlog.There are multiple implications by saying that the Product Owner "owns" the Product Backlog or is the sole responsible person. Only they can add items to the backlog or decompose them into smaller items; while this is done by input from the customers and developers, and even the Product Owner can delegate this responsibility to the developers.Only they can decide on the order of the items on the Product Backlog, while this is usually based on the input from customers and developers."

In what ways does the Product Owner manage the value of the product? (choose 2 answers)

The Product Owner manages the value of the product by: 1 - Product Backlog Order 2 - Customer Feedback via frequent releases

How much time should a Product Owner spend with the team?

The Product Owner should be committed to the delivery of product value and should spend enough time with the Development Team to meet that commitment. Note that the only reason for the Product Owner to spend time with the developers is not refactoring, but also Sprint Planning, answering questions during the Sprint, helping developers adjust their work, etc.

In a Scrum Team, only the Product Owner communicates with the stakeholders. There is no exception to this rule

The Product Owner should have sole responsibility for representing the stakeholders with the team and ensuring that the team is working on the correct items to maximize their contribution to the business. The goal of the Scrum team is to create high-value products and find ways to do this as effective as possible. According to the rules, the PO should work with the stakeholders to get the requested value right, so the team can build it without needing the stakeholder. But first of all, it doesn't mean that the Dev Team can't interact with stakeholders, for example at Sprint Review (why not?). The second is that sometimes the domain expert is also the stakeholder and he/she may be invited to the Sprint Planning.

Select the five Scrum Values. 1) Openess 2) Effectiveness 3) Courage 4) Commitment 5) Agility 6) Focus 7) Respect 8) Self-organization

The Scrum Guide recognizes the following Scrum Values: commitment, courage, focus, openness and respect.

The role of Scrum Master in Sprint Retrospective is

The Scrum Master ensures that the Sprint Retrospective is positive and productive. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting regarding the accountability over the Scrum process.

The Scrum Master is a participant in the Sprint Retrospective.

The Scrum Master ensures that the meeting is positive and productive. The Scrum Master teaches everyone to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting for accountability over the Scrum process. But anyway it doesn't mean that he is not a participant in the Retrospective meeting

Who is responsible for promoting and supporting Scrum? Select the best choice. 1) The Development Team 2) The Scrum Master 3) The Product Owner 4) The Scrum Master and the Product Owner 5) The Scrum Team

The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

The Product Owner doesn't spend enough time on the project. Which of the following options is the best response from the Scrum Master?

The Scrum Master is responsible for training and coaching team members on a proactive way and convinces them to do the right thing. All other options are either reactive, or not self-organized.

A new developer is having continuing conflicts with existing Development Team members and creating a hostile environment. If necessary, responsible for removing the team member?

The Scrum Master is responsible, because he/she removes impediments

A new developer is having continuing conflicts with existing Development Team members and creating a hostile environment. If necessary, who is responsible for removing the team member?

The Scrum Master is responsible, because he/she removes impediments.

How does the Scrum Master serve the Development Team? Select the three most appropriate answers. 1) Helping the Development Team to create high-value products 2) Removing impediments to the Development Team's progress 3) Coaching the Development Team in self-organization and cross-functionality 4) Helping the Development Team as the team leader 5) Adding or removing developers from the Development Team in accordance with team velocity changes

The Scrum Master serves the Development Team in several ways, including: ◦ Coaching the Development Team in self-organization and cross-functionality; ◦ Helping the Development Team to create high-value products; ◦ Removing impediments to the Development Team's progress; ◦ Facilitating Scrum events as requested or needed; and, ◦ Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

How does the Scrum Master help to the Product Owner? Select the three most appropriate answers. 1) Facilitating Scrum events as requested or needed 2) Finding techniques for effective Product Backlog management 3) Understanding product planning in an empirical environment 4) Introducing cutting edge development practices 5) Leading and coaching the organization in its Scrum adoption

The Scrum Master serves the Product Owner in several ways, including: ◦ Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; ◦ Finding techniques for effective Product Backlog management; ◦ Helping the Scrum Team understand the need for clear and concise Product Backlog items; ◦ Understanding product planning in an empirical environment; ◦ Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; ◦ Understanding and practicing agility; and, ◦ Facilitating Scrum events as requested or needed.

How does the Scrum Master serve the Organization? Select the three most appropriate answers. 1) Planning Scrum implementations within the organization 2) Mixing experienced developers and junior specialists across different Development Teams in the organization to speed up Scrum adoption 3) Leading and coaching the organization in its Scrum adoption 4) Making sure the key stakeholders are invited on all Scrum Reviews within organization 5) Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization

The Scrum Master serves the organization in several ways, including: - Leading and coaching the organization in its Scrum adoption; - Planning Scrum implementations within the organization; - Helping employees and stakeholders understand and enact Scrum and empirical product development; - Causing change that increases the productivity of the Scrum Team; and, - Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

If a member of the development team expresses their concerns to the Scrum Master about system performance issues of specific backlog items, what should the Scrum Master do?

The Scrum Master should ask the member to share the issue with the Development team

Who is responsible for coping with incomplete artifact transparency? 1) The Scrum Master 2) The Product Owner 3) The Development Team 4) The Scrum Team

The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.

Who is responsible for coping with incomplete artifact transparency? 1) The Product Owner 2) The Scrum Team 3) The Development Team 4) The Scrum Master

The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.

Who is on the Scrum Team? (select all that apply)

The Scrum Team consists of a Product Owner, Development Team, and a Scrum Master.

The Scrum Team consists of: 1) The Scrum Master 2) The Key Stakeholders 3) The Product Owner 4) The Development Team

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

Who's in the Scrum Team? (Choose multiple answers)

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

A cross-functional team in Scrum consists of what types of team members?

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all the competencies needed to accomplish the work without depending on others who are not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses and any complex work.

Which of the following is correct about Product Backlog refinement?

The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.

Who must do all the work to make sure Product Backlog items conform to the Definition of "Done"?

The Scrum Team.

Who determines when it's time to update the Sprint Backlog during the Sprint?

The Sprint Backlog includes the items selected from the Product Backlog and the tasks created by decomposing the items. Only the tasks are updated during the Sprint, and it's the Development Team's responsibility to do so.

Who updates the work remaining during the Sprint?

The Sprint Backlog is a plan with enough detail that changes in progress and can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work required to achieve the Sprint Goal.

A new task to complete the Sprint Goal is identified after the Sprint Planning. When will this task be added to the Sprint Backlog?

The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.

Who can change the Sprint Backlog during the Sprint?

Who can change the Sprint Backlog in the middle of the Sprint?

The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint.

The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that increase quality, creativity and productivity. Based on this, which of the following is FALSE?

The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint ... lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do? Select the best option. 1) Assign a responsible team member for at least one improvement. 2) Check the progress at the next Retrospective. 3) Make sure the Sprint Backlog for the next Sprint includes at least one high priority process improvement. 4) Make sure the Sprint Backlog for the next Sprint includes all the improvements. 5) Assign responsible team members for every improvement. Check the progress at the next Retrospective.

Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do? Select the best option. 1) Assign responsible team members for every improvement. Check the progress at the next Retrospective. 2) Make sure the Sprint Backlog for the next Sprint includes at least one high priority process improvement. 3) Assign a responsible team member for at least one improvement. Check the progress at the next Retrospective. 4) Make sure the Sprint Backlog for the next Sprint includes all the improvements.

Which artefact contains a plan for realising the Sprint Goal?

Who owns the Sprint Backlog?

The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.

What provides guidance to the Development Team on why it is building the Increment? 1) The Sprint Goal 2) The Sprint Backlog 3) The Scrum Master 4) The Product Owner

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.

Which of the following statements is true? Select all that apply

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.

Who creates the Sprint Goal?

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

This Scrum event for the process improvement is

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

In which event the Scrum team discusses the process improvements?

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to: "- Inspect how the last Sprint went with regards to people, relationships, process, and tools;" "- Identify and order the major items that went well and potential improvements; and," - Create a plan for implementing improvements to the way the Scrum Team does its work.

The maximum length of the Sprint Retrospective is

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

A Development Team has the following condition under the definition of "Done": "All the code is to be reviewed and approved by Industry Coding Standard Organization." This Industry Coding Standard Organization is a third party Subject Matter Expert outside the Scrum Team.

The activities required to complete the Product Backlog items to a "done" state should be completely within the ownership and influence of the Scrum Team.

Every Development Team should have:

The competencies and skills needed to deliver a Done Increment in a Sprint.

Why is the Daily Scrum held at the same time and same place?

The consistency reduces complexity.

In which cases is an Increment valuable? (choose 2 answers)

The customer's satisfaction is valuable and important to us. Reducing the operational costs, which consequently decreases the total cost of ownership, is also a way of bringing value.All Increments are delivered on time because the Sprints are timeboxed.There's no need to have all the Sprint Backlog items completed before the end of the Sprint. At least, this is not the most important thing when we are dealing with value.

Which statement best describes the definition of "Done"?

The definition of "Done" helps us understand when everything is done on a Product Backlog item, and it can become part of the Increment. The definition of "Done" is defined by the development organization, or the Development Team, rather than the Product Owner

How is management external to the Scrum Team involved in the Daily Scrum?

The development Team self-manages and is the only management required at the Daily Scrum

Who creates the definition of "Done"?

The development organization (or Development Team if none is available from the development organization)

Who creates the definition of "Done"?

The development organization (or Development Team if none is available from the development organization)

Who creates the definition of Done?

The development organization (or Development Team if none is available from the development organization)

Who creates the definition of "Done"?

The development organization (or Development Team if none is available from the development organization) If the definition of "done" is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. The Development Team of the Scrum Team can complement it with elements specific for the product or context. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product.

Who creates the definition of "Done"?

The development organization (or Development Team if none is available from the development organization).

17 Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

The development team

Duration (length) of the Sprint is decided by

The entire Scrum Team decides the duration of the Sprint.

What is the essence of Scrum? Select the most appropriate option.

The essence of Scrum is a small team of people. The individual team is highly flexible and adaptive. These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.

What does it mean to say that an event has a time-box?

The event can take no more than a maximum amount of time.

You are on a Scrum Team that is enhancing an existing product. Which is the LEAST useful piece of documentation you want to have at your disposal?

The full history of retrospective plans and lessons learned

What's the vertical axis in a typical burn-down chart?

The horizontal axis is time, the vertical axis is the remaining amount of work, and the trend line shows the forecasted finish date if the Product Backlog and the team capacity stay the same.

What is the input to the Sprint Planning? Select four. 1) The Product Backlog 2) Feedback from the Key Stakeholders 3) The latest product Increment 4) Projected capacity of the Development Team during the Sprint 5) Past performance of the Development Team 6) Feedback from the Organization CEO

The input to the Sprint Planning is: . The Product Backlog . The latest product Increment . Projected capacity of the Development Team during the Sprint . Past performance of the Development Team

What is the accountability of the product owner during Sprint 0?

There is no such thing as Sprint 0

What happens to the incomplete Product Backlog items when the Sprint is over?

The items should be re-estimated, because they have been partially done, and it would take less effort to complete them in the future.Whenever an item is not done during the Sprint (for cancellation or reaching the end of the timebox), it would be moved back to the Product Backlog, rather than the next Sprint Backlog. This is so, because the Product Owner might reorder them, and they won't be on the top of the Product Backlog anymore.

What's the optimal length of a Sprint?

The length of Sprint should be short enough to minimise risk but no more than 1 month

The purpose of the Daily Scrum for the developers is to inform the Product Owner of the progress.

The main purpose of Daily Scrum is the synchronization for developers.

The number of developers has increased from 7 to 14. Now the Daily Scrums do not fit in 15 minutes. What's the best response to this problem?

The maximum number of Development Team members is 9 (optimal size). If more is needed, it's possible to use scaled Scrum (more than one team working on the same product)

Which of the following can be considered for ordering the Product Backlog?

The most important basis for ordering the Product Backlog is a value. "Importance" can also refer to a value, and that's why this is the right answer. The size, risk, and cost affect the value, but do not impact ordering "directly".

What's the most important metric for a Product Owner to measure, in order to make the progress of the project clear?

The most important thing to calculate is the completion date of the project. That's also the most important thing that should be communicated to the customer. Traditional criteria such as lines of code or man-hours spent on the project are not good measures of performance. The velocity can be a guide in forecasting the completion date, but is not enough, and is not the main reporting item.

Imagine you are a Scrum Master. There are 10 professionals (developers and QAs) and the Product Owner. How should you distribute people between development teams? Choose all applicable answers:

The number of people in a Development Team should be between 3 and 9. Each team should be cross-functional and self-organized. Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and result in smaller productivity gains. Having more than nine members requires too much coordination. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.

Development team members sign up to own Product backlog items at the Sprint Planning

The only one owner of the Product Backlog (include Product Backlog items) is the Product Owner

When multiple teams are working on the same product, their Sprints should be synchronised, and their outputs should be integrated into one integrated Increment.

The output created by each team should be potentially releasable, and then they will be packaged into one integrated Increment. This means that each Product Backlog item will be handled by one team, and each team should be cross-functional. Teams start and finish their Sprints at the same time to reduce complexity.

Developers sign up to own (individually) sprint backlog items at the Sprint Planning.

The ownership of the items and tasks are shared. The items are not even "assigned" to developers because they require multiple expertise. Only the tasks are assigned, and even then, their ownership is shared.

The primary objective behind why the Scrum Master ensures that the Scrum Team and those interacting with the Team from the outside adhere to the Scrum rules is

The primary objective behind why a Scrum Master ensures that the Scrum Team and those interacting with the Team from the outside adhere to the Scrum rules to maximize the value created by the Scrum Team

Cadence

The purpose of a cadence is to establish a reliable and dependable capability which demonstrates a predictable capacity. Cadence gives some confidence in the upcoming work when we are triggering rather than scheduling work. Thus cadence is what gives a team a feeling of demarcation, progression, resolution or flow. A pattern which allows the team to know what they are doing and when it will be done. For very small, or mature teams, this cadence could by complex, arrhythmic or syncopated. However, it is enough to allow a team to make reliable commitments because recognizing their cadence allows them to understand their capability or capacity.

The purpose of the Sprint Retrospective is to (select three): 1) Get technical or domain advice from specialists invited by The Development Team or The Scrum Master 2) Inspect how the last Sprint went with regards to people, relationships, process, and tools 3) Identify and order the major items that went well and potential improvements 4) Create a plan for implementing improvements to the way the Scrum Team does its work 5) Get feedback from the Key Stakeholders invited by the Product Owner

The purpose of the Sprint Retrospective is to: ◦ Inspect how the last Sprint went with regards to people, relationships, process, and tools; ◦ Identify and order the major items that went well and potential improvements; and, ◦ Create a plan for implementing improvements to the way the Scrum Team does its work.

The purpose of the Sprint Retrospective is to (select three):

The purpose of the Sprint Retrospective is to: "- Inspect how the last Sprint went with regards to people, relationships, process, and tools;" "- Identify and order the major items that went well and potential improvements;" - Create a plan for implementing improvements to the way the Scrum Team does its work.

The purposes of the Sprint Retrospective are to (select three):

The purposes of the Sprint Retrospective are to: "- Inspect how the last Sprint went with regards to people, relationships, process, and tools;" "- Identify and order the major items that went well and potential improvements; and," - Create a plan for implementing improvements to the way the Scrum Team does its work.

Stakeholders provide feedback in the Sprint Review, and this feedback impacts the next Sprint Planning meeting

The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall so as to meet new opportunities.

The development team should have the supervisor to ensure the work is correctly executed

There is no supervisor role in Scrum

When is it time to integrate the solution?

The solution may be added at any time during the Sprint. Integration is part of the development of each item, and a step in a normal definition of "Done". Agile projects use continuous integration to make the output potentially releasable.

What are the three questions the Scrum Guide gives as an example that can be used at the Daily Scrum? 1) What did I do yesterday that helped the Development Team meet the Sprint Goal? 2) What will I do today to help the Development Team meet the Sprint Goal? 3) Do I have complete understanding of the Sprint Backlog item I am working on? 4) Did I explain all the discovered issues I found yesterday to the Product Owner? 5) Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used: ◦ What did I do yesterday that helped the Development Team meet the Sprint Goal? ◦ What will I do today to help the Development Team meet the Sprint Goal? ◦ Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

The Development Team is ready to start the first Sprint, while the Product Backlog is not complete yet. What should the Product Owner do?

The team may do all necessary work in Sprint Planning. The Product Backlog is a dynamic concept that is never complete. You don't have to have all the items identified before starting the first Sprint.

What are the three main qualities the team model in Scrum is designed to optimize? 1) Competence 2) Flexibility 3) Productivity 4) Creativity 5) Agility 6) Responsabilit

The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

Who participates in the Sprint Planning? Select three. 1) The Product Owner 2) The Scrum Master 3) The Development Team 4) The Key Stakeholders 5) The Team Manager

The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team: the product owner, the scrum master and the developement team

Select three reasons why automated builds are important

There are 3 reasons of this: - They allow frequent validation of the unit of software being worked on, ensuring it remains in a potentially shippable state. - They support continuous integration - The build process is clearly defined and scripted, making it easy consistent and repeatable

Hardening Sprints are helpful for defect management and integration.

There are no hardening Sprints in Scrum. All Sprints are the same and create Increments."Hardening" is done during all Sprints.

What activities would a Product Owner typically undertake in the phase between the current Sprint Review meeting and the next Sprint's Sprint Planning?

There are no such activities. The next Sprint starts immediately after the current Sprint

What activities would a Product Owner typically undertake in the phase between the end of the current Sprint and the start of the next Sprint?

There are no such activities. The next Sprint starts immediately after the current Sprint

What pre-conditions must be fulfilled in order to allow Sprint Planning to begin?

There are no such pre-conditions

Which of the following is a responsibility of team leaders when multiple teams are working on the same product?

There are only three roles in Scrum, and it's not allowed to add other roles or titles: Product Owner, Scrum Master, Development Team

Since the Scrum Team is self-organizing, it can create an additional role to represent the organization within Scrum

There are only three roles in Scrum. Product Owner, Scrum Master, Development Team

Which of the following is not a role in Scrum?

There are only three roles in Scrum: Scrum Master, Product Owner, and Scrum Master. It's not allowed to define other roles or titles.

What are two good ways for a Scrum Team to ensure security concerns are satisfied? (2 answers)

There are two good ways for a Scrum Team to ensure security concerns are satisfied: Add security concerns to the definition of "Done" Have the Scrum Team create Product Backlog items for each concern.

The Scrum Master shouldn't allow the Development Team to start developing without having the tasks identified and assigned.

There are two problems with this statement:1. The Scrum Master doesn't manage people and cannot forbid team members from doing something and cannot order them to do certain things. S/he should always "convince" them to do the right thing by training and coaching.2. The Development Team identifies the tasks and assigns them gradually, throughout the Sprint. We don't do it upfront, at the beginning of the Sprint.

There is one Product Backlog for a Nexus.

There is a single Product Backlog for the entire Nexus and all of its Scrum Teams. The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering.

A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:

There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint.

There should be many integration Sprints to integrate the solution.

There is no additional integration Sprint in Scrum. There should be many integration Sprints to integrate the solution. All Sprints are the same and create increments. Integration is done during all Sprints.

In their journey to deliver products of the highest business value, what factors will enable the Scrum Team to balance creativity, flexibility and productivity? Select all that apply

There is no team leader in Scrum Team and it is impossible to reward only part of Dev Team in Scrum

It's allowed to have team leaders when many developers are working on a complex project.

There is no team leader role in Scrum Team

This Scrum event supports daily inspection and adaptation

There is only one daily event in Scrum: the Daily Scrum. The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that itâ€™s a good idea to have teams organized by feature.What are the advantages of keeping component teams while starting Scrum?

There's less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this

When should the Product Owner update the project plan?

There's no "project plan" artefact in Scrum. The Product Backlog is a form of planning in Scrum projects, and it's updated continuously (Product Backlog refinement).

Which of the following helps the Product Owner avoid waste in the project?

There's no need to spend too much time on the items at the bottom of the Product Backlog. They can be broken down into smaller items and have more details when they move to the top of the backlog.

What should the Product Owner do during the Sprint zero?

There's no such thing as a Sprint zero. The first Sprint is called Sprint 1, and it's exactly the same as other Sprints: it creates an Increment. The infrastructure and tools and requirements are prepared gradually throughout the project.

Which one of the following statements is correct when multiple Scrum teams are working on the same product?

There's only one Product Backlog for Scrum Team. "One" project and "one" product has only "one" Product Backlog and "one" Product Owner. Otherwise, prioritization and accountability would be difficult.

Which of the following is a way of decreasing technical debt?

There's usually room for improving the definition of "Done". A good definition will let less technical debt pass on to the next Sprints. Technical debt is minor shortcomings in the code that makes it less than "good enough", and therefore creates risks in the future. It usually decreases velocity in the future (because the team has to fix the shortcomings), and as some of the debt might remain in the final product, the maintenance cost will increase as well. Another Agile way of reducing technical debt is continuous refactoring.

A Development Team gets into a situation where a conflicting team members' behaviour causes issues to progress. Who is responsible for removing this issue?

Think about who is responsible for identifying and removing different types of issues. The Scrum Master is responsible for removing impediments outside the Development Team's influence. Also, they are responsible for causing change that increases the productivity of the Scrum Team. In this case, the issue faced by the Development Team is well within the influence of the Development Team to resolve. So, the Scrum Master should coach the team to resolve such items themselves. If the Scrum Master actively takes steps such as removing this person from the Team, it will lead to a diminished inclination of the Development Team to resolve internal problems for themselves in the long run.

The Scrum Master tracks the work remaining in the Product Backlog

This is the responsibility of a Product Owner.At any point in time, the total work remaining to reach a goal can be summed. The Product Owner tracks this total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.

Who's responsible for planning releases?

This is the responsibility of the Product Owner

Which of the following is not a pillar of Scrum?

Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

How can a Product Owner use time-boxed Sprints to obtain feedback from users and the market?

Through frequent delivery of Increments of the product into the market.

Using timebox Sprints helps limit work-in-progress.

Timebox in Scrum ceremonies helps limit WiP

What is the role of management in Scrum?

To facilitate the Scrum Teams with insights and resources that help them improve.

What is the purpose of a Sprint Review?

To inspect the product increment with the stakeholders and collect feedback on next steps.

As the Sprint Planning meeting progresses, the Development Team sees the workload as greater than they can handle, which are two valid actions? (choose 2 answers)

When the Development Team realizes they cannot finish everything, they receive help from the Product Owner to adjust their work (tasks), to ensure they will deliver maximum value by the end of the Sprint.

When is a Sprint cancelled?

When the Product Owner determines that it makes no sense to finish it.

The purpose of a Sprint is to produce a done increment of Product.

True

The purpose of a Sprint is to produce a done increment of working product

True

The purpose of a Sprint is to produce a done increment of working product.

True

To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guide the process.

True

True of False: The purpose of a Sprint is to produce a done increment of a product

True

True of False: To get started in terms of what to build, Scrum requires no more than a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas and a Scrum Master to help guid the process

True

True or False: Multiple Scrum Teams working on the same product or system all select work from the same Product Backlog

True

Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice. True or False.

True .The Development Team may also invite other people to attend in order to provide technical or domain advice.

All Development Teams working on the same Product should use the same Product Backlog. True or False?

True. Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.

Scrum is not a process or technique. True or False?

True. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques.

In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?

Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.

Scrum should be tailored for the project.

Unlike methodologies, the Scrum "framework" is not tailored, because it's already limited to the essentials. Even the terms should not change. However, you need to add many practices and techniques to the framework.

Product Backlog Items should always be expressed as User Stories

User Stories are very popular in Scrum, but they are not mandatory

user story

User Story is a single "user flow" from a Feature I described above. "User can enter his password and re-enter it for password verification. If the passwords are not matched, the system will show a message". Another example: "User can enter his password; the system will check the password's strength by [rules] and notify the user if the password is not strong enough". By itself, from User Story is hard to understand the entire picture, but it's a smaller unit of work to plan and execute by.

A Scrum Team is in the process of defining Product Backlog items. The Scrum Master notices that the team is not using User Story format to capture the backlog items. Scrum Master should

User Story is a very good method to write requirements. However, user stories are not mandatory in Scrum. And only the team decides which type of requirements the will use.

It's required to use user stories in Scrum.

User stories are not mandatory in Scrum

Non-functional requirements should always be written as user stories

User stories are not mandatory in Scrum. So they can be written in any form which is appropriate for the team

When might a Sprint be abnormally terminated?

When the Sprint Goal becomes obsolete.

When is a Product Backlog item considered complete?

When the item has no work remaining in order to be released.

When is a Sprint Backlog item considered complete?

When the item is completely based on the definition of "Done", the end users can use it, and it creates an Increment of working software which is potentially releasable.

When is a Sprint over?

When the time-box expires.

What is the benefit of using value points in ordering the Product Backlog?

Value points are relative units for value assigned to the Product Backlog items. It increases transparency (everyone understands why) when applied correctly.

Which of the following refers to the average amount of work done per Sprint?

Velocity - is the average amount of work done per Sprint

Our velocity was 250 at the end of the 6th Sprint. It has become 275 at the end of the 11th Sprint. Therefore, we're creating more value now, compared to the past.

Velocity and value are not related directly.

Which of the following are optional in Scrum? (choose 2 answers)

Velocity calculations and the use of burn-down charts are common and recommended, but not mandatory. The rest are Scrum artifacts. All Scrum roles, events, and artifacts are mandatory.

What's velocity?

Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric inScrum

Which of the following is less likely to be used by a Scrum Team?

WBS and Gantt Chart are used in traditional projects because they are focused on an upfront understanding of the scope of the project. The scope of Agile projects evolve during the project.

When does the Development Team prepare the tools and infrastructure for the development?

We do not prepare the infrastructure and tools upfront because it requires an understanding of the whole product, which is against the adaptation concept. The required infrastructure and tools depend on the product we're going to create, which in turn is defined through the project. The infrastructure and tools will be prepared gradually through the project. There's no Sprint zero in Scrum. All Sprints are the same, used to create an Increment of working software

The Product Backlog is baselined at the beginning of the project.

We don't baseline any artefact in Scrum. The Product Backlog is dynamic, and never complete

The Sprint Backlog is baselined at the end of the Sprint Planning.

We don't baseline any artefact in Scrum. The Sprint Backlog is dynamic, and changes during the Sprint to include newly identified tasks

What happens when the Product Backlog is not clear enough at Sprint Planning?

We prefer to have "ready" items at the top of the Product Backlog before Sprint Planning, which is done through Product Backlog refinement. However, nothing stops our flow of Sprints, and for example, we do not delay the Sprint because the items are not ready. In such cases, the "unready" items would be selected for the Sprint anyway, and refined during the Sprint."Ready" items are those that are clear, and small enough to fit into one Sprint.

continuous integration

We've often experienced programmers writing code and the task working perfectly, but later, while we integrated that code with the rest of the application, we faced unexpected results. To overcome such situations, continuation integration is very much needed. It becomes more important with Agile frameworks, where the nature of delivery is incremental, iterative, and in short cycles (as in Scrum, XP, or in fact in any other Agile framework). Continuous integration is possible only through an automated process that builds, tests, analyzes, and deploys the application. This process runs with each source-code change and provides immediate feedback to the development team. Minimum human intervention in these processes results in saving time. Continuous integration also reduces the risk of delivery slippage as the development team performs testing and integration on a continuous basis. This helps us identify defects in time and take appropriate and necessary action. The integration may be daily, weekly, nightly, release based, or for testers as per requirement -- and it must be, of course, done in a continuous manner. Tools used for Continuous Integration are: Cruise Control, Jenkins, Bamboo, and Buildbot Automated regression testing prevents vampire stories that leap out of the grave.

It's better to have longer Sprints when the project is riskier.

When Sprints are shorter, there are more opportunities for demonstration, receiving feedback, and adaptation. So, when risks are higher, it's better to have shorter Sprints (if it's possible).

What happens when a Sprint is cancelled? Select three. 1) Several top Product Backlog Items are taken into the Sprint Backlog to replace the obsolete items 2) If part of the work is potentially releasable, the Product Owner typically accepts it 3) All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog 4) At the Sprint Retrospective the Scrum Master determines who from the Development Team is responsible for cancelling the Sprint 5) Any completed and "Done" Product Backlog items are reviewed

When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. If part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.

When is a Product Backlog item considered complete?

When all the work in the Sprint Backlog related to the item is finished

The product Owner must release each increment to production.

When it makes sense

What does the word "development" mean in the context of Scrum? Select the best option. 1) Product development, its releasing and sustaining 2) Software and hardware development 3) Research and identifying of viable markets, technologies, and Product capabilities 4) Development of an operational environment for the Product 5) Complex work that can include all the suggested options and even more

When the words "develop" and "development" are used in the Scrum Guide, they refer to complex work including software and hardware development, development and releasing of products and enhancements, development and sustaining product operational environments, research and identifying of viable markets and technologies, and even more.

If burndown charts are used to visualize progress, what does a trend tine through a release burndown chart indicate?

When the work remaining will be likely completed if nothing changes on the Product Backlog or the Development Team

A company has four products. Which two of the following are acceptable ways of forming Scrum teams?

When there's one product, there should be only one Product Owner, even if the product is large and there are many Development Teams. However, when there are multiple products, there are two options: 1) considering them separate and have a Product Owner for each of them, and 2) have only one Product Owner for all of them and develop them in the same way as a larger project in order to ensure compatibility.

When may a Development Team change its engineering practices?

Whenever needed

Sprint Backlog emerges during the Sprint.

While the Product Backlog items selected for the Sprint Backlog stay the same, the tasks created by decomposing them always change and emerge during the Sprint.

difference between epic and theme

While the stories that comprise an epic may be completed independently, their business value isn't realized until the entire epic is complete. This means that it rarely makes sense to deliver an epic until all of the underlying stories are complete. In contrast, while stories comprising a theme are related, each is independent enough to be delivered separately and still provide some measurable sense of business value.

Who starts the Daily Scrum?

Whoever the Development Team decides should start.

Within just a few Sprints, Scrum increases the transparency of the following

Within just a few Sprints, Scrum increases the transparency of technical ability of the team to create Product Increment and information on real progress

What does the Burndown Chart represent?

Work remaining to be completed in the Sprint Backlog

When many Scrum Teams are working on the same product, should all of their in increments be integrated every Sprint?

Yes, but only for Scrum Teams whose work has dependencies

Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less? 1) No, all items in the Sprint Backlog should be decomposed to units of one day or less by the end of the Sprint Planning 2) Yes, if the remaining work is also estimated, maybe in bigger units

Yes, if the remaining work is also estimated, maybe in bigger units

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.

Sprint

a time period of 7-30 days, usually 15 days in which development occurs on a set of backlog items that has committed to

The Daily Scrum is an event that happens every day. What would three key concerns if the frequency were to be lowered to every two or three days?

a) Opportunities to inspect and adapt the Sprint Backlog are lost. b) Impediments are raised and resolved more slowly c) The Product Owner cannot accurately report progress to the stakeholders.

Who should know the most about the progress toward a business objective or a release

and be able to explain the alternatives most clearly?,The Product Owner

Velocity Driven sprint planning

based on the premise that the amount of work a team will do in the coming sprint is roughly equal to what they've done in prior sprints. The steps in velocity-driven sprint planning are as follows: 1. Determine the team's historical average velocity. 2. Select a number of product backlog items equal to that velocity. ----3. Identify the tasks involved in the selected user stories and see if it feels like the right amount of work. --------4. Estimate the tasks and see if the sum of the work is in line with past sprints.

When multiple teams work together on the same product

each team should maintain a separate Product Backlog.,False

The Product Owner's authority to change and update the Product Backlog is unlimited

except for:,Nothing. The entire organization must respect a Product Owner's decisions.

ATDD

high level business perspective With acceptance test driven development the focus is verifying work is done by passing acceptance tests. As it is dealing with acceptance tests it will usually be at the functional test level. ATDD is close in concept to BDD, but with a stronger focus on the testing aspect as validation ATDD tools would include Cucumber and Fitnesse.

The Scrum Team should choose at least one high priority process improvement

identified during the Sprint Retrospective, and place it in the Product Backlog.,False

testing in scrumSprint Planning

in Sprint Planning tester should - pick a user-story 4m d product backlog dt shud be tested. - decide how many hours (Effort Estimation) it should take to finish testing for each of selected user stories. - must know what sprint goals are. - contribute to the prioritizing process during sprint - support developers in unit testing - test user story when completed, log defects, retest once resolved - attend daily scrum - put any item that can not be completed to next sprint - develop automation scripts, schedule automation testing with continuous integration system, review CI automation results and create reports on it and send it to stakeholders - execute functional, non- functional testing - co ordinate with cust and PO to define acceptance criteria for acc tests - also does acceptance testing sometimes and conforms testing completeness for the particular user story retrospective - as a tester what went wrong, what went right, lessons learned and best practices

Spiral model

incremental model with emphasis on risk analysis (both technical and managerial risks) 4 phases 1. Determine objectives Kind of requirement gathering is done 2. Identify and resolve risks risks and alternative solutions are identified prototype is produced after this 3. Development and test Detailed design code integration test deploy 4. Plan next iteration adv 1. risk reduction 2. new features can be added 3. software produced early disadv 1. specific expertise needed 2. highly dependent on risk analysis 3. complex than waterfall and hence costly

acceptance criteria

its different for each item whereas def of done is same for all items in backlog both are musts these requirements have to be met for a story to be declared as complete at review meeting

capacity

no of people * no of hrs * no of days but thats too much to estimate.. better to use focus factor for estimating

forced ranking

only 1 PBI should be on the top.. no 2 PBIs can be at same level or at the top.

Velocity

rate at which a team delivers stories from the product back log used to measure future commitments(forecasting) OR work(story points) done by the team in one sprint or iteration from prev sprint ull have focus factor=vel/cap(cz u hv predicted vel here) after few sprints ull have actual focus factor n ull be able to forecast the velocity for coming sprints velocity = focus factor * capacity

user stories

s/w system requirements formulated as 1 or 2 sentences in everyday or business language of the user. written throughout a project. usually a story writing workshop is held at the beginning. goal is to create product backlog basically a user story talks about 1. title 2. as a (user) 3. i want to (goal) 4. so that (reason) 2 types 1. epics - a large user story, high level. these can be broken down/decomposed into smaller stories that can fit into a single iteration 2. ready stories - small detailed that can be implemented directly, tested tools used - version 1 (most famous) its about who what why not how

The Product Owner actively asks for stakeholder input into the Product Backlog However, a Product Owner is the only person who is responsible for Product Backlog he

she actively asks for stakeholder input into the Product Backlog

Bad apple theory

suggests that a single negative individual ("withholding effort from the group, expressing negative affect, or violating important interpersonal norms"14) can disproportionately reduce the performance of an entire group. Such individuals are rare, but their impact is magnified by a team's reluctance to remove them. This can be partly mitigated by giving teams greater influence over who joins them.

pair programming

two people work collaboratively on the same task on a single computer. - better communication, - better clarification of the problem, - better understanding of its solution. - The person who controls the mouse and keyboard is called the "driver." - The other person, who sits beside the driver and makes sure that solution is implemented in an effective and efficient manner, is called the "navigator." - The members of the pair can switch with other members within the team to take on a different task in another iteration. Better coding practice adherence Less dependence on particular individuals More effective inclusion of new team members Greater knowledge sharing among members No separate code reviews required Better code quality

Test driven development (TDD)

unit tests are written first, then enough code is written to make the tests pass. The pure TDD cycle is to write one failing unit test, then enough code to pass the test. Then a second failing unit test, then enough new code to pass both tests. And so forth. refactoring is one imp factor Unit Testing layer : junit, jasmine, jmock

behavior driven development (BDD)

used to calculate TDD BDD (Behaviour Driven Development) is a synthesis and refinement of practices stemming from TDD (Test Driven Development) and ATDD (Acceptance Test Driven Development). BDD augments TDD and ATDD with the following tactics: apply the "Five Why's" principle to each proposed User Story, so that its purpose is clearly related to business outcomes thinking "from the outside in", in other words implement only those behaviors which contribute most directly to these business outcomes, so as to minimize waste describe behaviors in a single notation which is directly accessible to domain experts, testers and developers, so as to improve communication apply these techniques all the way down to the lowest levels of abstraction of the software, paying particular attention to the distribution of behavior, so that evolution remains cheap Cucumber tool + Selenium tool Which layer? It should be E2E (End To End)

focus factor/capacity planning

used to measure the change in velocity in the instance of a capacity change it will vary from person to person Focus factor is teams ability to remain focussed on the sprint goals without any other distractions usually ranges from 0.6 to 0.8 real capacity = total capacity * focus factor (real commitments can be made against this real capacity) focus factor(F) = velocity(V) / capacity(C) 1. commitment driven(feature driven) 2. date driven

Technical Spikes

used to research various technical approaches in the solution domain. For example, a technical spike may be used for evaluation of potential performance or load impact of a new user story, evaluation of specific implementation technologies that can be applied to a solution, or for any reason when the team needs to develop a more confident understanding of a desired approach before committing new functionality to a timebox.

Functional spikes

used whenever there is significant uncertainty as to how a user might interact with the system. Functional spikes are often best evaluated through some level of prototyping, whether it be user interface mockups, wireframes, page flows, or whatever techniques is best suited to get feedback from the customer or stakeholders.

When many Development Teams are working on a single product

what best describes the definition of "Done?",All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

If burndown charts are used to visualize progress, what do they track?

work remaining across time

How does Definition of "Done" help the Scrum Team? Select three most applicable items. 1) DoD ensures artifact transparency 2) DoD is used to assess when work is complete on the product Increment 3) DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning 4) DoD helps in inspection and adaptation 5) DoD helps to calculate velocity of the Scrum Team

◦ DoD is used to assess when work is complete on the product Increment ◦ DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning ◦ DoD ensures artifact transparency

What are the three most applicable characteristics of the Product Owner? 1) Product Value Maximizer 2) Product Marketplace Expert 3) Facilitator of Scrum events 4) Lead Facilitator of Key Stakeholder Involvement 5) Lead Scrum evangelist in the Organization

◦ Product Value Maximizer ◦ Lead Facilitator of Key Stakeholder Involvement ◦ Product Marketplace Expert

What is the duration for: 1) Sprint planning 2) Sprint retrospective 3) Daily scrum 4) Sprint review

◦ Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. ◦ The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. ◦ Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. ◦ Sprint Retrospective is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

certification PSM 1 - SCRUM, SCRUM PSM I Assessment, Professional Scrum Master 1 (PSM1) "Questions and explanations", SCRUM MASTER, Scrum Study Guide - Rachel, Scrum, Scrum, PSM I Assessment, PSM I Assessment

संबंधित स्टडी सेट्स

Anthropology Final Exam

Web Servers and Hypertext Transfer Protocol

Classification of Hormones 4

Population Health Study Guide

Chapter 8: New Product Development

LIFE

WH 12.2 Quiz

Chapter 12 PMBOK 5th edition - Practice Test #10

Social Psychology 9th Edition Chapter 7

WMS050: Midterm, Key Concepts: Weeks 1-5

Nervous System (Multiple Choice Questions)

Human Origins Final

ENG129 Final

Accounting and Finance

Chapter 3 - Organization Culture, Socialization, Mentoring

Fossils

History test two

Information Systems

Egyptian and Mesopotamian Death Practices

Anatomy Final Schwartz