7776.NovoGV14.2.0

The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog. True. False.

Every Scrum Team should have: The competencies and skills necessary to create value each Sprint. At least one representative from each major software engineering discipline (like QA, Dev, UX). One Lead Developer and no more than 10 other members.

What three factors are best considered when establishing the Sprint length? Choose 3 answers. The ability to go to market with a product release. Sprints must have the same length throughout an organization. The frequency at which team formation can be changed. The level of uncertainty over the technology to be used. The risk of being disconnected from the stakeholders.

Which three of the following are true about Scrum? Choose 3 answers. Scrum is a methodology, where you can pick and choose which parts of Scrum you think will work for your environment. Scrum is like traditional processes but with self-organization to replace Project Managers. Scrum is a framework for developing and sustaining complex products. Scrum is based on empirical process control theory. 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 two metrics will help a Product Owner establish that value is being delivered?. Time to market. Customer satisfaction. Velocity. Productivity. Budget spent.

The Product Owner is accountable for the functionality included in each Increment. Does he or she have the final say over the definition of "Done"?. Yes, the Product Owner is responsible for the definition of "Done". The Developers may be consulted. No, the Scrum Team is responsible for the definition of "Done". The Product Owner should be consulted.

Who is responsible for clearly expressing Product Backlog Items?. The Product Owner. The Scrum Master. The Scrum Master, or the Scrum Master may have the Developers do it. The business analyst who represents the Product Owner in the Developers.

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. Each task is estimated in hours. It is the Developers plan for the Sprint. Every item has a designated owner. It is ordered by the Product Owner.

When the Developers determines that they are over-committed for a Sprint, who has to be present when reviewing and adjusting the Sprint work selected?. The Scrum Master, project manager and Developers. The Product Owner and the Developers. The Product Owner and all stakeholders. The Developers.

The time-box for a Daily Scrum is?. The same time of day every day. Two minutes per person. 4 hours. 15 minutes. 15 minutes for a 4 week Sprint. For shorter Sprints it is usually shorter.

Who must do all the work to make sure Product Backlog items conform to the Definition of “Done?”. The Scrum Team. The Developers. The Product Owner. QA Specialists. The Scrum Master.

Which does a self-managing Developers choose?. How to best accomplish its work. Product Backlog ordering. Stakeholders for the Sprint Review. Sprint length. When to release, based on its progress.

Which of the following are roles on a Scrum Team? Choose all that apply. Developers. Users. Customers. Product Owner. Scrum Master.

As the Sprint Planning meeting progresses, the Developers sees that the workload is greater than they can handle. Which two are valid actions? Choose 2 answers. The Developers works overtime during this Sprint. Recruit additional Developer before the work can begin. Cancel the Sprint. Remove or change selected Product Backlog items. The Developers ensures that the Product Owner is aware, starts the Sprint, and monitors progress.

What does it mean to say that an event has a time-box?. The event must happen at a set time. The event must happen by a given time. The event must take at least a minimum amount of time. The event can take no more than a maximum amount of time.

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?. Yes, in order to accurately inspect what is done. No, each Scrum Team stands alone. Yes, but only for Scrum Teams whose work has dependencies. No, that is far too hard and must be done in a hardening Sprint.

During a Sprint Retrospective, for what is the Scrum Master responsible?. Acting as a scribe to capture the Developers answers. Prioritizing the resulting action items. Participating as a Scrum Team member and facilitating as requested or needed. Summarizing and reporting the discussions to management.

Which are NOT appropriate topics for discussion in a Sprint Retrospective? Choose 2 answers. How the team does its work. Team relations. Definition of "Done". Sprint Backlog for the next Sprint. The value of work currently represented in the Product Backlog.

Which phrase best describes a Product Owner?. Requirements engineer. Value optimizer. Team manager. Go-between between Developers and customers.

What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Scrum Teams?. Create teams based on their skills across multiple layers (such as database, UI, etc.). Ask the Product Owner to assign the people to teams. Ask the developers to divide themselves into teams.

Which of the following best describes an increment of working product?. An automated test suite to verify functionality delivered in previous iterations. UML diagrams that describe how to deliver functionality in future iterations. A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists. A new user interface design for functionality delivered in previous iterations. Additional features in a useable state that complement those delivered in previous iterations.

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 Developers. The Scrum Master. The Project Manager.

