There are many ways to support us; in exchange, you'll get this material in a proper format:
- ❤️ shop.ditectrev.com, in EPUB or PDF formats, with answers marked,
- ❤️ shop.ditectrev.com, in EPUB or PDF formats, without answers marked,
- 📖 Udemy is the only one to have explanations for questions,
- 📚 Google Play Books, in PDF format, with answers marked,
- 📚 Google Play Books, in PDF format, without answers marked,
- 🛍️ Etsy, in PDF format, with answers marked,
- 🛍️ Etsy, in PDF format, without answers marked,
- 🛒 eBay, in PDF format, with answers marked,
- 🛒 eBay, in PDF format, without answers marked,
- 🔄 Patreon subscription allows you to get access to all of the materials in EPUB and PDF formats. You can also buy separate items on Patreon, but the subscription technically allows us to include all updates for EPUB and PDF formats. Hence, you get EPUB and PDF updates when you subscribe to Patreon.
💰 If you work for a company, you could probably easily claim this expense while preparing for your exam. For us, it's about being in the game or not.
⭐ Good ratings & reviews help us to survive. Please don't forget to leave a nice one when you purchase an item.
✋ Join a live online community and a course taught by industry experts and pass the Scrum Product Owner (PSPO I) confidently. We aim to build an ecosystem of Information Technology (IT) certifications and online courses in cooperation with the technology industry. We believe it will give our students 100% confidence in the pacing market in an open-source environment. We are just at the beginning of our way, so it's even better for you to join now!
- Always happy to answer your questions on Udemy's Q&A's and outside :)
- Failed? Please submit a screenshot of your exam result and request a refund (via our upcoming platform, not possible on Udemy); we'll always accept it.
- Learn about topics, such as:
- Accountability in Scrum;
- Definition of Done (DoD);
- Product Backlog;
- Scrum;
- Scrum Daily;
- Scrum Team;
- Scrum Value;
- Self-management;
- Sprint Backlog;
- Sprint Goal;
- Sprint Planning;
- Sprint Retrospective;
- Sprint Review;
- Much More!
- Questions are similar to the actual exam, without duplications (like in other courses ;-)).
- The Practice Tests Exams simulate the actual exam's content, timing, and percentage required to pass the exam.
- This course is not a Scrum Product Owner (PSPO I) Exam Dump. Some people use brain dumps or exam dumps, but that's absurd, which we don't practice.
- 264 unique questions.
v1.0.0: January 25, 2023.
- Launch of the course.
v1.0.1: May 7, 2023.
- Fix 2 questions with minor improvements.
v1.1.0: July 13, 2023.
- Fix 8 questions with correct answers.
v1.1.1: November 16, 2023.
- Fix all remaining typos with support of automated proofreading software.
v1.1.1: July 30, 2024.
- AI-generated explanations (only paid Udemy).
v1.1.2: September 9, 2024.
- Fix 1 question with correct answer.
We are so thankful for every contribution, which makes sure we can deliver top-notch content. Whenever you find a missing resource, broken link in a Table of Contents, the wrong answer, please submit an issue. Even better would be a Pull Request (PR).
- 👨🎓 Students preparing for the Scrum Product Owner (PSPO I) Exam;
- 👨🎓 Agile Coaches;
- 👨🎓 Agile Leaders;
- 👨🎓 DevOps Engineers;
- 👨🎓 IT Professionals;
- 👨🎓 Lead Engineers;
- 👨🎓 Scrum Masters;
- 👨🎓 Software Developers/Engineers;
- 👨🎓 Software Testers;
- 👨🎓 Product Managers;
- 👨🎓 Product Owners;
- 👨🎓 Project Managers;
- 👨🎓 Team Leaders.
- 🤩 Excitement to learn!
- 0️⃣ Prior knowledge is required;
- ✅ You can pass the Scrum Product Owner (PSPO I) Exam solely based on our Practice Tests Exams.
A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog? Stability requirements. Performance requirements. Product Functionality. Documentation. Fixes. (choose the best answer)
- Yes, they all belong on the Product Backlog. Product Backlog is supposed to be the Single Source of Truth for all the work for the product.
- No, Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholders. Other types of requirements should be managed separately by the Developers. They are not the Product Owner's concern.
What variables should a Product Owner consider when ordering the Product Backlog? (choose the best answer)
- Development cohesion as indicated by the Developers.
- The availability of resources and skills for implementation.
- Lowest development cost in order to maximize Return on Investment (ROI).
- Effort first, then value.
- Anything that informs them to achieve the product's goals and to optimize the value delivered.
It is mandatory for the Product Owner to monitor and share progress of the Product Backlog by using which method? (choose the best answer)
- 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.
The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog Items? (choose the best answer)
- The Developers.
- The PMO.
- The Product Owner.
True or False: The Sprint Review is the only time at which stakeholder feedback is taken into account.
- True.
- False.
How do timeboxes help the Product Owner and the other members of the Scrum Team validate assumptions, adapt, and maximize the value of their product? (choose the best answer)
- Timeboxes help by making sure a Sprint does not stop until all testing is done, and the work is verified by the Product Owner.
- Timeboxes assure the Product Owner that the Developers will finish all work on the Sprint Backlog by the end of the Sprint.
- Timeboxes help minimize risk by creating the opportunity to validate assumptions using feedback from users and the market; allowing Scrum Teams to inspect progress toward the Product Goal and decide whether to pivot or persevere.
- At the end of each Sprint when the timebox expires a detailed report with all test cases and test results is available.
- True.
- False.
True or False: The Scrum Team must choose at least one high priority process improvement item, identified during the Sprint Retrospective, and place it in the Sprint Backlog.
- True.
- False.
How important is it for a Product Owner to order Product Backlog Items by using value points? (choose the best answer)
- Calculating value points is a predictive approach that conflicts with the empiricism of Scrum, and is therefore not acceptable.
- Using value points is the ultimate way for a Product Owner to predict the value that the product will provide.
- The Product Owner may order the Product Backlog by using value points or select another technique, the decision is up to them.
- Never, unless agreed to by the change request.
- At any time when done by the Product Owner or a delegate.
- Only after a Sprint Review if agreed to by the stakeholders.
- Only during Product Backlog Refinement sessions if the Product Owner is present.
True or False: The Product Owner should have the entire Product Backlog documented in detail before the first Sprint can start?
- True.
- False.
- True.
- False.
Who is accountable for creating a valuable and usable Increment each Sprint? (choose the best answer)
- The Scrum Master.
- The CEO.
- The Developers.
- The Scrum Team.
- The Product Owner.
What are two effective ways for the Scrum Team to make non-functional requirements visible? (choose the best two answers)
- Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
- Add them to the Product Backlog to ensure transparency.
- Put them on a separate list on the Scrum board, available for all to see.
- Add them to the Definition of Done so the work is taken care of every Sprint.
- Determine the length of the next Sprint.
- Determine the cost of a project before it begins.
- Determine whether to cut quality, similar to the Iron Triangle of project management.
- Illustrate that as a project forecast lengthens, it is increasingly less certain.
- Risk.
- Tools and techniques.
- Importance to customers.
- Alignment with business strategy and goals.
- Dependencies on other Product Backlog Items.
True or False: The Product Owner must write all of the Product Backlog Items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team.
- True.
- False.
- Value of Product Backlog Items.
- Dependencies between Product Backlog Items.
- Dependencies to other products.
- The availability of the Scrum Master.
- All of the above.
All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Which two measures ensure that the Product Backlog is transparent? (choose the best two answers)
- The Product Backlog is managed using a web-based tool.
- The Product Backlog is available to all stakeholders.
- The Product Backlog is ordered.
- Each Product Backlog Item has a MoSCoW priority.
- The Product Backlog only has work for the next 2 Sprints.
Why is it important that there is only one Product Owner per product? (choose the best three answers)
- The Scrum Team always knows who determines the order of the Product Backlog.
- The Scrum Master knows who acts as their backup while on vacation.
- It is clear who is accountable for the ultimate value of the product.
- It would confuse the stakeholders if they had to work with more than one person.
- It helps avoid barriers to effective communication and rapid decision-making.
Which of the following practices might help the Product Owner minimize waste in developing and sustaining the Product Backlog? (choose the best two answers)
- Avoid distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood.
- Only fully describe Product Backlog items when it seems likely they will be implemented.
- Hand off ownership of the Product Backlog to someone else.
- Remove items from the Product Backlog that have not been addressed in a long time.
True or False: Product Owners must create clear and unambiguous acceptance criteria for each Product Backlog Item before it may be selected in Sprint Planning.
- True.
- False.
What three things might a Scrum Product Owner focus on to ensure the product delivers value? (choose the best three answers)
- Minimizing changes to project scope.
- How much of the functionality of the product is being used.
- How quickly or easily the product can be absorbed and used by its customers.
- Direct customer feedback.
- Velocity is increasing over time.
- Quarterly.
- Annually.
- Daily.
- Frequently.
Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done? (choose the best two answers)
- To be able to punish the team when they do not meet their velocity goal for the Sprint.
- The Product Owner should not care about the Definition of Done, it is the Scrum Team's responsibility.
- The Definition of Done can affect the product's total cost of ownership.
- To have complete transparency into what has been done at the end of each Sprint.
- To forecast the team's productivity over time.
- The impact on customer satisfaction.
- The impact on cost.
- The impact on my boss's mood.
- The delivery of upfront defend scope compared to the upfront planned time.
- The impact on my performance rating.
- The impact on revenue.
- True.
- False.
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency? (choose the best answer)
- The Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
- Product Backlog Items must be sized such that the highest ordered items are no bigger than a Sprint.
- The Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
- Product Backlog Items should hold no more than 8 points of work, which is the average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.
- The Product Backlog is continually kept up to date with the most recent insights.
What is the responsibility of the Product Owner in crafting the Sprint Goal? (choose the best answer)
- The Product Owner has no responsibility in it. This is the Developers responsibility.
- The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal.
- The Product Owner should not 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 Developers to craft the Sprint Goal.
- The Product Owner must work with stakeholders to set each Sprint's Goal.
- The Product Backlog is the plan in Scrum. It is updated as new information and insights emerge.
- The project plan must be updated prior to the Sprint Retrospective.
- 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.
- Managed by the Product Owner.
- Only visible to the Product Owner and stakeholders.
- An exhaustive list of upfront approved requirements to be implemented.
- Ordered based on priority, value, dependencies, and risk.
- An inventory of things to be done for the Product.
- As much time as the Developers ask the Product Owner to be present.
- 100%.
- Enough so that the Product Owner is confident, the Increment will meet the intended value.
- 40%, or more if the stakeholders agree.
Which metrics will help a Product Owner determine if a product delivering value? (choose the best two answers)
- Velocity.
- Productivity.
- Time to market.
- Customer satisfaction.
- Percentage of scope implemented.
True or False: All planned work for the Product done by the Scrum Team must originate from the Product Backlog.
- True.
- False.
What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning? (choose the best answer)
- The Product Owner should select the Sprint Goal for the Scrum Team so that work can begin.
- The Developers will find it difficult to create a Sprint forecast they are confident they can meet.
- Nothing in particular.
- The Scrum Master should not allow this to happen. Look for a new Scrum Master and restart the Sprint.
- Sprint Planning is cancelled so refinement can be done first.
- True.
- False.
- True.
- False.
What might indicate to a Product Owner that she needs to work more with the Scrum Team? (choose the best answer)
- People leave the Scrum Team.
- She is not working fulltime with the Scrum Team.
- The acceptance criteria do not appear to be complete.
- The Increment presented at the Sprint Review does not reflect what she thought she had asked for.
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
- Delegate the work to the security 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.
- Add a Sprint to specifically resolve all security concerns.
- Have the Scrum Team create Product Backlog Items for each concern.
You are the Scrum Master for four Scrum Teams working from the same Product Backlog. Several of the Developers come to you complaining that work identified for the upcoming two Sprints will require full-time commitment from a specialist who is external to the teams. What should the Scrum Master consider in this situation? (choose the best two answers)
- The need to have enough work to keep all Developers busy.
- The ability of the Scrum Teams to produce integrated Increments.
- The desire to maintain a stable velocity.
- The benefit of Developers figuring out a solution for themselves.
In order to maximize the value of the product, a Product Owner needs awareness of the following: (choose the best answer)
- Competitive reasearch.
- Customer feedback.
- Product vision.
- Forecasting & feasibility
- All of the above.
- None of the above.
The Developers ask their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a component. Without that component there will not be enough work in the next Sprint to occupy the full team. As the Scrum Master, what advice would you give the Product Owner? (choose the best answer)
- Tell the Product Owner that the Product Backog should be ordered to maximize utilization of the Developers.
- Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate Sprint.
- Remind the Product Owner that their primary concern is the flow of value reflected in the ordering of the Product Backlog.
A Project Manager working with your Scrum Team has raised concerns about progress and money spent. What are the two best responses? (choose the best two answers)
- Show the Earned Value Analysis (EVA) report.
- Scrum does not have Project Managers so disregard their concerns.
- Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access.
- Share the last stakeholder briefing document prepared by the Product Owner.
- Have a discussion with the Project Manager, share the current impediments and forecast for the Sprint.
The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has final say over the Definition of Done? (choose the best answer)
- Yes, the Product Owner decides the Definition of Done. The Developers may be consulted.
- No, the Scrum Team decides the Definition of Done. The Product Owner is just one member of the Scrum Team.
- A defined and predictive process that conforms to the principles of Scientific Management.
- A framework to generate value through adaptive solutions for complex problems.
- A cookbook that defines best practices for software development.
- A complete methodology that defines how to develop software.
- Nothing.
- Working with the Scrum Team on Product Backlog Refinement.
- Attending every Daily Scrum to answer questions about the Sprint Backlog items.
- Updating the work plan for the Developers on a daily basis.
- Collaborating with stakeholders, users and customers.
- Creating financial reporting upon the spent hours reported by the Developers.
True or False: Product Owners must specify complete acceptance criteria for a Product Backlog Item before the Developers can select the item in Sprint Planning.
- True.
- False.
- The Scrum Master.
- The Developers.
- The Project Manager.
- The Product Owner.
- Complete the project within the date and cost as calculated by the Product Owner.
- Turn Product Backlog Items into a valuable, useful Increment.
- Do all of the development work, except for specialized testing that requires additional tools and environments.
- Sprint 0.
- Release Retrospective.
- Sprint Retrospective.
- Daily Scrum.
- Sprint Planning.
- Release Planning.
- Sprint Testing.
- The person who has the token.
- Whoever the Developers decide should start.
- The person coming in last. This encourages people to be on time and helps to stay within the timebox.
- The Product Owner.
- The Scrum Master. This ensures that the Developers have the event, and it stays within the timebox.
Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum? (choose the best answer)
- Lead the discussions.
- Make sure that all 3 questions have been answered by each member of the team.
- Keep track of whether each Developer has a chance to speak.
- Teach the Developers to keep the Daily Scrum within 15 minutes.
- All of the above.
- True.
- False.
- Scrum Master.
- Product Owner.
- Developers.
- Project Manager.
- None of the above.
What tactic should a Scrum Master use to divide a group of 100 people into multiple Scrum Teams? (choose the best answer)
- Ask the people to divide themselves into 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.
- The length of the Sprint should be proportional to the work that is done in between Sprints.
- 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 Scrum Team can deliver what is to be accomplished in the upcoming Sprint.
- All Sprints must be one month or less.
Which are appropriate topics for discussion in a Sprint Retrospective? (choose the best three answers)
- Definition of Done.
- Arranging the Sprint Backlog for the next Sprint.
- How the Scrum Team does its work.
- Team relations.
- The value of work currently represented in the Product Backlog.
True or False: The Product Owner makes sure the correct stakeholders are invited to the Sprint Retrospective. They might have important instructions for team improvements.
- True.
- False.
Who has the final decision about the order of items in the Product Backlog? (choose the best answer)
- The Scrum Team.
- The Product Owner.
- The Scrum Master.
- The Stakeholders.
- The Developers.
What are the two primary ways a Scrum Master helps a Scrum Team work at its highest level of productivity? (choose the best two answers)
- By ensuring the meetings start and end at the proper time.
- By facilitating Scrum Team decisions.
- By keeping high value features high in the Product Backlog.
- By removing impediments that hinder the Scrum Team.
During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog? (choose the best answer)
- When the Product Owner identifies new work.
- When the Scrum Master has time to enter it.
- As soon as possible after it is identified.
- During the Daily Scrum after the Developers approve it.
True or False: A high-performance Scrum Team ensures that each Increment is complete by running a Release Sprint.
- True.
- False.
The Developers select 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 the best three answers)
- It tracks the percentage complete of a Product Backlog Item.
- It defines what it takes for an Increment to be ready for release.
- It creates transparency over the work inspected at the Sprint Review.
- It guides the Developers in creating a forecast at the Sprint Planning.
- It provides a template for elements that need to be included in the documentation.
- It controls whether the Developers have performed their tasks.
- Increased self-accountability.
- Increased rule compliance.
- Increased creativity.
- Increased commitment.
- Increased accuracy of estimates.
A new Developer is having continuing conflicts with existing members of the Scrum Team, which is impacting the delivery of the Increment. If necessary, who is responsible for removing the Developer from the Scrum Team? (choose the best answer)
- The hiring manager is responsible, they hired the Developer.
- The Product Owner is responsible, they control the return on investment (ROI).
- The Scrum Team is responsible.
- The Scrum Master is responsible, they remove impediments.
A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team. Which of the following can be delegated to others, while the Product Owner remains accountable for the work? (choose the best two answers)
- Attending the Sprint Review.
- Ordering Product Backlog Items.
- Developing and communicating the Product Goal.
- Attending the Sprint Retrospective.
During a Sprint Retrospective, the Developers propose moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master to recommend? (choose the best two answers)
- Consider the request and decide on which days the Daily Scrum should occur.
- Coach the team on why the Daily Scrum is important as an opportunity to update the plan.
- Acknowledge and support the self-managing team's decision.
- Have the Developers vote.
- Learn why the Developers want this and work with them to improve the outcome of the Daily Scrum.
During the Sprint Retrospective a Scrum Team has identified several high priority process improvements. Which of the following statements is most accurate? (choose the best answer)
- The Scrum Team may add the items to the Sprint Backlog for the next Sprint.
- The Scrum Team should choose at least one high priority process improvement to place in the Product Backlog.
- The Scrum Team should decline to add a process improvement to the Sprint Backlog when things are running smoothly.
- The Scrum Master selects the most important process improvement and places it in the Sprint Backlog.
How is management that is external to the Scrum Team involved in the Daily Scrum? (choose the best answer)
- The Product Owner represents their opinions.
- Managers are not required at the Daily Scrum.
- The Scrum Master speaks on their behalf.
- Management gives an update at the start of each Daily Scrum.
- The break between Sprints is timeboxed to one-week for a one-month Sprint, 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.
How much work is required of the Developers to complete a Product Backlog Item selected during the Sprint Planning? (choose the best answer)
- As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
- As much as is required to meet the Scrum Team's Definition of Done.
- All development work and at least some testing.
- A proportional amount of time on analysis, design, development, and testing.
- Every Sprint to promote shared learning.
- As needed, with no special allowance for changes in productivity.
- Never, it reduces productivity.
- As needed, while taking into account a short-term reduction in productivity.
If Product Backlog Refinement is needed, when is the ideal time for refinement to take place and who should participate? (choose the best two answers)
- 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 do this as essential work in Sprint 0.
- The Scrum Team on an ongoing basis, defining Product Backlog Items into smaller more precise items that are ready for selection.
- The Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog Items with enough precision to begin work.
- The Product Owner takes the time between the end of one Sprint and the start of the next Sprint to complete refinement.
Scrum requires that the Product Owner must use which of the following items? (choose all that apply)
- Burndown chart.
- Feature burn-up.
- Critical Path Analysis.
- Project Gantt Chart.
- None of the above.
True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.
- True.
- False.
- True.
- False.
What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team? (choose the best three answers)
- It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal.
- It helps the Developers estimate the date that the Product Backlog will be complete.
- It is easier to inspect Incremental progress at the Sprint Review.
- It is not mandatory in Scrum. There is no real advantage.
- It provides a good overall direction so Sprints will feel less like isolated pieces of work.
Which approach is best for Scrum Teams in order to produce valuable Increments? (choose the best answer)
- Each Developer works on the component where they feel that they can contribute.
- Each Scrum Team is accountable for developing functionality from beginning to end.
- Each Scrum Team works on an independent set of components.
- Each Scrum Member works only as an independent layer of the system.
- The Product Owner.
- The Developers.
- The most junior member of the team.
- The Scrum Master.
Who is part of the discussion about which Product Backlog Items are selected for a Sprint? (choose the best answer)
- The Product Owner.
- The Scrum Master.
- The Scrum Team.
- The Developers.
Why does the Product Owner want the Developers to adhere to its Definition of Done? (choose the best answer)
- To predict the teams productivity over time.
- To have complete transparency into what has been done at the end of each Sprint.
- To know what the team will deliver over the next three Sprints.
- To be able to reprimand the team when they do not meet their velocity goal for the Sprint.
Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product. You have gathered a number of requirements and ideas into an early form of a Product Backlog. How would you minimize dependencies between the Scrum Teams? (choose the best answer)
- You work with the Developers on how to best analyze and break apart the work.
- You divide Product Backlog Items among the six Product Owners.
- You create an independent Product Backlog per Scrum Team.
- You identify the dependencies and re-order the Product Backlog for the other five Product Owners.
- You raise this as an impediment with the Scrum Master.
- The event must take at least a minimum amount of time.
- The event must happen at a set time.
- The event can take no more than a maximum amount of time.
- The event must happen by a given time.
- True.
- False.
When is it most appropriate for a Scrum Team to change the Definition of Done? (choose the best answer)
- Prior to starting a new project.
- During the Sprint Retrospective.
- During Product Backlog Refinement.
- During Sprint Planning.
- True.
- False.
- The Developers are more focused with a common yet specific goal.
- Sprint Goals are not valuable. Everything is known from the Product Backlog.
- A Sprint Goal only gives purpose to Sprint 0.
- Sprint Goal ensures that all of the Product Backlog Items selected for the Sprint are implemented.
- The Scrum Master.
- The Product Owner with input from the Developers.
- The Developers after clarifying requirements with the Product Owner.
- The most senior people in the organization, including architects and subject matter experts.
- The Developers, alone.
- False, a Scrum Master is only required when asked for by the Development Team.
- True, outcomes are affected by their participation and availability.
- True, each must be 100% dedicated to their Scrum Team.
- False, a Product Owner can be replaced by a Business Analyst among Developer.
- The Scrum process, and how it was used during the Sprint.
- Coding and engineering practices.
- The product Increment.
- All of the above.
Five new Scrum Teams have been created to build one product. A few of the Developers on one of the Scrum Teams ask the Scrum Master who will coordinate the work with the other teams. What should the Scrum Master do? (choose the best answer)
- 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.
- Teach them that it is their responsibility to work with the other teams to create an Increment that is inclusive of all five team's work.
- Teach the Product Owner to work with the Lead Developer on ordering Product Backlog in a way to avoid too much overlap during a Sprint.
- Visit the five teams each day to inspect that their Sprint Backlogs are aligned.
True or False: Cross-functional teams are optimized to work on one component or layer of a system only.
- True.
- False.
- Tracking quality metrics.
- Scrum has no "Tester" role.
- Verifying the work of programmers.
- The Developers are responsible for quality.
- Finding bugs.
Which two ways of creating Scrum Teams are consistent with Scrum's values? (choose the best two answers)
- Existing teams propose how they would like to go about organizing into the new structure.
- Bring all people together and let them organize into Scrum Teams.
- Managers personally re-assign current subordinates to new teams.
- The chief Product Owner determines the new team structure and assignments.
- Managers collaborate to assign individuals into specific teams.
- True.
- False.
- The Monday following the Sprint Review.
- Immediately after the conclusion of the previous Sprint.
- Immediately following the next Sprint Planning.
- When the Product Owner is ready.
- True.
- False.
- There is no such thing as Sprint 0.
- Create the overall release plan to ensure that organizational goals are met.
- Determine the composition of the Scrum Team to meet the release plan.
- Gathering, eliciting and analyzing the requirements to build the Product Backlog.
- Make sure enough Product backlog items are refined to fill the first 3 Sprints.
True or False: When there are multiple teams working on one product, each Scrum Team should have a separate Product Owner.
- True.
- False.
- Who is the team and what team member roles will be.
- What to do and who will do it.
- What can be done, how to do it, and why to do it.
- What went wrong in the last Sprint and what to do differently this Sprint.
- How conditions have changed and how the Product Backlog should evolve.
Which of the following might the Scrum Team discuss during a Sprint Retrospective? (choose the best answer)
- Methods of communication.
- The way the Scrum Team does Sprint Planning.
- Skills needed to improve the Scrum Teams ability to deliver.
- The Definition of Done.
- 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? (choose the best answer)
- 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 of the above.
- Release Planning.
- Refinement Meeting.
- Sprint Retrospective.
- Sprint Review.
- Daily Scrum.
The IT manager asks the Scrum Team for a status report describing the progress throughout the Sprint. The Scrum Team ask the Scrum Master for advice. The Scrum Master should: (choose the best answer)
- Create and deliver the report to the manager herself.
- Tell the Developers to figure it out themselves.
- Tell the Developers to fit the report into the Sprint Backlog.
- Talk to the IT manager and explain that the progress in Scrum comes from inspecting an Increment at the Sprint Review.
- Ask the Product Owner to send the manager the report.
What happens if the Scrum Team cannot complete its work by the end of the Sprint? (choose the best answer)
- The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
- The Sprint is extended temporarily. Lessons are taken to ensure it does not happen again.
- The Sprint is extended and future Sprints use this new duration.
User documentation is part of your Definition of Done. However, there are not enough Technical Writers for all teams. Your Scrum Team does not have a Technical Writer. What should the Scrum Team do? (choose the best answer)
- Wait until you have a Technical Writer on your Scrum Team to take care of this.
- Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available Technical Writers.
- The Developers on the Scrum Team should write the user documentation.
- Form a separate team of Technical Writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
The Scrum Master observes the Product Owner is struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take? (choose the best answer)
- Present the Product Owner with an ordered Product Backlog to use.
- Suggest that the Developers order the Product Backlog to be sure that it is a feasible ordering of work.
- Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.
- Encourage the Product Owner to work with the Developers to see which items technically are fastest to implement.
- Suggest the Product Owner extend the Sprint, so he can have more time to order the Product Backlog.
- When they need to represent the stakeholders' point of view.
- When the Scrum Master asks them to attend.
- When there are impediments to discuss.
- When the Product Owner is actively working on items from the Sprint Backlog.
How much of the Sprint Backlog must be defined during the Sprint Planning event? (choose the best answer)
- Just enough to understand design and architectural implications.
- Just enough tasks for the Scrum Master to be confident in the Developers' understanding of the Sprint.
- The entire Sprint Backlog must be identified and estimated by the end of Sprint Planning.
- Enough so the Developers can create their forecast of what work they can do.
You are the Scrum Master of a new, to be developed Product. Development is going to require 45 people. What is a good first question for you to suggest the group thinks about when forming into teams? (choose the best answer)
- What is the right mixture of senior and junior people on each team?
- How will we make sure all teams have the right amount of expertise?
- Who are the subject matter experts on each team?
- Who are going to be the team leads?
What activities would a Product Owner typically undertake in the period between the end of the current Sprint and the start of the next Sprint? (choose the best answer)
- There are no such activities, the next Sprint starts immediately after the current Sprint.
- Update the project plan with stakeholders.
- Work with the Quality Assurance departments on the Increment of the current Sprint.
- Refine the Product Backlog.
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the quality of the product. What are two good options for the Scrum Master? (choose the best two answers)
- Explain to the Product Owner that it is up to the Developers to decide on acceptable quality standards.
- Encourage the Product Owner to put quality specifications on the Product Backlog and express the stakeholder's concern to the Developers.
- Coach the Product Owner on how to talk with the Developers about this concern.
- Bring the concern to the Testers to improve how the Product is verified.
- Wait to bring this up until the Sprint Retrospective.
As the Developers start work during the Sprint, they realize they have selected too much work to finish the Sprint. What should they do? (choose the best answer)
- Inform the Product Owner at the Sprint review, but prior to the demonstration.
- Find another Scrum Team to give the excess work to.
- Reduce the Definition of Done and get all of the Product Backlog Items done by the new definition.
- As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog Items.
Who does the work to make sure Product Backlog Items conform to the Definition of Done? (choose the best answer)
- The Quality Assurance Team.
- The Scrum Master.
- The Product Owner.
- The Developers.
- The Scrum Team.
Which two things are appropriate for a Scrum Master to do if the Scrum Team does not have the tools and environment to completely finish each selected Product Backlog Item? (choose the best two answers)
- Encourage the Product Owner to accept partially done Increments until the situation improves.
- Have the Scrum Team establish a Definition of Done that is actually possible to achieve given current circumstances.
- Declare the Scrum Team not ready for Scrum.
- Refocus the current Sprint on establishing the Scrum Team's environment instead of delivering an Increment.
- Coach the Scrum Team to improve its skills: tools and environment over time and adjust the Definition of Done accordingly.
For the purpose of transparency, when does Scrum say a valuable and useful Increment must be available? (choose the best answer)
- Every 3 Sprints.
- When the Product Owner asks to create one.
- After the Acceptance Testing phase.
- At the end of every Sprint.
- Before the Release Sprint.
- The Product Owner.
- The Business Analyst who represents the Product Owner.
- The Scrum Master.
- The Scrum Master, or the Scrum Master may have the Developers do it.
- It is a mechanism to control the Developers activities during a Sprint.
- It is used to congratulate the Developers if they complete their forecast or to punish the Developers if they fail to meet their forecast.
- 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
- Scrum is a framework for developing and sustaining complex products.
- Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment.
- Scrum implements self-management by replacing Project Managers with Scrum Masters.
- Each component of Scrum serves a specific purpose and is essential to Scrum's success and your usage of Scrum to develop complex products.
- Scrum is based on empiricism and lean thinking.
As the Sprint Planning progresses, the Developers realize that the workload may be greater than their capacity to complete the work. Which two are valid actions? (choose the best two answers)
- Recruit additional Developers before the work can begin.
- The Developers ensure that the Scrum Team is aware, start the Sprint, and monitor progress.
- The Developers work overtime during this Sprint.
- Cancel the Sprint.
- Remove or change selected Product Backlog Items.
True or False: The Product Owner makes sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders.
- True.
- False.
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 the best three answers)
- The Scrum Master loses the ability to update the Gantt Chart properly.
- Too much work is spent updating the Scrum board before the meeting.
- Opportunities to inspect and adapt the Sprint Backlog are lost.
- The Product Owner cannot accurately report progress to the stakeholders.
- Impediments are raised and resolved more slowly.
- The Sprint Backlog may become inaccurate.
True or 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, Developers to implement those ideas, and a Scrum Master to help guide the process.
- True.
- False.
- Make sure the release department understands these requirements, but it's not the Scrum Team's responsibility.
- Manage them during the Integration Sprint prior to the Release Sprint.
- Assign them to the Lead Developers on the team.
- Ensure every Increment meets them.
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? (choose the best two answers)
- Do not include the item in the Increment this Sprint.
- 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.
Who should make sure everyone on the Scrum Team does their tasks for the Sprint? (choose the best answer)
- The Project Manager.
- The Product Owner.
- The Scrum Master.
- The Scrum Team.
- All of the above.
To create focus which of the following are most important to have ready when Sprint Planning begins? (choose the best two answers)
- A fully refined Product Backlog.
- A clear cadence of when the Daily Scrum will take place.
- A Product Backlog with the most important items ready for discussion.
- Formal budget approval to conduct another Sprint.
- A Product Goal communicated by the Product Owner.
- A clear and non-negotiable Sprint Goal.
- True.
- False.
- It identifies undone work that can be addressed in a separate Sprint.
- It establishes the expected quality of the Increment reviewed at the Sprint Review.
- It creates transparency regarding progress within the Scrum Team.
- It helps the Product Owner track the open work during a Sprint.
When does a Developer become accountable for the value of a Product Backlog Item selected for the Sprint? (choose the best answer)
- Whenever a team member can accomodate more work.
- At the Sprint Planning Event.
- Never. The entire Scrum Team is accountable for creating value every Sprint.
- During the Daily Scrum.
True or False: A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place.
- True.
- False.
- Refining the top level Product Backlog Items until they are ready to be handed over to the Scrum Team.
- Describing an Increment at Sprint Planning and making sure that the Developers deliver it by the end of the Sprint.
- Writing the User Stories so they are comprehensive enough for the stakeholders.
- Maximizing the value of the product resulting from the work of the Scrum Team.
- High impact changes that have not been approved by the change request board.
- Decisions by the chief program manager.
- 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.
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.
- Skip Product Backlog Refinement activities.
- Change the Sprint Goal.
- Re-negotiate the selected Product Backlog Items with the Developers.
- Inform management that more resources are needed.
- Wait until the Product Owner is available again.
- Management should assign a substitue Product Owner to fill in where the Product Oner cannot be there.
- Ask the Product Owner's manager to decide in the Product Owner's absence.
- Within the Sprint, the Developers make the best decisions posssible to assure progress towards the Sprint Goal, re-aligning with the Product Owner once they are available again.
- They should work apart as much as posssible in order to keep the concerns of business and technology separated.
- They collaborate often so the Developers build Increments keeping end-user and stakeholder concerns in mind.
- They collaborate often so the Product Oner can make informed decisions in balancing effort and value of Product Backlog Items.
- They should share no more than the Sprint Planning and the Sprint Review meeting.
- The Product Owner should be with the Developers full-time to grow a deep understanding of the technology being used.
- To learn about the Scrum Team's productivity.
- To validate assumptions made when developing the product.
- To learn about the forecast of functionality that was developed.
- The Product Owner provides the stakeholders with acceptance forms at the Sprint Review to record their formal agreement over the delivered software.
- The Product Owner actively asks for stakeholder input and expectations to incorporate into the Product Backlog.
- The Product Owner has the final call over the requirements and should involve the stakeholders as little as possible.
- The Product Oner rites the Usser Storiess as provided by the stakeholders.
- Update the work plan for the Developers on a daily basis.
- Create financial reporting upon the spent hours reported by the Scrum Team.
- Work with the Developers on Product Backlog Refinement.
- Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items.
- Collaborate with stakeholders, user communities, and subject matter experts.
- They are not allowed. The Sprint Retrosspective is an opportunity for the Developerss to improve.
- They are optional. Attendance is only required when the Product Oner gets invited by the Scrum Master.
- Their attendance is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess and improve itself.
Adaptation requires regular inspection. In what ways does the Product Owner contribute to the results achieved by inspection?
- 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.
- The Product Owner verifies the Sprint Backlog for completeness at the end of Sprint Planning in order to allow the Sprint to start.
- The Product Owner inspects the Sprint burn-down at the Daily Scrum for progress towards a complete Increment and re-planning the team's work.
- The Product Owner shares the current state of Product Backlog at the Sprint Review, which, combined with the inspection of the Increment, leads to an updated Product Backlog.
- Chief Business Analyst.
- Requirements Collector.
- Project Manager 2.0.
- Scope Protector.
- Value Maximizer.
- The Scrum Master as they are responsible for the Scrum Team's productivity.
- The organization (or the Scrum Team if none is available from the organization).
- The Product Owner as 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.
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 accumulated cost over the earned value of the product.
- The money spent on development and delivery of the product.
- All investments required to conceive, develop, operate and maintain the product.
A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:
- The Quality Assurance department needs more time to make the previous Increment complete.
- The stakeholders are not happy with the value produced in the previous Sprint.
- There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint.
- The Product Owner has not identified a Sprint Goal.
- Not enough Product Backlog Items are ready.
- Devising a formula for a neutral calculation of value.
- Setting value on individual Product Backlog Items using Value Poker.
- The order of the Product Backlog.
- Validating assumptions of value through frequent releases.
- It is a detailed lists of functionalities from which the Developers draw items, to be complemented by a separate Technology Backlog managed by the Developers.
- 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 visible and clickable by anybody to enhance transparency.
- It is a formally approved list of requirements to be implemented over a set period.
- Technical debt does not influence the delivery of value.
- The velocity at which new functionality can be created is reduced when you have technical debt.
- Technical debt causes a greater percentage of the product's budget to be spent on maintenance of the product.
- Technical debt is not a Product Owner concern, technical debt is only an issue for the Developers.
- By the Product Owner and stakeholders accepting the Increment at the Sprint Review.
- By releasing frequently, and measuring the value customers/users experience.
- By measuring the actual time spent on development versus the time estimated for development.
- By measuring the velocity has increased since the last release.
- It is not required for the Product Owner to participate.
- To assign the Developers the daily tasks.
- To track the progress of the Project.
True or False: The Definition of Done increases the transparency and is used by the Developers to forecast how many items can be picked from the Product Backlog.
- True.
- False.
- True.
- False.
True or False: The Product Owner is the Scrum accountability (role = outdated term) responsible for engaging the product stakeholders.
- True.
- False.
- Plan the next Sprint.
- Discuss the way the Team has communicated in the last Sprint.
- Discuss the way the Development Team has collaborated with the Product Owner.
- Refine Product Backlog Items.
- There can be only one Product Owner.
- There can be only one Product Backlog.
- There can be 4 Product Owners.
- There can be 4 Product Backlogs.
- The Project Manager.
- The whole Scrum Team.
- The Scrum Master.
- The Product Owner.
- Hardening Sprints.
- Story Points.
- Time boxed events.
- Sprint Planning meetings.
- A Sprint 0.
- True.
- False.
- True.
- False.
- Ordering the items in the Product Backlog to best achieve goals and missions.
- Defining the Definition of Done.
- Defining the Definition of Ready.
- Product Backlog.
- Definition of Done.
- The Sprint Backlog.
- Creativity.
- Inspection.
- Adaption.
- Focus.
- It is moderated by the Product Owner.
- The Developers have to participate in the meeting.
- It is a time boxed event (15 min).
- It should be held at the same time and place.
- What can be delivered in the Increment resulting from the upcoming Sprint?
- Who will do which Sprint Backlog item?
- How will the work needed to deliver the Increment be achieved?
- True.
- False.
- The Project Manager takes care of non-functional requirements.
- Non-functional requirements can be added to the Product Backlog.
- Non-functional requirements are reflected in the Sprint Goal.
- Non-functional requirements can be added to the Definition of Done.
What should the Product Owner do when the Developers are ready to start the first Sprint, but the Product Backlog is not ready yet?
- The Product Owner should ask the Scrum Master to remove this impediment.
- The Product Owner should let the team start the Sprint and continue refining the Product Backlog.
- The Product Owner should not allow the team to Start the Sprint.
- True.
- False.
- As long as it is needed.
- A maximum of 40 hours per week.
- It is required to work at a constant pace.
- Between 40 and 60 hours per week.
- To be able to track the Sprint progress.
- It is not necessary for the Scrum Master to attend the meeting.
- To support the Product Owner.
- The Developers have asked the Scrum Master to facilitate the Daily Scrum.
- Support to have less technical debt.
- Support the Testers in the process.
- There are no QA's in Scrum.
- True.
- False.
- 3 to 10.
- 1 to 9.
- 3 to 9.
True or False: When n Scrum teams are working on a product, there should always be only 1 Product Owner but 1-n Scrum Masters.
- True.
- False.
- Supporting the Product Owner.
- Tracking the progress of a Release.
- There are no Project Managers in Scrum.
- Managing Risks.
- Work remaining across time.
- Business value delivered by the team.
- Budget remaining across time.
- The productivity will increase due to new ideas.
- The roles are clearly defined – nothing will happen.
- Often a short-term reduction in productivity can be seen.
- When the Product Owner declares it to be "Done".
- When the Development Team agrees that it is "Done".
- When it is potentially releasable.
How should the Developers react, when they realize that they have overcommitted themselves in a Sprint?
- They should collaborate with the Product Owner and decide together how to adjust the Sprint Backlog.
- They should ask the Scrum Master to cancel the Sprint.
- They should keep this information to themselves until the next Sprint Review.
- The Product Backlog contains only items that are completely refined.
- In the Product Backlog, Items at the top are usually smaller than on the bottom.
- The Product Backlog is never baselined.
- The Product Owner is accountable for the Product Backlog.
- If you have a high level of "technical debt", it could lead to false assumptions about the current state of the system.
- If you have "technical debt", no further features should be developed until the "technical debt" is fixed.
- It creates uncertainty, because when you add more and more features more and more problems will occur.
- It is the task of the Product Owner to take it into account during the release planning.
- Ask the Scrum Master to explain it to them.
- Don't touch the item until the Sprint Review to discuss it with the Product Owner again.
- Collaborate with the Product Owner immediately to receive a better understanding.
- Test Driven Development.
- Acceptance Tests.
- Unit Tests.
- All kind of test required to create a working Increment.
- The Developers are self-organized.
- The Development Team is not allowed to help the Product Owner managing the Product Backlog.
- The Development Team decides when to do the next release.
- The Development Team owns the Definition of Done.
Which Scrum accountability (role = outdated term) is responsible to do all the work required to turn Product Backlog in potentially releasable items?
- The Business Analyst.
- The Project Manager.
- The Development Team.
- The Stakeholders.
True or False: The Product Owner has to maximize the value – more features always bring more value. Therefore, the Product Owner has to maximize the number of features in a Sprint.
- True.
- False.
Yes or No: The Product Owner can ask a developer to order the Product Backlog Items instead of him/her – is that okay?
- Yes.
- No.
Which accountability (role = outdated term) in Scrum is responsible for explaining the items of the Product Backlog?
- The Developer.
- The Requirements Engineer.
- The Project Manager.
- The Scrum Master.
- The Product Owner.
- The Scrum Master should help the Product Owner to find techniques for managing the Product Backlog.
- The Scrum Master should help the Product Owner to do the documentation.
- The Scrum Master should remove impediments for the Scrum Team (incl. Product Owner).
- The Scrum Master should act as a "middleman" between the Product Owner and the Developers.
- True.
- False.
- Increase of predictability.
- Increase of respect.
- Increase of individual buy-in.
- Increase of creativity.
- When the Sprint Goal becomes obsolete.
- When the Developers are asking the Product Owner to do it.
- When the Business Analyst is asking the Product Owner to do it.
- When the Sprint Goal becomes obsolete and no items are "Done" yet.
If the Product Owner has concerns about the Definition of Done (DoD) – what should the Product Owner do?
- The Product Owner should discuss the Definition of Done with the Development Team.
- The Product Owner should change the Definition of Done.
- The Product Owner should ask the Scrum Master to change the Definition of Done.
- Using User Stories.
- Have a Product Owner.
- Answering the "three questions" in the Daily Scrums.
- Having time boxed Scrum Events.
- Have a Sprint Backlog.
- Using the concept of Story Points.
- The team should be able to collaborate with different departments.
- Each of the team members should be a developer, Tester and architect.
- The team has all the expertise (not each person) required to transform a Product Backlog Item in a potentially releasable Increment.
Which two of the following answers are not correct about the Product Owner accountability (role = outdated term)?
- The Product Owner decides which developer does what.
- The Product Owner has to participate in the Daily Scrum.
- The Product Owner measures the progress of a release.
- The Product Owner is responsible for maximizing the value.
- True.
- False.
- Improve the Definition of Done.
- Include external QA.
- Have hardening Sprints.
- True.
- False.
- The Sprint Review.
- The Sprint Planning.
- The Product Backlog Grooming.
- The Daily Scrum.
True or False: When n Scrum teams are working on a product, there are n Sprint Backlogs but only 1 Product Backlog.
- True.
- False.
- True.
- False.
- When the Sprint Goal is obsolete.
- When the Developers ask the Scrum Master to do so.
- The Scrum Master does not have the authority to do this.
- User Story "grooming".
- Nothing!
- Product Backlog Refinement.
True or False: When 3 products are developed using Scrum, there can be only a single Product Owner for all products.
- True.
- False.
- It is an old concept and overall not recommended.
- It helps the Product Owner to decide when the product is releasable.
- It gives an overall direction to all Sprints, makes it easier to prioritize Product Backlog Items and helps the team to stay focused.
Which statement describes best how the Product Backlog is impacted by changes in the product environment?
- The Product Backlog should always follow the Product Owners plan and should not reflect the changes at all.
- The Product Backlog should be very high level and therefore tolerate such changes.
- The Product Backlog should evolve and reflect the environment changes.
- Answering the questions of the Developers and Scrum Master.
- The Product Owner does not have the permission to attend the meeting.
- Participate as a Scrum Team member.
- Using User Stories.
- Having two Product Owners in a Scrum Team.
- A Sprint 0.
- A Release Sprint.
- Using Story Points.
True or False: When two Scrum Teams are working on the same product you should normalize their estimations to be able to compare their performance.
- True.
- False.
- The Product Backlog must only contain small, detailed and clearly described items.
- The Scrum Master is responsible for managing the Product Backlog.
- The Product Owner is responsible for managing the Product Backlog.
- True.
- False.
- Sprint Planning.
- Sprint Refinement.
- Sprint Review.
- Daily Scrum.
Which of the following answers is correct about the Product Owner accountability (role = outdated term)?
- The Product Owner is not part of the Scrum Team.
- The Product Owner creates all items in the Product Backlog on his own.
- The Product Owner is responsible to explain Product Backlog Items and to answer questions.
- It doesn't need to have detail.
- It has just enough detail.
- It has all the details.
- At least 15% of the time.
- As much as required.
- Min. 50% of the time.
True or False: Two Scrum Teams are working on the same product. Do they have to share the same Definition of Ready?
- True.
- False.
- Based on size.
- Based on value.
- Based on risk.
- The CEO.
- The higher management.
- The End-user.
True or False: It is not allowed that the Product Owner is a Developer (part of the "Developers") at the same time.
- True.
- False.
- The item is refined and small enough to fit in one Sprint.
- All stakeholder have agreed to prioritize it.
- The item is estimated (e.g. in Story Points).
- The item is smaller than 15 Story Points.
True or False: To be self-management means, that it is okay for the Developers to don't do the Daily Scrum.
- True.
- False.
The Product Owner is not available and cannot answer the developers questions before the Sprint Planning. Therefore, the developers feel a high level of uncertainty to make a reliable forecast. What should the team do?
- Extend the duration of the current Sprint and try to answer all questions.
- The Sprint Planning meeting should be cancelled or postponed.
- The upcoming Sprint should be cancelled.
- The developers should make a best guess and should not worry too much.
- Ask the Lead Developer to explain the IT architecture.
- Ask the Development Team to introduce themselves to each other and tell about their skills and background.
- Ensure, that all team members have a first ticket assigned to them.
- True.
- False.
- The team is clear on the next steps toward the Sprint Goal.
- The tasks are assigned to the developer.
- Impediments identified by the Scrum Master.
- A refined Daily Backlog.
- True.
- False.
- True.
- False.
Which statements describe best what happens in an organization if Scrum is introduced but the Scrum terminology is tailored to fit into the organizations environment?
- The change might be not obvious to everyone and therefore little change will happen.
- The organization will adapt the Scrum concepts faster due to the tailored approach.
- The management may feel less enthusiastic about the new approach.
- The change might not be obvious to every employee and some employees will not recognize it at all.
- The Scrum Master.
- The Project Manager.
- The Developers.
- The Product Owner.
- The Business Analyst.
The Developers have an internal conflict with one of the team members. What should the Product Owner do?
- Remove the Developer from the team?
- Ask the Scrum Master to remove the Developer from the Team?
- Let the team handle the conflict internally – they are self-organizing!
- It is a meeting for the inspection of the Increment and to collect feedback.
- It is a meeting to do the controlling and evaluation in regards to the developers work.
- It is a formal meeting to receive the approval for the work that was done.
True or False: In each Sprint Backlog at least one high priority process improvement items is existing.
- True.
- False.
True or False: The "Definition of Ready" shows the team when Product Backlog Items are ready to be selected for the Sprint Backlog.
- True.
- False.
- Having a Burn-Down-Chart.
- Having a Sprint Goal.
- Using Story Points.
- Having time boxed events.
- The Product Owner.
- The Project Lead.
- The Developers.
- The Scrum Master
How much time is needed between a Sprint Retrospective and the next Sprint Planning to prepare the Product Backlog?
- As much as defined by the Scrum Master.
- As much as it is needed.
- None.
- The whole process should be visible to everyone.
- The process should be visible to the key stakeholders.
- Significant aspect of the process must be visible to those responsible for the outcome.
- True.
- False.
- Respect.
- Focus.
- Inspection.
- Collaboration.
- Commitment.
- Maximize Value.
- Courage.
- Openness.
- True.
- False.
- True.
- False.
- The Product Owner.
- The Scrum Master
- The Development Team.
- Do Sprint Plannings.
- Do Daily Scrums.
- Have a Product Owner.
- Use Story Points.
- Use User Stories.
- True.
- False.
- Ideally budgeting is done every Sprint.
- Scrum doesn't need the team to care about budget.
- Budgeting is done based on the Product Backlog as a baseline.
The collaboration between the Developers and the Product Owner is very important for the product. Which of the following is the least productive way for the Scrum Master to improve this collaboration?
- The Scrum Master should act as a go-between for them.
- The Scrum Master should teach them techniques to improve it.
- The Scrum Master should suggest new collaboration tools.
- The Sprint Review.
- The Daily Scrum.
- The Sprint Retrospective.
- The Sprint Planning.
- True.
- False.
In the middle of the Sprint, the customer decides that there are two new features she wants. The Product Owner could: (choose the best two answers)
- Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal.
- Introduce these features at the next Daily Scrum.
- Have the Scrum Master add these features to the current Sprint.
- Add these features to the Product Backlog.
- Product Backlog ordering.
- When to release, based on its progress.
- Sprint Backlog.
- Stakeholders for the Sprint Review.
- Sprint length.
When the Developers determine that they will not be able to finish the complete forecast, who needs to be present when reviewing and adjusting the Sprint work selected? (choose the best answer)
- The Scrum Master and the Developers.
- The Product Owner and all stakeholders.
- The Product Owner and the Developers.
- The Scrum Master project manager and the Developers.
A Scrum Team is a cohesive unit of professionals that consists of which of the following? (choose all that apply)
- Developers.
- One Product Owner.
- Users.
- One Scrum Master.
- Customers.
- Sprint Retrospective.
- Developers must stand up at the Daily Scrum.
- Sprint Burndown Chart.
- Release Planning.
- All of the above.
A Scrum Master is working with a Scrum Team that has Developers in different physical locations. The Developers meet in a variety of meeting rooms and have much to do logistically (for example: reserve meeting rooms and set up conference calls) before the Daily Scrum. What action should the Scrum Master take? (choose the best answer)
- Set up the meeting and tell the Scrum Team that is how it will be done.
- Allow the Developers to self-manage and determine for themselves what to do.
- Inform management and ask them to solve it.
- Ask the Developers to alternate who is responsible for meeting setup.
- Developers on the Scrum Team work closely with business analysts, architects, developers, and testers who are not on the team.
- The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint.
- The Scrum Team is a virtual team drawing from separate teams of business analysts, architects, developers, and testers.
- The Scrum Team includes not only developers but also business analysts, architects, and testers.
- Clearly communicating project or release status and strategies to customers and stakeholders.
- Working with customers and stakeholders to identify the most valuable product requirements.
- Being with the Scrum Team all the time, just in case they need me to clarify a requirement.
- Writing clear, transparent User Stories.
When multiple Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint? (choose the best answer)
- Yes, but only for Scrum Teams whose work has dependencies.
- Yes, in order to accurately inspect what is done.
- No, that's far too hard and must be done in a hardening Sprint.
- No, each Scrum Team stands alone.
- Optimizing the value of the work the Scrum Team does.
- Keep stakeholders from distracting the Developers.
- Directing the Developers.
- Ensuring that the work meets the commitments to the stakeholders.
- Make up a plan for the rest of the project.
- Create at least one valuable, useful Increment.
- Build at least one piece of valuable functionality.
- Define the major product features and a release plan architecture.
- Analyze, describe, and document the requirements for the subsequent Sprints.
- Whenever it is done.
- Monthly.
- 4 hours for a one-month Sprint.
- 8 hours for a one-month Sprint.
- The Product Owner.
- The Scrum Team.
- The Developers.
- The Scrum Master.
Which of the following are appropriate topics for discussion during a Sprint Retrospective? (choose the best two answers)
- Documenting acceptance criteria for items in the next Sprint.
- The order of items in the Product Backlog.
- Identifying high priority process improvements for the next Sprint.
- How the team collaborates.
- Participating as a Scrum Team member.
- The Product Owner should not take part in Sprint Retrospective.
- Capturing requirements for the Product Backlog.
- Summarizing and reporting the discussions to the stakeholders that they represent in the Scrum Team.
