Pspo1-2 No Limit
-
What enhances the transparency of an Increment?
-
Keeping track of and estimating all undone work to be completed in a separate Sprint.
-
Updating Sprint tasks properly in the electronic tracking tool.
-
Reporting Sprint progress to the stakeholders daily.
-
Doing all work needed to meet the definition of “Done”.
-
Quiz Preview
- 2.
What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Development Teams?
-
Ask the Product Owner to assign the people to teams.
-
Ask the Developers to divide themselves into teams.
-
Create teams based on their skills across multiple layers (such as database, UI, etc.).
Correct Answer
A. Ask the Developers to divide themselves into teams.Explanation
The correct answer is to ask the Developers to divide themselves into teams. This approach empowers the team members to self-organize and allows them to utilize their knowledge and expertise in deciding how to divide the group. It promotes collaboration, ownership, and accountability within the Development Teams. Additionally, the Developers are more likely to have a better understanding of their own skills and capabilities, which can lead to more effective team compositions.Rate this question:
-
- 3.
Which does a self-organizing Development Team choose?
-
Stakeholders for the Sprint Review.
-
Product Backlog ordering.
-
When to release, based on its progress.
-
Sprint length.
-
How to best accomplish its work.
Correct Answer
A. How to best accomplish its work.Explanation
A self-organizing Development Team chooses "How to best accomplish its work" because self-organization empowers the team to make decisions and determine the most effective way to achieve their goals. This includes deciding on the best approach, techniques, and strategies to complete their tasks and deliver the desired outcomes. By allowing the team to make these choices, they can leverage their collective skills, expertise, and creativity to optimize their work process and increase their productivity and efficiency.Rate this question:
-
- 4.
True or False: Product Owners must specify complete acceptance criteria for a Product Backlog item before the team can select the item in Sprint Planning.
-
True
-
False
Correct Answer
A. FalseExplanation
False. While it is important for Product Owners to collaborate with the team and provide clear acceptance criteria for Product Backlog items, it is not necessary for the criteria to be fully specified before the team selects the item in Sprint Planning. The team can work with the Product Owner to refine and clarify the acceptance criteria during the Sprint Planning meeting itself. This allows for flexibility and adaptability in the development process.Rate this question:
-
- 5.
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?
-
Who are the subject matter experts on each team?
-
Who are going to be the team leads?
-
How will we make sure all teams have the right amount of expertise?
-
What is the right mixture of senior and junior people on each team?
Correct Answer
A. How will we make sure all teams have the right amount of expertise?Explanation
The suggested question of "How will we make sure all teams have the right amount of expertise?" is a good first question for the Scrum Master to suggest because it addresses the important aspect of ensuring that each team has the necessary skills and knowledge to successfully develop the product. By considering this question, the team can discuss and plan how to distribute expertise evenly across teams, ensuring a balanced allocation of subject matter experts and a suitable mixture of senior and junior members. This will contribute to the overall effectiveness and efficiency of the development process.Rate this question:
-
- 6.
Which statement best describes the Sprint Review?
-
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
-
It is a mechanism to control the Development Team’s activities during a Sprint.
-
It is used to congratulate the Development Team if it did what it forecast, or to punish the Development Team if it failed to meet its forecast.
-
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
Correct Answer
A. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.Explanation
The Sprint Review is a meeting where the Scrum Team and stakeholders come together to inspect the outcome of a Sprint. During this meeting, they review the work that has been completed and determine what to do next. It is an opportunity to gather feedback, discuss any changes or adjustments that need to be made, and plan for the next Sprint. This statement accurately describes the purpose and nature of the Sprint Review.Rate this question:
-
- 7.
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.
Correct Answer
A. Its productivity is likely to decrease.Explanation
When two additional Scrum Teams are added to the development of a product that previously had only one Scrum Team, the immediate impact on the productivity of the original Scrum Team is likely to decrease. This is because the addition of more teams can lead to increased complexity in coordination, communication, and collaboration. The original team may experience challenges in adjusting to the new dynamics, distributing work, and maintaining the same level of efficiency. It may take time for the teams to synchronize their efforts and establish effective ways of working together, which can initially impact the productivity of the original team.Rate this question:
-
- 8.
True or False: Scrum has a role called “Project Manager”.
-
True
-
False
Correct Answer
A. FalseExplanation
Scrum does not have a role called "Project Manager." In Scrum, the team is self-organizing and cross-functional, with no designated project manager. Instead, Scrum has three main roles: the Product Owner, who represents the stakeholders and prioritizes the product backlog; the Scrum Master, who facilitates the Scrum process and removes any obstacles that the team may encounter; and the Development Team, responsible for delivering the product increment. This structure promotes collaboration and empowers the team to make decisions collectively, rather than relying on a single project manager.Rate this question:
-
- 9.
Who determines how work is performed during the Sprint?
-
Subject matter experts.
-
Architects.
-
The Scrum Master.
-
Development Team managers.
-
The Development Team.
Correct Answer
A. The Development Team.Explanation
The Development Team determines how work is performed during the Sprint. In Scrum, the Development Team is responsible for self-organizing and deciding how to accomplish the tasks in the Sprint Backlog. They collaborate and make collective decisions on how to best achieve the Sprint Goal. This empowers the Development Team to take ownership and accountability for their work, fostering creativity and innovation. The Scrum Master, Architects, and Subject Matter Experts may provide guidance and support, but the ultimate responsibility lies with the Development Team. Development Team managers are not part of the Scrum framework and do not have authority over the Development Team's decisions.Rate this question:
-
- 10.
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.
Correct Answer
A. Any of the above (or others) which are a decomposition of the selected Product Backlog items.Explanation
The Sprint Backlog includes any of the above options or others that are a decomposition of the selected Product Backlog items. This means that the Sprint Backlog can include user stories, tasks, use cases, tests, or any other items that break down the selected Product Backlog items into smaller, manageable units of work for the sprint. The specific items included in the Sprint Backlog will depend on the needs and requirements of the project.Rate this question:
-
- 11.
The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take?
-
Present the Product Owner with an ordered Product Backlog to use.
-
Suggest the product Owner extend the Sprint, so he can have more time to order the Product Backlog.
-
Suggest that the Development Team does the ordering 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 Development Team to see which items technically are fastest to implement.
Correct Answer
A. Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.Explanation
The appropriate action for the Scrum Master is to offer help to the Product Owner in understanding that the goal of ordering the Product Backlog is to maximize value. This action aligns with the Scrum Master's role in facilitating the Scrum process and supporting the Product Owner. By offering assistance, the Scrum Master can provide guidance and insights to the Product Owner on how to prioritize and order the backlog items based on their value to the stakeholders. This will help the Product Owner make informed decisions and ensure that the most valuable items are delivered early in the project.Rate this question:
-
- 12.
User documentation is part of your definition of “Done”. However, there aren’t enough technical writers for all teams. Your Development Team doesn’t have a technical writer. What should you do?
-
Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it.
-
Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
-
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.
-
Wait until you have a technical writer on your Development Team to take care of this.
Correct Answer
A. Your Development Team is still responsible for creating user documentation. In this case, the Development Team members will write it. -
- 13.
Which of the following best describes an increment of working software?
-
A decomposition of all Product Backlog items into tasks for future Sprint Backlog lists.
-
An automated test suite to verify functionality delivered in previous iterations.
-
Additional features in a usable state that complement those delivered in previous iterations.
-
A new user interface design for functionality delivered in previous iterations.
-
UML diagrams that describe how to deliver functionality in future iterations.
Correct Answer
A. Additional features in a usable state that complement those delivered in previous iterations. -
- 14.
When does the next Sprint begin?
-
Immediately after the conclusion of the previous Sprint.
-
When the Product Owner is ready.
-
Immediately following the next Sprint Planning.
-
The Monday following the Sprint Review.
Correct Answer
A. Immediately after the conclusion of the previous Sprint.Explanation
The correct answer is "Immediately after the conclusion of the previous Sprint." This is because in Scrum, a Sprint is a time-boxed iteration during which a potentially shippable product increment is created. Once a Sprint is completed, the next Sprint begins immediately after without any delay. This ensures a continuous flow of work and allows for regular feedback and adaptation.Rate this question:
-
- 15.
When should a Sprint Goal be created?
-
It must be established before Sprint Planning in order to begin planning.
-
A Sprint Goal is not mandatory in Scrum.
-
It should have been created in the previous Sprint during Product Backlog refinement.
-
During Sprint Planning.
-
At any time during the Sprint.
Correct Answer
A. During Sprint Planning.Explanation
A Sprint Goal should be created during Sprint Planning. During this meeting, the Scrum Team collaborates to discuss and select the Product Backlog items that will be worked on during the Sprint. The Sprint Goal provides a clear objective and focus for the team to work towards during the Sprint. It helps align the team's efforts and ensures that they are working towards a common purpose. By creating the Sprint Goal during Sprint Planning, the team can effectively plan and prioritize their work for the upcoming Sprint.Rate this question:
-
- 16.
As the Development Team starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do?
-
Inform the Product Owner at the Sprint Review, but prior to the demonstration.
-
Find another Scrum Team to give the excess work to.
-
As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
-
Reduce the definition of “Done” and get all of the Product Backlog items “Done” by new definition.
Correct Answer
A. As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.Explanation
The correct answer is to work with the Product Owner to remove some work or Product Backlog items as soon as possible in the Sprint. This is because the Development Team has realized that they have selected too much work to finish in the Sprint. By working with the Product Owner, they can prioritize and remove some items from the Sprint backlog to ensure that the team can complete the remaining work within the Sprint timeframe. This allows for a realistic and achievable goal for the team.Rate this question:
-
- 17.
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.
Correct Answer
A. Sprint Retrospective.Explanation
The Sprint Retrospective is required by Scrum. It is a meeting held at the end of each sprint where the Scrum Team reflects on their performance and identifies areas for improvement. The purpose of this meeting is to learn from past experiences and make adjustments to enhance future sprints. Stand-up meetings, Sprint Burndown Charts, and Release Planning are also important components of Scrum, but they are not explicitly required.Rate this question:
-
- 18.
Why does the Product Owner want the Development Team to adhere to its definition of “Done”?
-
To be able to reprimand the team when they don’t need their velocity goal for the Sprint.
-
To know what the team will deliver over the next three Sprints.
-
To have complete transparency into what has been done at the end of each Sprint.
-
To predict the team’s productivity over time.
Correct Answer
A. To have complete transparency into what has been done at the end of each Sprint.Explanation
The Product Owner wants the Development Team to adhere to its definition of "Done" in order to have complete transparency into what has been done at the end of each Sprint. By ensuring that the team meets the agreed-upon criteria for "Done," the Product Owner can accurately assess the progress and outcomes of each Sprint. This transparency allows the Product Owner to make informed decisions, provide feedback, and effectively communicate the team's accomplishments to stakeholders.Rate this question:
-
- 19.
How much work must a Development Team do to a Product Backlog item it selects for a Sprint?
-
All development work and at least some testing.
-
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.
-
A proportional amount of time on analysis, design, programming, testing, and documentation.
-
As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
Correct Answer
A. As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.Explanation
The correct answer is "As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of 'Done'." This means that the Development Team must complete all the work that they have committed to the Product Owner for each selected Product Backlog item. This ensures that the work is done according to the agreed-upon criteria of "Done" for that item.Rate this question:
-
- 20.
There are multiple teams working on one product. True or False: Each Development Team should have a separate Product Owner.
-
True
-
False
Correct Answer
A. FalseExplanation
False. Each Development Team does not need to have a separate Product Owner. According to the Scrum framework, there is only one Product Owner who is responsible for managing the Product Backlog and prioritizing the work for the entire Scrum Team. The Development Team collaborates with the Product Owner to understand the requirements and deliver a valuable product. Having multiple Product Owners for each team could lead to conflicting priorities and hinder the efficiency of the development process.Rate this question:
-
- 21.
How often should customer satisfaction be measured?
-
Annually.
-
Daily.
-
Quarterly.
-
Frequently.
Correct Answer
A. Frequently.Explanation
Customer satisfaction should be measured frequently in order to gather accurate and up-to-date feedback on customer experiences. By measuring customer satisfaction frequently, businesses can identify any issues or concerns quickly and make necessary improvements to enhance the overall customer experience. Regular measurement also allows for tracking trends and changes in customer satisfaction over time, enabling businesses to make informed decisions and adjustments to their products, services, or processes.Rate this question:
-
- 22.
Which of the following might the Scrum Team discuss during a Sprint Retrospective?
-
A) Methods of communication.
-
B) The way the Scrum Team does Sprint Planning.
-
C) Skills needed to improve the Development Team’s ability to deliver.
-
D) Its Definition of “done”.
-
E) All of the above.
Correct Answer
A. E) All of the above.Explanation
During a Sprint Retrospective, the Scrum Team discusses various aspects to improve their performance. This includes methods of communication to enhance collaboration and efficiency within the team. They also discuss the way they conduct Sprint Planning to identify any areas for improvement. Additionally, the team addresses the skills needed to enhance the Development Team's ability to deliver high-quality work. Lastly, they review and refine their Definition of "done" to ensure a shared understanding of what constitutes a completed increment. Therefore, all of the options mentioned (A, B, C, and D) are valid topics for discussion during a Sprint Retrospective.Rate this question:
-
- 23.
The IT manager asks a Development Team for a status report describing the progress throughout the Sprint. The Development Team asks the Scrum Master for advice. The Scrum Master should:
-
Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.
-
Ask the Product Owner to send the manager the report.
-
Tell the Development Team to figure it out themselves.
-
Create and deliver the report to the manager herself.
-
Tell the Development Team to fit the report into the Sprint Backlog.
Correct Answer
A. Talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review.Explanation
The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because in Scrum, the progress is measured by inspecting the Increment during the Sprint Review, where the Development Team demonstrates the work done. The Scrum Master is responsible for guiding and educating the team and stakeholders about Scrum principles and practices, and in this case, it is important to clarify the appropriate way to measure progress in Scrum.Rate this question:
-
- 24.
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?
-
Update the project plan with stakeholders.
-
Work with the QA departments on the Increment of the current Sprint.
-
There are no such activities. The next Sprint starts immediately after the current Sprint.
-
Refine the Product Backlog.
Correct Answer
A. There are no such activities. The next Sprint starts immediately after the current Sprint.Explanation
The correct answer is that there are no such activities. The next Sprint starts immediately after the current Sprint. This means that there is no specific phase or time allocated for the Product Owner to undertake any activities between the end of the current Sprint and the start of the next Sprint. The transition from one Sprint to another is seamless and continuous. Therefore, the Product Owner does not have any specific tasks or responsibilities during this phase.Rate this question:
-
- 25.
Who creates a Product Backlog Item’s estimate?
-
The Development Team, alone.
-
The Product Owner with input from the Development Team.
-
The most senior people in the organization, including architects and subject matter experts.
-
The Scrum Master.
-
The Development Team after clarifying requirements with the Product Owner.
Correct Answer
A. The Development Team after clarifying requirements with the Product Owner.Explanation
The Development Team creates a Product Backlog Item's estimate after clarifying requirements with the Product Owner. This is because the Development Team is responsible for understanding the work that needs to be done and estimating the effort required to complete it. The Product Owner provides the necessary information and requirements, and the Development Team uses their expertise to estimate the time and effort needed for each item in the Product Backlog. This collaborative approach ensures that the estimates are accurate and realistic.Rate this question:
-
- 26.
What might indicate to a Product Owner that she needs to work more with the Scrum Team?
-
The Increment presented at the Sprint Review does not reflect what she thought she had asked for.
-
She isn’t working full time with the Scrum team.
-
Developers leave the Team.
-
The acceptance tests don’t appear to be complete.
Correct Answer
A. The Increment presented at the Sprint Review does not reflect what she thought she had asked for.Explanation
If the Increment presented at the Sprint Review does not reflect what the Product Owner thought she had asked for, it indicates that she needs to work more with the Scrum Team. This suggests that there may be a lack of clear communication and understanding between the Product Owner and the Scrum Team. By working more closely with the team, the Product Owner can ensure that her requirements and expectations are properly conveyed, leading to a more accurate and satisfactory Increment at the Sprint Review.Rate this question:
-
- 27.
How is management external to the Scrum Team involved in the Daily Scrum?
-
Management gives an update at the start of each Daily Scrum.
-
The Product Owner represents their opinions.
-
The Scrum Master speaks on their behalf.
-
The Development Team self-manages and is the only management required at the Daily Scrum.
Correct Answer
A. The Development Team self-manages and is the only management required at the Daily Scrum.Explanation
In Scrum, the Daily Scrum is a meeting for the Development Team to synchronize their work and plan the next 24 hours. It is not intended for management to give updates or represent their opinions. The purpose of the Daily Scrum is for the Development Team to inspect and adapt their progress towards the Sprint Goal. Therefore, management external to the Scrum Team is not involved in the Daily Scrum, and the Development Team self-manages during this meeting.Rate this question:
-
- 28.
When might a Sprint be abnormally cancelled?
-
When it becomes clear that not everything will be finished by the end of the Sprint.
-
When the Sprint Goal becomes obsolete.
-
When the sales department has an important new opportunity.
-
When the Development Team feels that the work is too hard.
Correct Answer
A. When the Sprint Goal becomes obsolete.Explanation
A Sprint may be abnormally cancelled when the Sprint Goal becomes obsolete. The Sprint Goal is a crucial aspect of Scrum, as it provides a clear objective for the Development Team to work towards during the Sprint. If the Sprint Goal is no longer relevant or achievable, it may be necessary to cancel the Sprint to prevent wasting time and resources on work that will not contribute to the overall project goals. This decision should be made by the Product Owner in consultation with the Development Team and other stakeholders.Rate this question:
-
- 29.
True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.
-
True
-
False
Correct Answer
A. FalseExplanation
A Product Owner with multiple teams working on one product should not maintain separate Product Backlogs for each team. Instead, they should maintain a single Product Backlog that encompasses all the work for the entire product. This allows for a holistic view of the product and ensures that all teams are aligned and working towards a common goal. It also helps in prioritizing and sequencing the work across teams, making sure that the most valuable features are delivered first.Rate this question:
-
- 30.
True or False: Sprint Reviews are an opportune time to collect customer feedback.
-
True
-
False
Correct Answer
A. TrueExplanation
Sprint Reviews are indeed an opportune time to collect customer feedback. During these reviews, the development team presents the work completed during the sprint to stakeholders, including customers. This provides an opportunity for customers to provide feedback, ask questions, and suggest improvements. By actively involving customers in the review process, the team can gather valuable insights that can be used to refine and enhance the product.Rate this question:
-
- 31.
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, a Development Team to implement those ideas and a Scrum Master to help guide the process.
-
True
-
False
Correct Answer
A. TrueExplanation
Scrum is an agile framework that emphasizes collaboration and adaptability in software development. It suggests that to get started, all that is required is a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas, and a Scrum Master to guide the process. This means that Scrum does not require any additional roles or complex processes to begin building a product. Therefore, the statement "True" is the correct answer.Rate this question:
-
- 32.
Why is the Daily Scrum held at the same time and same place?
-
The Product Owner demands it.
-
Rooms are hard to book and this lets it be booked in advance.
-
The place can be named.
-
The consistency reduces complexity.
Correct Answer
A. The consistency reduces complexity.Explanation
The Daily Scrum is held at the same time and same place to reduce complexity. By having a consistent time and place for the meeting, team members can easily plan their schedules and ensure they are available. It also helps to establish a routine and create a sense of structure within the team. This consistency allows the team to focus on the important discussions and updates during the Daily Scrum, rather than spending time and energy on figuring out when and where the meeting will take place.Rate this question:
-
- 33.
Who can abnormally terminate a Sprint?
-
The Stakeholders.
-
The Development Team or its members.
-
The Scrum Master.
-
The Product Owner.
Correct Answer
A. The Product Owner.Explanation
The Product Owner can abnormally terminate a Sprint because they have the authority to make decisions regarding the product backlog and prioritize the work. If the Product Owner determines that the Sprint goal is no longer achievable or that the project priorities have changed significantly, they can decide to terminate the Sprint. This decision is based on their understanding of the product and its requirements, and it is their responsibility to ensure that the team is working on the most valuable and relevant tasks.Rate this question:
-
- 34.
When is the Sprint Backlog created?
-
During the Sprint Planning meeting.
-
During the Sprint.
-
Prior to the Sprint Planning meeting.
-
At the beginning of the project.
Correct Answer
A. During the Sprint Planning meeting.Explanation
The Sprint Backlog is created during the Sprint Planning meeting. This meeting is held at the beginning of each sprint, where the Scrum Team collaboratively decides which items from the Product Backlog will be included in the upcoming sprint. The team then breaks down these selected items into smaller tasks and adds them to the Sprint Backlog. This backlog serves as a plan for the work that needs to be completed during the sprint and helps the team track their progress towards achieving the sprint goal.Rate this question:
-
- 35.
True or False: Scrum is a methodology that tells in detail how to build software incrementally.
-
True
-
False
Correct Answer
A. FalseExplanation
Scrum is not a methodology that provides detailed instructions on how to build software incrementally. Instead, it is an agile framework that focuses on collaboration, flexibility, and iterative development. Scrum provides a set of guidelines and principles that teams can adapt to their specific needs and context. It encourages self-organization and empowers teams to make decisions on how to best build software incrementally, rather than prescribing a specific methodology or process.Rate this question:
-
- 36.
Who should make sure everyone on the Development Team does his or her tasks for the Sprint?
-
A) The Project Manager.
-
B) The Product Owner.
-
C) The Scrum Master.
-
D) The Development Team.
-
E) All of the above.
Correct Answer
A. D) The Development Team.Explanation
The Development Team should make sure that everyone on the team completes their tasks for the Sprint. This responsibility lies within the team itself, as they are self-organizing and cross-functional. The Development Team collaboratively plans and manages their work, ensuring that all tasks are completed within the Sprint. The Project Manager, Product Owner, and Scrum Master may provide support and guidance, but it is ultimately the responsibility of the Development Team to ensure that all tasks are completed.Rate this question:
-
- 37.
What is the recommended size for a Development Team?
-
At least 7.
-
3 to 9.
-
7 plus or minus 3.
-
9.
Correct Answer
A. 3 to 9.Explanation
The recommended size for a Development Team is 3 to 9. This range allows for effective collaboration and communication within the team. With fewer than 3 members, there may not be enough diversity of skills and perspectives. On the other hand, having more than 9 members can lead to coordination challenges and decreased productivity. Therefore, a Development Team of 3 to 9 members is considered optimal for efficient and successful project development.Rate this question:
-
- 38.
Which statement best describes the Sprint Backlog as outcome of the Sprint Planning?
-
Every item has a designated owner.
-
It is a complete list of all work to be done in a Sprint.
-
Each task is estimated in hours.
-
It is the Development Team’s plan for the Sprint.
-
It is ordered by the Product Owner.
Correct Answer
A. It is the Development Team’s plan for the Sprint.Explanation
The Sprint Backlog is the Development Team's plan for the Sprint. It is a dynamic list of all the work that the Development Team identifies as necessary to meet the Sprint Goal. It is created during the Sprint Planning meeting and is owned by the Development Team. The Sprint Backlog is not a complete list of all the work to be done in the Sprint, as it can be updated and adjusted throughout the Sprint as new information emerges or priorities change. It is not ordered by the Product Owner, as the Development Team is responsible for organizing and managing the Sprint Backlog. Each task in the Sprint Backlog may be estimated in hours, but this is not the main purpose or requirement of the Sprint Backlog.Rate this question:
-
- 39.
Which topics should be discussed in the Sprint Review?
-
The Scrum process, and how it was used during the Sprint.
-
Coding and engineering practices.
-
Sprint results.
-
All of the above
Correct Answer
A. Sprint results.Explanation
The Sprint Review is a crucial event in Scrum where the development team presents the increment they have built during the sprint to the stakeholders. It provides an opportunity to inspect the product increment and gather feedback from stakeholders. The discussion in the Sprint Review should primarily focus on the sprint results, which include the completed user stories, any unfinished work, and the overall progress towards the project goal. While the Scrum process and coding/engineering practices are important, they are not the main topics to be discussed in the Sprint Review.Rate this question:
-
- 40.
Who is responsible for tracking the remaining work of the Sprint?
-
The Product Owner.
-
The Scrum Master.
-
The Project Manager.
-
The Development Team.
-
The Development Team in consultation with the Product Owner.
Correct Answer
A. The Development Team.Explanation
The Development Team is responsible for tracking the remaining work of the Sprint. They are self-organizing and cross-functional, meaning they have the skills and expertise to estimate and track their own work. The Development Team collaborates with the Product Owner to understand the requirements and priorities, but ultimately, it is their responsibility to track and manage the remaining work to ensure the Sprint goal is achieved. The Scrum Master is responsible for facilitating the Scrum process and removing any impediments, while the Project Manager is not a role in Scrum methodology.Rate this question:
-
- 41.
What is the purpose of a Sprint Review?
-
To take time to judge the validity of the project.
-
To inspect the product Increment with the stakeholders and collect feedback on next steps.
-
To review the Scrum Team’s activities and processes during the Sprint.
-
To build team spirit.
Correct Answer
A. To inspect the product Increment with the stakeholders and collect feedback on next steps.Explanation
The purpose of a Sprint Review is to inspect the product Increment with the stakeholders and collect feedback on next steps. This allows the Scrum Team to gather valuable input from stakeholders, assess the progress of the project, and determine the next course of action. It helps ensure that the product is meeting the needs and expectations of the stakeholders and allows for adjustments and improvements to be made in subsequent sprints.Rate this question:
-
- 42.
The Development Team should have all the skills needed to:
-
Turn Product Backlog items into an Increment of potentially releasable product functionality.
-
Complete the project within the date and cost as calculated by the Product Owner.
-
Do all of the development work, expect for specialized testing that requires additional tools and environments.
Correct Answer
A. Turn Product Backlog items into an Increment of potentially releasable product functionality.Explanation
The correct answer is "Turn Product Backlog items into an Increment of potentially releasable product functionality." This answer aligns with the principle of self-organization in Scrum. The Development Team is responsible for delivering a potentially releasable Increment at the end of each Sprint. They should have all the necessary skills to take the items from the Product Backlog and transform them into a working product functionality. The answer also dismisses the idea of completing the project within a specific date and cost, as these are determined by the Product Owner, not the Development Team. Additionally, it states that the Development Team is responsible for all development work, except for specialized testing that may require additional tools and environments.Rate this question:
-
- 43.
True or False: The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.
-
True
-
False
Correct Answer
A. TrueExplanation
The Sprint Goal is indeed a result of Sprint Planning, along with the Sprint Backlog. During Sprint Planning, the Scrum Team collaboratively defines the Sprint Goal, which is a concise statement that describes the objective of the Sprint. The Sprint Backlog, on the other hand, is a list of items selected from the Product Backlog that the Scrum Team plans to work on during the Sprint to achieve the Sprint Goal. Therefore, both the Sprint Goal and the Sprint Backlog are outcomes of the Sprint Planning process.Rate this question:
-
- 44.
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 Development Team 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.
Correct Answer
A. He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.Explanation
The main reason for the Scrum Master to be at the Daily Scrum is to ensure that the Development Team has a Daily Scrum. The Scrum Master's role is to facilitate and support the Scrum process, and one of their responsibilities is to ensure that the team is following the Scrum framework correctly. By being present at the Daily Scrum, the Scrum Master can ensure that the team is conducting the meeting and following the guidelines of Scrum. This helps to maintain the integrity of the Scrum process and ensures that the team is working effectively and efficiently.Rate this question:
-
- 45.
Which of the following criteria to order Product Backlog items?
-
Value of Product Backlog items.
-
Dependencies between Product Backlog items.
-
Dependencies to other products.
-
The availability of the Scrum Master.
-
All of the above.
Correct Answer(s)
A. Value of Product Backlog items.
A. Dependencies between Product Backlog items.
A. Dependencies to other products.Explanation
The Product Backlog is a prioritized list of all the desired features, enhancements, and fixes for a product. The criteria for ordering Product Backlog items include the value of the items, dependencies between the items, and dependencies to other products. The value of an item determines its importance and impact on the product. Dependencies between items indicate that certain items need to be completed before others can be started. Dependencies to other products imply that certain items are dependent on the completion of work in other products. Considering all of these criteria ensures that the Product Backlog is ordered in a way that maximizes value and efficiency.Rate this question:
-
- 46.
Who is on the Scrum Team?
-
Scrum Master.
-
Product Owner.
-
Development Team member.
-
Project Manager.
-
None of the above.
Correct Answer(s)
A. Scrum Master.
A. Product Owner.
A. Development Team member.Explanation
The Scrum Team consists of the Scrum Master, who is responsible for facilitating the Scrum process and ensuring that the team adheres to the Scrum principles and practices. The Product Owner, who represents the stakeholders and is responsible for managing the product backlog and prioritizing the work. And the Development Team members, who are responsible for delivering potentially releasable increments of the product at the end of each sprint. The Project Manager is not a part of the Scrum Team as Scrum promotes self-organization and does not have a traditional project manager role.Rate this question:
-
- 47.
Which are NOT appropriate topics for discussion in a Sprint Retrospective? Choose the best two answers
-
The value of work currently represented in the Product Backlog.
-
Arranging the Sprint Backlog for the next Sprint.
-
How the team does its work.
-
Definition of “Done”.
-
Team relations.
Correct Answer(s)
A. The value of work currently represented in the Product Backlog.
A. Arranging the Sprint Backlog for the next Sprint.Explanation
The value of work currently represented in the Product Backlog and arranging the Sprint Backlog for the next Sprint are not appropriate topics for discussion in a Sprint Retrospective. The Sprint Retrospective is a time for the team to reflect on their performance and identify areas for improvement. It is not the appropriate forum to discuss the Product Backlog or the planning for the next Sprint. Instead, the team should focus on discussing how they work together, their definition of "Done," and any team relations issues that may be hindering their progress.Rate this question:
-
- 48.
What are two good ways for the Development Team to make non-functional requirements visible? Choose the best two answers
-
Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
-
Add them to the definition of “Done” so the work is taken care of every Sprint.
-
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.
-
Put them on a separate list on the Scrum board, available for all to see.
Correct Answer(s)
A. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
A. Add them to the definition of “Done” so the work is taken care of every Sprint.Explanation
One good way for the Development Team to make non-functional requirements visible is by adding them to the Product Backlog and keeping the Product Owner posted on the expected effort. This ensures that the non-functional requirements are included in the overall prioritization and planning of the project. Another good way is to add them to the definition of "Done" so that the work related to non-functional requirements is taken care of in every Sprint. This ensures that the non-functional requirements are considered as part of the team's commitment for each Sprint and are not overlooked.Rate this question:
-
- 49.
Which three of the following are feedback loops in Scrum? Choose the best three answers
-
Sprint Review.
-
Release Planning.
-
Daily Scrum.
-
Sprint Retrospective.
-
Refinement Meeting
Correct Answer(s)
A. Sprint Review.
A. Daily Scrum.
A. Sprint Retrospective.Explanation
The three feedback loops in Scrum are Sprint Review, Daily Scrum, and Sprint Retrospective. The Sprint Review provides feedback on the product increment, allowing stakeholders to inspect and adapt the product. The Daily Scrum is a daily meeting where the team inspects progress and adjusts the plan for the day. The Sprint Retrospective is a meeting at the end of each sprint where the team reflects on their processes and identifies areas for improvement. These three feedback loops are essential in Scrum to continuously improve the product and the team's performance.Rate this question:
-
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
-
Current Version
-
Mar 22, 2023Quiz Edited by
ProProfs Editorial Team -
May 30, 2020Quiz Created by
AB
Back to top