Which three purposes does the definition of “Done” serve? Choose 3 answers. Increase transparency. Create a shared understanding of when work is complete. Describe the work that must be done before the Sprint is allowed to end. Describe the purpose, objective, and time-box of each Scrum event. Guide the Developers on how many Product Backlog items to select for the Sprint.

Learning turns into "validated learning" when assumptions and goals can be assessed through results. What is a key way for a Product Owner to apply validated learning?. Release an Increment to the market to learn about the business assumptions built into the product. Accept an Increment at the Sprint Review to learn about the forecast of functionality that was developed. Set the Sprint Goal before selecting Product Backlog items at Sprint Planning to learn about the Developers productivity.

Which two statements explain why the definition of "Done" is important to the Product Owner?. It assures the Increment reviewed at the Sprint Review is usable so the Product Owner may choose to release it. It helps the Product Owner track the open work during a Sprint. It creates transparency regarding progress within the Scrum Team. It identifies undone work that can be addressed in a separate Sprint.

What best describes the relationship of the Product Owner and the stakeholders?. The Product Owner writes the User Stories as provided by the stakeholders. The Product Owner has the final call over the requirements and should involve the stakeholders as little as possible. The Product Owner actively asks for stakeholder input and expectations to process into the Product Backlog. The Product Owner provides the stakeholders with acceptance forms at the Sprint Review to record their formal agreement over the delivered software.

How important is it for a Product Owner to order Product Backlog items by value points?. The Product Owner may order the Product Backlog by using value points or select another technique, the decision is up to them. Using value points is the ultimate way for a Product Owner to predict the value that the product will provide. Calculating value points is a predictive approach that conflicts with the empiricism of Scrum, and is therefore not acceptable.

A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason: Not enough Product Backlog items are "Ready". The Product Owner has not identified a Sprint Goal. There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint. The QA department needs more time to make the previous Increment "Done". The stakeholders are not happy with the value produced in the previous Sprint.

What two phrases best describe the relationship of the Product Owner and the Developers?. They should work apart as much as possible in order to keep the concerns of business and technology separated. They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog items. The Product Owner should be with the Developers full-time to grow a deep understanding of the technology being used. They collaborate often so the Developers builds Increments keeping end-user and stakeholder concerns in mind. They should share no more than the Sprint Planning and the Sprint Review meeting.

The Product Owner´s authority to change and update the Product Backlog is unlimited, except for: Decisions by the CFO, the CEO or the board of directors. Technical and architectural work that needs to be done first, as indicated by the chief enterprise architect. Items the Scrum Master has identified as impediments. There are no exceptions; the entire organization must respect a Product Owner's decisions. Decisions by the chief program manager. High impact changes that have not been approved by the change request board.

Must the Product Owner be present at the Sprint Retrospective?. It is optional. Attendance is only required when the Product Owner gets invited by the Scrum Master. It is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess its performance and improve itself. It is not allowed. The Sprint Retrospective is an opportunity for the Developers to inspect themself.

The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?. The Developers. As a collective, they have a complete view of the work needed to transform Product Backlog item into Increments of product. The PMO. They have all the history on projects delivered, and this enables the IT department to make delivery commitments. The Product Owner. The Product Owner is required to commit on delivery to the users and the stakeholders.

What two things best help the Product Owner manage the value of a product?. Setting value on individual Product Backlog items using Value Poker. Devising a formula for a neutral calculation of value. The order of the Product Backlog. Validating assumptions of value through frequent releases.

It is mandatory for the Product Owner to monitor and share progress of Product Backlog through: A Product or Release burn-down chart. A Value burn-up chart. A Gantt chart. Any practice based on trends of work completed and upcoming work. A Sprint Review acceptance report.

What pre-conditions must be fulfilled in order to allow Sprint Planning to begin?. A fully refined Product Backlog. Formal budget approval to conduct another Sprint. A clear and non-negotiable Sprint Goal. A clear but negotiable business objective for the Sprint. Enough "Ready" Product Backlog to fill the Sprint. There are no such pre-conditions.

The Sprint Review is the only time at which stakeholder feedback is taken into account. True. False.

