7764.v3.0

The primary reason one might choose a four-week Sprint is when the work is too large for a two-week Sprint and cannot be decomposed further. True. False.

During the Sprint, the Scrum Master's role is to: - Facilitate inspection and adaptation opportunities as requested or needed - Assign tasks within the Scrum Team. - Assign tasks within the Scrum Team - Ensure the Product Owner attends all scrum events. - Escalate team conflicts to functional line managers - Facilitate inspection and adaptation opportunities as requested or needed. - Facilitate inspection and adaptation opportunities as requested or needed - Remove impediments.

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?. As a decomposition of the selected Product Backlog Items, the Sprint Backlog changes and may grow as the work emerges. The Sprint Backlog and its contents are fully formulated in the Sprint Planning meeting and do not change during the Sprint. 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. The Product Owner can help clarify or optimize the Sprint when asked by the Development Team.

The Product Owner remains distant. He/she has handed over the required Product Backlog for the Sprint but is not collaborating with the Development Team during the Sprint. What are valuable actions for a Scrum Master?. - Coach the Product Owner in the values of scrum and incremental delivery - Bring up the problem in the Sprint Retrospective. - Bring up the problem in the Sprint Retrospective - Stop the Sprint, send the Product Owner to a course and restart. - Stop the Sprint, send the Product Owner to a course and restart - Nominate a proxy Product Owner.

How much of the Sprint Backlog must be defined during the Sprint Planning meeting?. Enough so the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint. Just enough tasks for the Scrum Master to be confident in the Development Team`s understanding of the Sprint. All of the potential work: the Sprint Planning meeting isn`t over until 100% of the work is identified and estimated. Just enough to understand design and architectural implications.

Which statement best describes the Sprint Backlog as an outcome of the Sprint Planning?. It is a task list where every Development Team member has signed up for all the tasks that he/she intends to do in the Sprint. It is a decomposition of Product Backlog items such that enough work is decomposed for at least the first days of the Sprint. It must be ordered by the Product Owner. It is an exhaustive list of all tasks for the Sprint, and tasks must be estimated in hours. It is a list of the user stories estimated in story points, and a list of corresponding tasks that are estimated in hours.

Which two behaviors demonstrate that a team is self-organizing?. - Development team members collaboratively select their own work during the Sprint - The Development Team creates their own Sprint Backlog, reflecting all work that is part of the definition of "Done". - The Development Team members work within the boundaries of their functional description and nicely hand off work from analyst to developer to tester to integration - The Scrum Master is no longer needed. - The Scrum Master is no longer needed - The Development Team creates their own Sprint Backlog, reflecting all work that is part of the definition of "Done". - The Development Team invites external people to the Sprint Planning to ask them how to turn Product Backlog items into an Increment via a complete and detailed Sprint Backlog - Development team members collaboratively select their own work during the Sprint.

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

The IT manager asks a Development Team for a status report describing the progress throughout the Sprint. The Development Team asks the Scrum Master for advice. The Scrum Master should: Ask the Product Owner to send the manager the report. Tell the Development Team to figure it out themselves. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. Create and deliver the report to the manager herself. Tell the Development Team to fit the report into the Sprint Backlog.

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

Who has the last say on the order of the Product Backlog?. The Development Team. The CEO. The Scrum Master. The Product Owner. The stakeholders.

Which answer best describes the topics covered in Sprint Planning?. Who is on the team and what team member roles will be. How conditions have changed and how the Product Backlog should evolve. What can be done and how to do it. What went wrong in the last Sprint and what to do differently in this Sprint. What to do and who will do it.

Which of the following is the Development Team NOT responsible for?. Selecting the Product Owner. Planning how to meet a Sprint goal. Monitoring and increasing productivity. Monitoring and optimizing the work required to meet the Sprint goal at least daily. Resolving internal conflicts.

How do you know that a Development Team is cross-functional?. There are no conflicts within the Development Team. A few of the Development Team members pair program and do Test Driven Development. Development Team has all the skills to create a releasable increment by the end of every Sprint. Every member of the Development Team is able to perform every task.

