1. Question 1
2. Question 2
3. Question 3
4. Question 4
5. Question 5
6. Question 6
7. Question 7
8. Question 8
9. Question 9
10. Question 10
11. Question 11
12. Question 12
13. Question 13
14. Question 14
15. Question 15

1. 8 Points

What is the most likely role for each team member based on the description for a Scrum project.

1. Prompts

1. Answers

1. Question 16

1. 1

Kai: Responsible for the product's vision and ensuring the team delivers value to the business

Select match

1. Question 16

1. 2

Izzy: Provides regular market and competitive analysis to the team.

Select match

1. Question 16

1. 3

Dana: Works on coding, testing, and designing the product

Select match

1. Question 16

1. 4

Bailey: Represents the client's interests and prioritizes the Product Backlog

Select match

1. Question 16

1. 5

Alex: Facilitates Scrum ceremonies and removes impediments for the team.

Select match

1. Question 16

1. 6

Gabi: Pays invoices on software

Select match

1. Question 16

1. 7

Jim: Provides demo of user stories during the Sprint review

Select match

1. Question 16

1. 8

Jordan: Ensures the team adheres to Agile principles and Scrum practices.

Select match

1. 1 Point

What action is planned for the next Sprint regarding the search functionality?

Removing the search functionality

Adding filters for price range and user ratings

Integrating a third-party search service

Decreasing search speed for better accuracy.

1. 1 Point

The team faced major delays due to issues with the payment gateway integration.

1. True

1. False

1. 1 Point

Which user story was not completed during the Sprint?

User account creation

Search for restaurants by cuisine type

View a restaurant's menu

None of the above

1. Sprint Review.pdf

Use the following Sprint review notes to answer the following questions.

1. 1 Point

How does Scrum's emphasis on flexibility and change sometimes negatively impact project predictability?

By limiting stakeholder input to only the Sprint reviews.

By requiring detailed upfront planning, which often needs to be revised.

By discouraging changes to the project scope once it has begun.

By making it difficult to commit to long-term project timelines and budgets.

1. 1 Point

A critique of Scrum concerning organizational culture is that:

Scrum can easily adapt to any organizational culture, making it universally applicable.

Scrum discourages traditional project management roles, leading to resistance from management.

The high level of transparency and openness required by Scrum can be difficult to achieve in hierarchical or traditional organizations.

All of the above

1. 1 Point

A Scrum team has a Sprint burndown chart showing that halfway through the Sprint, the amount of work remaining is significantly above the ideal line. What does this indicate, and what action should be taken?

It indicates the team is ahead of schedule. No action is necessary.

It indicates that too much work was completed too soon, and the team should slow down.

It suggests the team may not f all work by the end of the Sprint. The team should assess whether to descope or increase effort.

No impact because you can't tell until the end of the sprint

1. 1 Point

A project's burndown chart shows that the team has consistently been completing more points than planned each day. What might this indicate?

The team is overestimating the complexity of tasks.

The team is underperforming and needs to work overtime

The team is not following the Scrum methodology properly.

All of the above

1. 1 Point

Which phase of a project under Water-Scrum-Fall methodology would likely follow a more traditional Waterfall approach?

Daily stand-ups and sprint retrospectives

The development and testing phases within each sprint.

Initial requirements gathering and final project deliverables.

The prioritization of the product backlog.

1. 1 Point

A team consistently fails to meet the Sprint Goal due to technical challenges. What should the Sprint Retrospective focus on?

Identifying ways to improve technical skills within the team.

Reevaluating the feasibility of the Sprint Goals

Allocating blame to team members for failures.

Reducing the scope of future Sprints.

1. 1 Point

The Product Owner is pressured to add more features than the team can handle. What should the Scrum Master do?

Insist that the team work overtime to meet the demand.

Allow the Product Owner to make the decision

Facilitate a discussion between the Product Owner and stakeholders about the team's capacity.

Suggest dropping less important work to accommodate new features.

1. 1 Point

What strategy should the team employ for a highly complex and uncertain Product Backlog item?

Break the item into smaller, more manageable pieces.

Postpone the item until the team has more information.

Increase the estimation to account for complexity and uncertainty.

Assign the item to the most experienced team member.

1. 1 Point

As an organization transitions from Waterfall to Scrum, how does the role of the Product Owner evolve?

The Product Owner becomes less involved with the team.

The Product Owner's involvement with stakeholders decreases.

The Product Owner takes on more responsibilities for project documentation.

The Product Owner plays a key role in stakeholder engagement and product vision.

1. 5 Points

Match the Scrum terms

1. Prompts

1. Answers

1. Question 2

1. 1

Accountable for maximizing the value of the product resulting from the work of the Scrum Team.

Select match

1. Question 2

1. 2

Facilitates Scrum events and ensures the Scrum Team adheres to Scrum theory, practices, and rules.

Select match

1. Question 2

1. 3

A list of everything that needs to be done within the project

Select match

1. Question 2

1. 4

To inspect the sprint and adapt the Product Backlog if needed with stakeholders

Select match

1. Question 2

1. 5

visual tool used in project management to track the progress of work completed against the total work planned over time.

Select match

1. 10 Points

Match the statement with the most appropriate methodology

1. Prompts

1. Answers

1. Question 1

1. 1

Projects benefit from teams that bring together a variety of skills to address complex challenges

Scrum

1. Question 1

1. 2

Periodic reviews with stakeholders are important for gathering feedback and adjusting project direction.

Scrum

1. Question 1

1. 3

Project teams often work in specialized functions

Waterfall

1. Question 1

1. 4

The approach is well-suited for projects with clear objectives and stable requirements

Waterfall

1. Question 1

1. 5

Each phase has specific deliverables and a review process to ensure completeness before moving to the next phase

Waterfall

1. Question 1

1. 6

Regular team meetings are crucial for aligning on project progress

Scrum

1. Question 1

1. 7

Reflecting on project processes and outcomes helps teams improve their approach

Scrum

1. Question 1

1. 8

Documentation is emphasized throughout the project

Waterfall

1. Question 1

1. 9

The project's success is measured by its ability to deliver increments of value in a short timeframe, fostering continuous collaboration and feedback loops with stakeholders.

Scrum

1. Question 1

1. 10

ef

Testing is performed after the build stage is fully completed and before deployment, ensuring that all parts of the application work together as expected.

Waterfall