How can a Product Owner use time-boxed Sprints to obtain feedback from users and the market?. Through the assurance that the Developers finishes all work on the Sprint Backlog. Through frequent delivery of Increments of the product into the market. By making sure a Sprint does not stop until all testing is done, and the work is verified by the Product Owner. At the end of each Sprint, a detailed report with all test cases and test results is available. A business analyst represents the Product Owner to make decisions on his behalf during the Sprint. This way the Product Owner can accept the work at the Sprint Review without further involvement.

What two things should be done if the Product Owner is unavailable?. Within the Sprint, the Developers makes the best decisions possible to assure progress toward the Sprint Goal, realigning with the Product Owner once he/she is available again. There should be a Product Owner team to allow a different person from that team to instantly take over the role of Product Owner. In a permanent state of unavailability, a new Product Owner needs to be appointed. Development efforts without a Product Owner are not employing Scrum. Development of functional requirements stops until the Product Owner is available again.

What variables should a Product Owner consider when ordering the Product Backlog?. Lowest development cost in order to maximize Return on Investment (ROI). Effort first, then value. Development cohesion as indicated by the Developers. Anything that informs them to achieve the product's goals and to optimize the value delivered. The availability of resources and skills for implementation.

How does an organization know that a product built through Scrum is successful?. By measuring the actual time spent on development versus the time estimated for development. By measuring that velocity has increased since the last release. By releasing frequently, and measuring the value customers/users experience. By the Product Owner and stakeholders accepting the Increment at the Sprint Review.

What is a Product Backlog?. The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is a list of references to Use Case documents that are stored in a central repository. The references should be viewable and clickable by anybody to enhance transparency. It is a formally approved list of requirements to be implemented over a set period. It is a detailed list of functionalities from which the Developers draw items, to be complemented by a separate Technology Backlog managed by the Developers.

When can the Product Backlog be updated?. Only after a Sprint Review if agreed to by the stakeholders. Only during Product Backlog refinement sessions if the Product Owner is present. Never, unless agreed to by the change request. At any time when done by the Product Owner or at the Product Owner's discretion.

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?. The money spent on development of the product, often a fixed cost per Sprint multiplied by the Sprints required. All investments required to conceive, develop, operate and maintain the product. The accumulated cost over the earned value of the product.

A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place. True. False.

What is the Product Owner accountable for in Scrum?. Describing an Increment at the Sprint Planning and make sure that the Developers delivers it by the end of the Sprint. Creating and sustaining a Product Backlog that maximizes value and represents the needs of the stakeholders. Refining the top level Product Backlog items until they are ready to be handed over to the Developers. Writing the User Stories so they are understandable to stakeholders.

Who creates the definition of "Done"?. The Scrum Master since they are responsible for the productivity of the Developers. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Product Owner since they are responsible for the product's success. The Scrum Team, in a collaborative effort where the result is the common denominator of all members' definitions.

What are two typical activities for a Product Owner in a Sprint?. Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items. Update the work plan for the Developers on a daily basis. Work with the Scrum Team on Product Backlog refinement. Create financial reporting upon the spent hours reported by the Scrum Team. Collaborate with stakeholders, user communities and product managers.

Incremental delivery means: Deliver nonfunctional increments in the iteration retrospectives. Release working product only after testing each increment. Improve and elaborate our Agile process with each increment delivered. Deploy functional increments over the course of the project.

Why is it imperative that the Scrum Master attend the Daily Scrum?. To document impediments. To facilitate the meeting. To get the information to update the burndown chart. They don’t have to attend – they just have to ensure that the team has it.

If the Product Owner is not collaborating with the Developers during the Sprint, what should the Scrum Master do?. Escalate to senior management. Cancel scrum until a better Product Owner is identified. Coach the Product Owner on the values and benefits of Scrum and incremental delivery.

Wich is NOT a Scrum role?. Product Owner. Developers. Project Manager. Scrum Master.

What are the purposes of the definition of "Done"? (Choose 2 answers). Help ensure the increment is releasable. Provide transparency. Document the Sprint goal. Ensure unit testing occurs.

How complete should the Sprint Backlog be at the end of the Sprint Planning meeting?. Enough to ensure there is work for the first few days of the Sprint. The Product Owner will set the threshold for completeness. Every task should be defined. It depends.

Management does not have a role within Scrum. True. False.