What are some consequences if a Development Team does not have a consistent definition of "Done" from Sprint to Sprint?. The Development Team may not know how many Product Backlog items it can do in a Sprint. The Product Owner may not know what he/she is inspecting at the Sprint Review. The Product Owner may be unable to gauge the progress toward his/her goals. The Development Team may not know what work is entailed in completing selected Product Backlog items. All of the above.

Which Scrum Value is affected by a lack of trust in the Scrum Team?. Focus. Commitment. Courage. Openness. Respect. All of the above.

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

Why does a Development Team need a Sprint Goal?. Sprint goals are not valuable because everything is known from the Product Backlog. The Development Team is more focused through a common specific goal. A Sprint goal ensures that all of the Product Backlog items selected for the Sprint are implemented. A Sprint goal gives only purpose to Sprint 0.

As Scrum Teams mature, it is expected that the following decision is likely to be taken: The Sprint Retrospectives will grow to be longer than 4 hours. A Scrum Master is no longer needed since they are a mature team now. They will improve their definition of done to include more stringent criteria. Sprint Reviews will no longer be needed. There is no need for a time-boxed Sprint, since time-boxes are only for new Scrum Teams.

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

For which is the Scrum Master responsible?. The Scrum process being adopted and used properl. The meetings and the objectives that a Scrum Team set for itself. Keeping track of resource allocation. Managing the performance of the Scrum Team.

Development Team members step up to own a Sprint Backlog item: Whenever a team member can accommodate more work. 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. During the Daily Scrum. At the Sprint Planning meeting.

Who is responsible for registering the work estimates during a Sprint?. The most junior member of the team. The Scrum Master. The Product Owner. The Development Team.

If burndown charts are used to visualize progress, what do they track?. Accumulated business value delivered to the customer. Individual worker productivity. Accumulated cost. Work remaining across time.

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?. When the Product Owner identifies a new work. As soon as possible after they are identified. During the Daily Scrum after the Development Team approves them. When the Scrum Master has time to enter them.

What are two good ways for a Scrum Team to ensure that security concerns are satisfied?. Have the Scrum Team create Product Backlog items for each concern. Add a Sprint to specifically resolve all security concerns. Delegate the work to the concerned department. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items. Add security concerns to the definition of "Done".

The Product Backlog is ordered by: Whatever is deemed most appropriate by the Product Owner. Items are randomly arranged. Small items at the top to large items at the bottom. Least valuable items at the top to most valuable at the bottom. Safer items at the top to riskier items at the bottom.

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

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. Maintaining and preferably increasing velocity. Having an even number of team members to be able to do pair programming. Time-boxing events to manage risks. Forming teams happens by the Product Owner selecting each member. Creating a releasable Increment by the end of each Sprint.

The Product Owner must ship each Sprint increment... ... to make sure the Development Team is done every Sprint. ... without exception. ... when it makes sense. ... whenever the increment is free of defects.

What are two good ways for a Scrum Team to ensure that security concerns are satisfied?. Have the Scrum Team create Product Backlog items for each concern. Add a Sprint to specifically resolve all security concerns. Delegate the work to the concerned department. Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items. Add security concerns to the definition of "Done".

During the Daily Scrum, the Scrum Master's role is to: Facilitate discussions of the Development Team. Ensure that all three questions have been answered. Ensure that each team member has a chance to speak. Teach the Development Team to keep the Daily Scrum within the 15-minute time-box. All answers apply.

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

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

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

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?. Comply with the decision of the self-organizing team. Begin facilitating productive, useful retrospectives. Consult with the Product Owner to see how he/she feels about the situation. Call a meeting between the Development Team and senior management.

What is the purpose of a Scrum of Scrums?. Align Product Backlogs of related products by bringing their Product Owners together. Align plans for different Scrum Teams by bringing the Scrum Masters together every day. Share cross-team experiences of different Scrum Masters. Meet to report to stakeholders. Align plans of different Development Teams working on the same product.

Which two ways of creating Development Teams are consistent with Scrum´s values?. Managers personally re-assign current subordinates to new teams. The chief Product Owner determines the new team structures and assignments. Bring all the developers together and let them self-organize into Development Teams. Existing teams propose how they would like to go about organizing into the new structure. Managers collaborate to assign individuals to specific teams.

