7776.NovoGV14.1.0

The Product Owner should have a complete and exhaustive Product Backlog before the first Sprint can start?. True. False.

What are two ways that architecture and infrastructure are handled in Scrum?. They are discussed, determined, and documented before the actual feature development Sprints. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small. They are built by a separate team through the creation of an architectural runway. They are implemented along with functional development of the product.

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

Which is the most important stakeholder Product Owners must satisfy?. The company owner or shareholders. Executive staff. The Chief Product Owner. The product´s users.

A Product Backlog is: (Choose 3 answers). An inventory of things to be done for the Product. Ordered based on priority, value, dependencies, and risk. An exhaustive list of upfront approved requirements to be implemented for the product. Managed by the Product Owner. Only visible to the Product Owner and stakeholders.

What might indicate to a Product Owner that she needs to work more with the Scrum Team?. She isn´t working full time with the Scrum Team. The increment presented at the Sprint Review does not reflect what she thought she had asked for. Developers leave the Team. The acceptance tests don't appear to be complete.

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

What is Product Owner work that a Product Owner might delegate?. Writing Product Backlog Items. Facilitating Stakeholder Involvement. Attend the Sprint Review.

The Product Backlog is ordered by: Size, where small items are at the top and large items are at the bottom. Risk, where safer items are at the top, and riskier items are at the bottom. Items are randomly arranged. Value, where the most important items are at the top at all times.

How much time must a Product Owner spend with the Developers?. 100%. 40%, or more if the stakeholders agree. However much time the Developers asks the Product Owner to be present. Enough for the Product Owner to remain up to date on the evolution of the Increment.

What is included in the Sprint Backlog?. User Stories. Tasks. Use Cases. Tests. Any of the above (or others) which are a decomposition of the selected Product Backlog items.

What is the role of the Product Owner in crafting the Sprint Goal?. The Product Owner shouldn't come to the Sprint Planning without a clearly defined Sprint Goal. The Product Owner should come to the Sprint Planning with a business objective in mind and work with the Team Scrum to craft the Sprint Goal based upon the forecast. The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal. The Product Owner must work with the stakeholders to set each Sprint's Goal.

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

Which three of the following are feedback loops in Scrum?. Daily Scrum. Sprint Review. Release Planning. Sprint Retrospective. Refinement Meeting.

During the Sprint Review it is up to the stakeholders to reorder the Product Backlog. True. False.

The Product owner must use: Release burndown diagram. Burndown chart. Feature burn-up. Critical Path Analysis. Refactoring. Project Gantt chart. None of the above.

A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team. True. False.

Which is NOT a valid consideration when ordering a Product Backlog?. Alignment with business strategy and goals. Risk. Importance to customers. Development tools and techniques. Dependencies on other Product Backlog Items.

Which two of the following are true about the Scrum Master role? (Choose 2 answers). The Scrum Master assigns tasks to Developers when they need work. The Scrum Master helps those outside the team interact with the Scrum Team. The Scrum Master teaches the ScrumTeam to keep the Scrum meetings to their timebox. The Scrum Master is responsible for updating the Sprint Burndown. At the Sprint Review, the Scrum Master identifies what has been "Done" and what has not been "Done".

What is the time-box for the Sprint Review?. 2 hours for a monthly Sprint. 4 hours for a monthly Sprint. As long as needed. 1 day. 4 hours and longer as needed.

The Developers find out during the Sprint that they are not likely to build everything they forecast. What would you expect a Product Owner to do?. Cancel the Sprint. Change the Sprint Goal. Renegotiate the selected Product Backlog items with the Developers. Skip Product Backlog refinement activities. Inform management that more resources are needed.

A product’s success is measured by: (Choose 3 answers). The impact on customer satisfaction. The delivery of upfront defined scope compared to the upfront planned time. The impact on revenue. The impact on cost. The impact on my performance rating. The impact on my boss's mood.

When can Developers cancel a Sprint?. When the Product Owner is absent too often. When functional expectations are not well understood. They cannot. Only Product Owners can cancel Sprints. When the selected Product Backlog items for the Sprint become unachievable. When a technical dependency cannot be resolved.

What are criteria to order Product Backlog items?. Value of Product Backlog items. Dependencies between Product Backlog items. Dependencies to other products. All of the above.

What three things might a Scrum Product Owner focus on to ensure his product delivers value? (Choose 3 answers). How readily his product can be absorbed and used by his customers. The size of his product in 'lines of code'. How much of the functionality of his product is being utilized. Direct customer feedback. Minimizing changes to project scope.

The "cone of uncertainty" can be used to do what?. Determine the cost of a project before it is begun. Project what will be complete by a given Sprint. Determine whether to cut quality, similar to the "Iron Triangle" of software development. Illustrate that, as a forecast lengthens, it is increasingly less certain.

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 ScrumTeam. Collaborate with stakeholders, user communities and product managers. Nothing.

