PMI-ACP 無料問題集「PMI Agile Certified Practitioner」

（A）Identity and create personas that can help the team better understand the needs of the target user base.

（B）Push it back due to the number of users and socialize the idea of developing a standard application and training session for all users.

（C）'Engage the human resources (HR) team to identify the key users and interview all of them accordingly.

（D）Build a minimum viable product (MVP), a standard application for all users, and release the new version (per users/areas).

（A）Email all stakeholders with status updates

（B）Create a central repository for information, and provide access to team B

（C）Use an information board that will be visible to all passing through the workspace

（D）Provide team B with the information on an "as needed" basis

（A）Prioritizing stories

（B）Tracking progress

（C）Estimating story size

（D）Validating a product

（A）Add code cleanup activities to the next release backlog and request documentation from the product owner

（B）Add code cleanup activities to the next iteration and request clarification from the product owner

（C）Add code cleanup activities to the next iteration and ask the product owner to end the current iteration

（D）Add code cleanup activities to the product backlog and request prioritization by the product owner

（A）Reevaluate the minimum viable product (MVP) deliverables to remove high-risk stories and meet timelines.

（B）Adjust the story points included in each sprint to represent the actual velocity.

（C）Perform value stream analysis to eliminate the processes with wastage.

（D）Include high-risk stories in earlier sprints to deliver incremental velocity.

（A）Develop a reward system related to position and years of experience.

（B）Clarify project goals and project contract constraints.C Promote cross-training and -entering among tea- members

（C）Introduce performance standards and evaluation methods.

（A）Consult with the project sponsor and project team to resolve the issue.

（B）Consult with the project team to rework the existing estimates.

（C）Consult with the product owner to prioritize the new work at a higher level.

（D）Consult with the product owner and project team.

（A）Schedule in-person monthly meetings with key stakeholders to review the project's progress

（B）Seek regular input from project stakeholders, and reflect this input in the backlog's priorities

（C）Focus on stories based on the highest number of story points to first address those items with the highest value

（D）Schedule regular meetings with the scrum team to write, groom and size user stories

（A）Re-estimate by assigning more story points to smaller stories to increase the velocity.

（B）Set the velocity to the delivered story points of the last sprint.

（C）Use different estimation methods for stories and defects to meet the desired velocity.

（D）Split each story into multiple stories to meet the desired velocity.

（A）Stop the team politely and suggest scheduling another meeting to discuss this specific matter.

（B）Inform the team that the meeting will be extended so there is time to hear what the team member is reporting

（C）Ask the team member to wait to discuss until the next daily coordination meeting, the team needs to review the current status.

（D）Dismiss the rest of the team from the meeting to focus on the problem reported by the team member

（A）Problems that arose

（B）Solutions to project problems that were built into the last sprint

（C）Solutions that saved the organization the most time and money

（D）Problems that were solved

（A）Ask the developer to build and let the testing be postponed until after the release, and inform the architect that the feature will be implemented.

（B）Inform the sponsor that features are being added and will extend the release date after getting approval and communicating this to the architect.

（C）Have the team brainstorm and propose error logging at the client level, which will have a higher impact with less effort within the release timeline.

（D）The product owner should explain to the architect that monitoring, alerting, and logging are not essential for the customer and can be prioritized post-release.

（A）Ensure the teams are working together daily throughout the product development and are keeping the team's progress up to date.

（B）Ensure there is an environment where team members feel comfortable sharing their ideas, concerns, and feedback.

（C）Ensure the team is able to release new features and updates frequently so that customers can see the product and provide feedback.

（D）Ensure the customer is provided with regular project status updates and that the meeting minutes are well documented.

（A）Use MoSCoW ratings to keep people engaged.

（B）Hire a SAFe coach to provide encouragement.0 Employ BDUF to help with providing structure to meetings

（C）Use the DISC framework with each team member.

（A）Delegate the decision for the best feature implementation to the most senior team member.

（B）Coach the team individually then the whole team during the Sprint review on how to resolve this conflict.

（C）Decide on the technical implementation that best fits the purpose of the technical design.

（D）Bring a subject matter expert (SME) from the technology design team to act as a consultant for the team.

（A）Work with the customer to understand which user stories will deliver the best business value, re- prioritize the backlog, and share it with the customer to provide release plans.

（B）Explain to the customer that an agile approach requires re-prioritization at the beginning of each sprint, so it is not possible to provide a roadmap.

（C）Ask the customer to develop a roadmap the team can follow for future delivery.

（D）Work with the product owner to develop a tentative roadmap for the customer but explain that it is always subject to change.