Sample 2 – Indemia

PMP Quiz

1 / 5

31. Members of an Agile development group are in discussions about integrating Kanban's continuous flow approach into their project processes. One member of the group expresses skepticism, suggesting that Kanban may not fully conform to established Agile tenets, and outlines several points of contention regarding the application of Kanban in their business setting. What is NOT accurately applicable to Kanban?

A. The sprint-focused workflow of Kanban generally corresponds with the principles of the Scrum Framework

B. The Work in Progress (WIP) limits of Kanban diverge from the practices advocated by Extreme Programming.

C. Kanban promotes anti-push-driven system to maintain workflow management in accordance with Team capacity.

D. Kanban isn't bound to adhere to the traditional tri-column structure of To Do, In Progress, and Completed.

2 / 5

32. A software development company is transitioning to Agile methodologies. In their new framework, the Agile Coach is tasked with guiding the overall shift in processes and mindset. The Product Owner collaborates with stakeholders to prioritize the product backlog, while the Scrum Master focuses on facilitating the daily scrums and sprint retrospectives. During a team meeting to clarify roles, some misconceptions arise regarding role of the product owner, prompting a discussion to correct any misunderstandings about her duties. Which one of the following is NOT the responsibility of the Product Owner?

A. Develop and communicate a clear product vision to the development team and stakeholders.

B. Authorize the team to determine the value-based prioritization of user stories

C. Determine the priority of items in the product backlog based on customer needs, business goals, and market trends.

D. Participate in sprint planning meetings to help the team select and commit to user stories for each sprint.

3 / 5

33. You are a Project Manager leading an Agile development team in a software development project. Your team is about to start a Sprint Planning Meeting for the upcoming sprint. The Product Owner, Scrum Master, and Development Team members are present. The product backlog has been prepared with several user stories and tasks. What is the first action you should take in the Sprint Planning Meeting?

A. Team members initiate the sprint planning process by reflecting on insights gained from the previous Sprint Retrospective to initiate planning for the next iterations

B. The Product Owner begins by introducing a prioritized list of user stories to decide which tasks will be included in the upcoming sprint.

C. The Sprint begins with outlining the overarching aim or objective that the team intends to accomplish throughout the sprint.

D. To ascertain which user stories will be addressed and the amount of work that can be tackled, team members initiate the process by conducting a capacity/velocity analysis.

4 / 5

34. In a Scrum project, the Product Owner is keen to release a Minimum Viable Product (MVP) to the market as soon as possible. The development team has completed a set of user stories during the current Sprint, and there's a desire to release these features to gain early user feedback. However, during the Sprint Review, some stakeholders express concerns about the MVP's completeness and the potential risks of releasing it prematurely. What should the Scrum team consider regarding the release of the MVP?

A. Scrum Team should not release the features now as Scrum Framework promotes fixed release dates as per Release planning and

B. The Scrum team should always prioritize feature completeness over early release, and MVPs should not be considered within the Scrum framework.

C. Assess the MVP's readiness and potential impact on users. Release planning should consider the MVP as part of the overall product roadmap.

D. The Scrum team should immediately release the MVP as it aligns with Scrum principles of iterative development, and any missing features can be added later in subsequent Sprints.

5 / 5

35. You are a Scrum Master facilitating a Sprint Review meeting for your Scrum team. The team has just demonstrated a set of completed user stories to the stakeholders. During the discussion, a stakeholder asks about the significance of the "Definition of Done." They want to understand its primary purpose. How would you explain it to them?

A. To define the scope of work for each sprint.

B. To specify the acceptance criteria for user stories to be considered complete

C. To establish the criteria that must be met for a product increment

D. To determine the test scenarios to verify user stories meet customer requirements

Your score is

The average score is 10%

Discover More

Contact Details