How is management external to the Scrum Team involved in the Daily Scrum?. The Scrum Master speaks on their behalf. Management gives an update at the start of each Daily Scrum. The Product Owner represents their opinions. The Developers self-manages and is the only management required at the Daily Scrum.

My role as a Product Owner focuses on which two of the following? (Choose 2 answers). Writing User Stories. Working with customers and stakeholders to identify the most important product requirements. Being with the Scrum Team all the time, just in case they need me to clarify a requirement. Keeping the stakeholders informed of the project and release status.

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

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 is one person. The Product Owner role can be played by a committee or a team of people. The Product Owner can be influenced by a committee. The Product Owner is accountable for ordering the Product Backlog.

Who is responsible for managing the progress of work during a Sprint?. The Developers. The Scrum Master. The Product Owner. The most junior member of the Team.

When many Scrum Teams are working on a single product, what best describes the definition of "Done?". Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint. Each Scrum Team uses its own but must make their definition clear to all other Teams so the differences are known. All Scrum Teams must mutually define a Definition of Done and comply with the same Definition of Done. It depends.

What are two good ways for a Scrum Team to ensure security concerns are satisfied? (Choose 2 answers). Have the Scrum Team create Product Backlog items for each concern. Add a Sprint to specifically resolve all security concerns. Add security concerns to the definition of “Done”. 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.

What are two responsibilities of testers in a Scrum Team? (Choose 2 answers). Scrum has no "tester" role. Finding bugs. Verifying the work of programmers. All Developers are responsible for quality.

The Product Owner must write all of the Product Backlog items (e.g. user stories, non-functional requirements, etc.) on the Product Backlog before handing them over to the Developers. True. False.

When might a Sprint be abnormally terminated?. When it becomes clear that not everything will be finished by the end of the Sprint. When the Developers feels that the work is too hard. When the sales department has an important new opportunity. When the Sprint Goal becomes obsolete.

Which of the following practices might help the Product Owner minimize waste in developing and sustaining the Product Backlog? (Choose 2 answers). Let others manage the Product Backlog. Only fully describe Product Backlog items when it seems sure that they are likely to be implemented. Write or cause Product Backlog items to be written clearly, and with as little ambiguity as possible. Always write the Product Backlog items as computer code that will later just be tested by developers.

A product Increment must be released to production at the end of each Sprint. True. False.

When should a Sprint Goal be created?. At any time during the Sprint. It must be established before Sprint Planning in order to begin planning. During Sprint Planning. A Sprint Goal is not mandatory in Scrum. It should have been created in the previous Sprint during Product Backlog refinement.

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 may be consulted.

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?. Its productivity is likely to decrease. Its productivity is likely to increase. Its productivity is likely to stay the same.

In the middle of the Sprint, the customer decides that there are 2 new features she wants. The Product Owner could: Have the Developers add these features to the current Sprint. Have the Scrum Master add these features to the current Sprint. Introduce these features at the next Sprint Planning meeting. Introduce these features at the next Daily Scrum.

Which of the following are true about the length of the Sprint? (Choose 2 answers). 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 be long enough to make sure the Developers can deliver what is to be accomplished in the upcoming Sprint. 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. The length of the Sprint should be proportional to the work that is done in between Sprints.

Sprint Reviews are an opportune time to collect customer feedback. True. False.

Who is responsible for engaging the stakeholders?. The team manager. The business analyst. The project manager. The Developers. The Product Owner.

As the Developers starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do?. Reduce the definition of "Done" and get all of the Product Backlog items "Done" by the new definition. Inform the Product Owner at the Sprint Review, but prior to the demonstration. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items. Find another Scrum Team to give the excess work to.

How much time is required after a Sprint to prepare for the next Sprint?. The break between Sprints is time-boxed to 1 week for 30 day Sprints, and usually less for shorter Sprints. Enough time for the requirements for the next Sprint to be determined and documented. Enough time for the Developers to finish the testing from the last Sprint. None. A new Sprint starts immediately following the end of the previous Sprint. All of the above are allowed depending on the situation.

All work to be done by the Developers must ultimately originate from the Product Backlog?. True. False.

How often should customer satisfaction be measured?. Annually. Quarterly. Daily. Frequently.

In order to maximize the value of the product, a Product Owner needs awareness of the following: Competitive research. Customer feedback. Product vision. Forecasting & feasibility. All of the above. None of the above.

Who can abnormally terminate a Sprint?. The Developers. The Product Owner. The Stakeholders. The Scrum Master.

How small should a "ready" Product Backlog item be?. Small enough to build in 1 Sprint. No longer than one day. Small enough for a single team member to complete in a Sprint. No bigger than 8 story points. It should fit on a small index card.