At the end of a Sprint a 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?. Put it on the Product Backlog for the Product Owner to decide what to do with it. If the stakeholders agree, the Product Owner can accept it and release it to the users. Review the item, add the"Done" part of the estimate to the velocity and create a Story for the remaining work. Do not include the item in the Increment this Sprint.

Which of the following two items are NOT topics of discussion within a Sprint Retrospective?. Definition of "Done". Team relations. Functionality implemented as a result of the Sprint. Process improvements. Sprint Backlog for the next Sprint.

Which two things does the Development Team NOT do during the first Sprint?. Develop a plan for the rest of the project. Deliver an increment of potentially shippable functionality. Develop and deliver at least one piece of functionality. Nail down the complete architecture and infrastructure.

Who is responsible for tracking the remaining work of the Sprint?. The Development Team. The Development Team in consultation with the Product Owner. The project manager. The Scrum Master. The Product Owner.

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

What is the timebox for a Daily Scrum?. 4 hours. 15 minutes. Two minutes per person. The same time of day every day. 15 minutes for a 4 week Sprint; for shorter Sprints it is usually shorter.

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 all stakeholders. The Product Owner and the Development Team. The Scrum Master, the project manager and the Development Team. The Development Team.

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

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

The maximum length of the Sprint Review (its timebox) is: 2 hours. 1 day. 4 hours and longer as needed. As long as needed. 4 hours for a monthly Sprint; for shorter Sprints it is usually shorter.

The three pillars of empirical process control are: Respect for people; kaizen; eliminating waste. Inspection; transparency; adaptation. Planning; inspection; adaptation. Transparency; eliminating waste; kaizen. Planning; demonstration; retrospective.

Who has the final say on the order of the Product Backlog?. The Scrum Master. The Product Owner. The Development Team. The CEO. The stakeholders.

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

If quality assurance work does not occur as part of the development work within a Sprint, which benefits are lost? (Choose 3 answers). The project manager cannot effectively update the plan. The increment is probably not releasable. Future Sprints will probably be interrupted with bugs that are being found. The indication of progress on the Product Backlog is not transparent.

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?. Inform management and ask them to solve it. Allow the Development Team to self-manage and determine for itself what to do. Ask the Development Team members to alternate who is responsible for meeting setup. Set up the meeting and tell the Development Team that is how it will be done.

Who is responsible for clearly expressing Product Backlog items?. The Product Owner. The Scrum Master. The business analyst who represents the Product Owner in the Development Team. The stakeholders.

Which of the following best describes an increment of working software?. 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. Additional features in a useable state that complement those delivered in previous iterations. A new user interface design for functionality delivered in previous iterations. An automated test suite to verify functionality delivered in previous iterations.

Items on the Product Backlog tend to be: The same size as the items in the Sprint Backlog. It depends. Larger than the items in the Sprint Backlog. Smaller than the items in the Sprint Backlog.

Which of the following are NOT time-boxed events in Scrum? (Choose 4 answers). Sprint 0. Sprint testing. Release testing. Sprint Retrospective. Daily Scrum. Release Retrospective. Sprint Planning.

What are two responsibilities of testers in a Development Team? (choose 2 answers). Everyone in the Development Team is responsible for quality. Finding bugs. Tracking quality metrics. Scrum has no "tester" role. Verifying the work of programmers.

How often should Development Team membership change?. As needed, while taking into account a short term reduction in productivity. Just as it would on any Development Team, with no special allowance for changes in productivity. Never, because it reduces productivity. Every Sprint, to promote shared learning.

Who is responsible for engaging the stakeholders?. The Development Team. The Team Manager. The Project Manager. The Business Analyst. The Product Owner.

Which of the following are true about the Product Owner role? (Choose 3 answers). Multiple people can share the Product Owner role on a Scrum Team. The Product Owner can be influenced by a committee. The Product Owner role can be played by a committee or a team of people. The Product Owner is accountable for ordering the Product Backlog. The Product Owner is one person.