What outcome is expected as Scrum Teams mature?. Many of the Scrum events will be optional. The Scrum Master’s role will no longer be necessary. Their definition of done will improve to be more stringent.

There are five Scrum Teams working on a product. How many Product Owners would there be?. 5. 1. Let the team decide. It depends.

When is a Sprint finished?. When the Product Owner accepts the increment. When the definition of done is met. When the time-boxed duration is met. When the work remaining is zero.

The Product Owner is an optional attendee of the Sprint Retrospective. True. False.

Which one of the following is NOT a responsibility of the Developers?. Pull Product Backlog items for the Sprint in agreement with the Product Owner. Reorder the Product Backlog. Do the work planned in accordance with the definition of done. Determine the time for the Daily Scrum.

In the Sprint Review, the Product Backlog is re-prioritized by the stakeholders. True. False.

During which meeting do the Developers synchronize their work and progress and report any impediments to the Scrum Master for removal?. Sprint Planning meeting. Daily Scrum. Sprint Retrospective. Weekly status meeting.

Holding a Sprint 0 is the most effective way to: Define a reference architecture. Work on team development. Create a complete Product Backlog. There is no Sprint 0 in scrum.

If the Product Backlog is not ready for Sprint Planning, what happens?. Cancel the Sprint until backlog is ready. Identify enough work for the first day and set up a second Sprint Planning meeting when the Product Owner is ready. Work during Sprint Planning to refine the backlog for one Sprint.

Which statement is least accurate when providing a definition of done?. It is the exit criteria to determine whether a Product Backlog item is complete. It may vary depending on the project. It is defined by the Scrum Master. It becomes more complete over time.

What happens if the costumer no longer wants the feature that the Sprint Goal intended to meet?. The Product Owner should cancel the Sprint. The executive stakeholders should determine if the Sprint should continue. The Scrum Master should cancel the Sprint.

What is the primary purpose of the Scrum Master at the Daily Scrum?. Manage the time-box. Ensure the 3 questions are answered. Prevent interruptions. Document impediments.

The Scrum Master is a participant in the Sprint Retrospective. True. False.

Who assigns ownership of the Sprint Backlog items during the Sprint?. Whoever has the skills. Individual Team Members. There is no single owner of a Product Backlog item, all Scrum Team owns the Sprint Backlog. The Product Owner.

Scrum mandates the use of burndown charts. True. False.

The purpose of a Sprint Retrospective is for Scrum Team to: Review stories planned for the next Sprint and provide estimates. Demonstrate completed User Stories to the Product Owner. Determine what to stop doing, start doing, and continue doing. Individually provide status updates on the User Stories in progress.

When is the Sprint Backlog created?. In advance or Sprint Planning. During the Sprint. Backlog refinement. Sprint Planning.

Why would the Product Owners concern themselves with technical debt?. The total cos of ownership (TCO) of the product will be impacted if technical debt ir present and grows. The Scrum Master is responsible for technical debt management. They wouldn´t, it is an issue for Developers.

Who updates work remaining during the Sprint?. Scrum Master. Developers. Senior Executives. Product Owner.

There must be a release every Sprint. True. False.

What happen if Product Owner delegate the ordering of Product Backlog?. The User Story is moved to the next Sprint. Additional tester are added in the next Sprint. A risk of not creating a potentially shippable product occurs. The burndown chart is updated.

Who is responsible for maximizing the value of the product?. Scrum Master. Product Owner. Senior Executives. Developers.

What is typical work for a Product Owner in a Sprint? (Choose 2 answers). Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items. Update the work plan for the Developers on a daily basis. Work with the Developers on Product Backlog refinement. Create financial reporting upon the spent hours reported by the Developers. Collaborate with stakeholders, user communities and product managers. Nothing.

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

How much work must the Developers do to a Product Backlog item it selects for a Sprint?. Enough so that each Product Backlog item they select meets the Definition of Done. As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint. All development work and at least some testing. A proportional amount of time on analysis, design, programming, testing, and documentation.

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. At the Daily Scrum the Product Owner inspects the Sprint burn-down for progress towards a complete Increment and replanning the team's work. At the end of Sprint Planning the Product Owner verifies the Sprint Backlog for completeness in order to allow the Sprint to start. 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.