What are advantages of a Product Owner with a solid product vision? (Choose 3 answers). It gives a good overall direction so Sprints will feel less like isolated pieces of work. It is easier to inspect incremental progress at the Sprint Review. It's not mandatory in Scrum. There's no real advantage. It helps the Scrum Team keep focus and they can check any decision against it, even within a Sprint. It helps the Scrum Team to keep focus on when the complete Product Backlog should be finished.

What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning?. The Developer has difficulties creating a forecast of work for the Sprint. Nothing in particular. It is compensated if the Product Owner gives the team a clear Sprint Goal instead. The meeting is cancelled so refinement can be done first. The Scrum Master shouldn't allow this to happen. Look for a new Scrum Master and re-start the Sprint.

Which of the following is required by Scrum?. Sprint Retrospective. Members must stand up at the Daily Scrum. Sprint Burndown Chart. Release Planning. All of the above.

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?. Refine the Product Backlog. Update the project plan with stakeholders. There are no such activities. The next Sprint starts immediately after the current Sprint. Work with the QA departments on the Increment of the current Sprint.

A PO (Product Owner) is essentially the same thing as a traditional PM (Project Manager). True. False.

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

What is the recommended size for a Scrum Team?. At least 12. 6 to 12. 9 plus or minus 3. 10 or fewer.

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.

Sprint burndown charts are an efficient tracking tool because they show: How much effort has gone into a Sprint. An estimate of the total work remaining for the Sprint. How many hours have been worked by each Developer. How many Product Backlog items remain.

What is the accountability of the Product Owner during Sprint 0?. Make sure enough Product Backlog items are refined to fill the first 3 Sprints. Determine the composition of the Developers so they have the capacity to deliver the completed forecast. Make the complete project plan to commit date, budget and scope to the stakeholders. There is no such thing as Sprint 0. Gathering, eliciting, and analyzing the requirements that will be inserted into the Product Backlog.

The Product Owner makes sure the right stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements. True. False.

When should the Product Owner update the project plan?. The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge. Before the Sprint Planning to know how much work will have to be done in the Sprint. After the Daily Scrum to ensure an accurate daily overview of project progress. Scrum forbids having a project plan. The Product Owner shouldn't be occupied by that. It is work for the Project Manager.

Who is responsible for releasing the most valuable product possible?. The Scrum Master. The Developers. The Product Owner. The CEO. The entire Scrum Team.

What is the purpose of a Sprint Review?. To take time to judge the validity of the project. To review the Scrum Team's activities and processes during the Sprint. To build team spirit. To inspect the product Increment with the stakeholders and collect feedback on next steps.

Why does the Product Owner want the Scrum Team to adhere to its definition of "Done?". To predict the team's productivity over time. To know what the team will deliver over the next three Sprints. To be able to reprimand the team when they don't meet their velocity goal for the Sprint. To have complete transparency into what has been done at the end of each Sprint.

Which technique is the best way the Scrum Master can ensure that the Developers communicates effectively with the Product Owner?. Monitor communications between them and facilitate direct collaboration. Act as a go-between for them. Teach the Developers to talk in terms of business needs and objectives. Teach the Product Owner about the technologies employed during the Sprints.

Which statement best describes the Sprint Review?. It is a mechanism to control the Developers activities during a Sprint. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. It is a demo at the end of the Sprint for everyone in the organization to check on the work done. It is used to congratulate the Developers if they did what it forecast, or to punish the Developers if they failed to meet its forecast.

When should the Product Backlog be refined? (Choose 2 answers). The Product Owner and the Developers do it in the 1-2 preceding Sprints. The Product Owner takes the time between the Sprints to do it. The Product Owner must do this as essential work in Sprint 0. The Product Owner and the Developers do it in the actual Sprint if they haven´t been able to do it in preceding Sprints. Business analysts in the organization should do this work for the Scrum Team 1-2 Sprints ahead of the development Sprints.

The Product Owner must release each Increment to production. Without exception. When it makes sense. Whenever the product is free of defects. To make sure the Developers work is done every Sprint.

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

Why is it important that there is only one Product Owner per product? (Choose 3 answers). It is clear who is accountable for the ultimate success of the product. The Developers always knows who determines priorities. It helps the economy by increasing employment. It helps avoid barriers to effective communication and rapid decision-making. The Scrum Master knows who will be his back-up whenever he goes on vacation.

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. He or she does not have to be there; he or she only has to ensure the Developers has a Daily Scrum. To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down. To gather status and progress information to report to management.

Product Owners must specify complete acceptance criteria for a Product Backlog item before the team can select the item in Sprint Planning. True. False.

What are two good ways for a Scrum Team to ensure security concerns are satisfied? (Choose 2 answers). Have the Scrum Team create Product Backlog items for each concern. Add a Sprint to specifically resolve all security concerns. Add security concerns to the definition of “Done”. 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.

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

A Product Owner can measure success by an increase in the team´s velocity. True. False.

Product dependencies could influence how the Product Owner orders Product Backlog Items. True. False.