When is implementation of a Product Backlog item considered complete?. When QA reports that it passes all acceptance criteria. At the end of the Sprint. When all work in the Sprint Backlog that is related to it is complete. The item has no work remaining that must still be done before it can be used by its end user.

Who determines how work is performed during the Sprint?. Development team managers. Subject matter experts. The Development Team. Architects. The Scrum Master.

A Sprint Retrospective should be held: At the beginning of each Sprint. At the end of the last Sprint in a project or a release. Only when the Scrum Team determines it needs one. At the end of each Sprint.

When can a Development Team cancel a Sprint?. The Product Owner is absent too often. Functional expectations are not well understood. It can´t - only Product Owners can cancel Sprints. A technical dependency cannot be resolved. The forecast for the Sprint becomes un-achievable. Answers A or D.

Every Scrum Team must have a Product Owner (PO) and a Scrum Master (SM). False; a Product Owner can be replaced by a business analyst in the Development Team. True; each must be 100% dedicated to the Scrum Team. True; outcomes are affected by their participation and availability. False; a Scrum Master is only required when asked for by the Development Team.

Which technique is the LEAST productive way for the Scrum Master to ensure that the Development Team communicates effectively with the Product Owner?. Teach the team to talk in terms of business needs and objectives. Teach the Product Owner about the technologies employed during the Sprints. Act as a go-between for them. Monitor communications between them.

Which of the following is true about Scrum? (Choose 3 answers). Scrum is like traditional processes but with self-organization to replace project managers. Scrum is based on empirical process control theory. Scrum is a methodology where you can pick and choose which parts of scrum you think will work for your environment. Scrum is a framework for developing and maintaining complex products. Each component of scrum serves a specific purpose, and is essential to scrum´s success and your usage of scrum to develop complex products.

The definition of “Done” is used to: (Choose 3 answers). Describe the work that must be done before the Sprint can end. Guide the Development Team on how many Product Backlog Items to do in a Sprint. Describe purpose, objective, and timebox of each Scrum event. Create a shared understanding of when work is complete. Increase transparency.

Which of these may a Development Team deliver at the end of a Sprint?. Failing unit tests, to identify acceptance tests for the next Sprint. An increment of software with minor known bugs in it. A single document, if that is what the Scrum Master asked for. An increment of working software that is "Done".

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

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?. Without a new vocabulary as a reminder of the change, very little change may actually happen. The organization may not understand what has changed with scrum and the benefits of scrum may be lost. Management may feel less anxious. All answers may apply.

What are three benefits of self-organization? (Choose 3 answers). Increased self-accountability. Increased rule compliance. Increased commitment. Increased creativity. Increased predictability.

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

Why should the Product Owner be present at the Daily Scrum?. To participate as a Scrum Team member. To represent the stakeholders´ point of view. He/She doesn´t need to be there. To hear about impediments in functionality.

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

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

What happens if the Development Team cannot complete its work by the end of a time-box?. Scrum should be abandoned. The time-box holds and the Development Team continuously learns what is actually possible to do within a time-box. The time-box is adjusted permanently to reflect reality. The time-box is extended temporarily; lessons are taken to ensure it doesn´t happen again.

An abnormal termination of a Sprint is called when?. When the team feels that the work is too hard. When it is clear at the end of a Sprint that everything won´t be finished. When the Product Owner determines that it makes no sense to finish it. When sales has an important opportunity.

Which of the following is true about the Scrum Master role? (Choose 2 answers). The Scrum Master teaches the Development Team to keep the scrum meetings to their time-box. At the Sprint Review, the Scrum Master identifies what has been "Done" and what has not been "Done". The Scrum Master assigns tasks to Development Team members when they need work. The Scrum Master is responsible for updating the Sprint burndown. The Scrum Master helps those outside the team interact with the Scrum Team.

Drawing a trend line through a release burndown chart indicates... When the work remaining will likely be completed if nothing changes on Product Backlog or on Development Team. When all Sprint Backlog work will be completed & ScrumTeam will be released for other work. When the project will be over if Product Owner removes work that is equal in effort to any new work added. Cost of the project.