PMI-ACP試験無料問題集「PMI Agile Certified Practitioner 認定」

A. Meet with the product owner and stakeholders to discuss the issue

B. Review established ground rules with the team

C. Ask team members specific questions to identify the cause

D. Encourage the team to continue working to maintain the iteration's schedule

A. Conduct retrospectives at the end of every sprint.

B. Include senior management in the process decisions.

C. Include process feedback in the next sprint planning session.

D. Communicate the processes and expectations to the team.

A. Share the project's trajectory with the legal department

B. Work with the customer to narrow the scope

C. Meet with the team to gain alignment with the legal department's need to stay within the contracted time and scope

D. Meet with the legal department to help them understand that the customer and the team are satisfied with the time and deliverables

A. An Agile Manifesto should be created to document the project stakeholders, their desired outcomes, and identified risks.

B. A user story should be created for all key stakeholders to list their individual business objectives and needs.

C. A product backlog should be created to list the project requirements from all of the project stakeholders.

D. A project charter should be established and reviewed throughout the project life cycle to ensure the accurate documentation of stakeholders' interests and expectations.

A. Work with the client to ensure that the requirements are clear enough to allow a correct estimation and refine the backlog if needed.

B. Recommend that the team skip requirements that are too complex and estimate them later through progressive elaboration.

C. Assist the team with schedule planning to mitigate risks, including the possibility of crashing if needed.

D. Implement clear measurements to control any deviation and therefore ensure the project's success per client requirements

A. Timeline of the project

B. Stated understanding of the release goal

C. Complete vision of the end product

D. Complete roadmap of the next iterations

E. List of the user stories that will be part of the next releases

A. Direct the executive to the information radiator.

B. Invite the executive to the standup.

C. Email the requested information to the executive.

D. Personally meet with the executive.

A. Attend daily coordination meetings and retrospectives with the agile coach.

B. Follow the organization's policies to remove the team member to boost team engagement.

C. Escalate the issue to senior management to make a decision.

D. Mitigate the new conflicts that appear and rely on the self-organization of the team.

A. Request that the Product Owner include a spike in the next iteration's backlog so they can perform an initial investigation.

B. Propose alternative components with which the team has experience.

C. Suggest that the Product Owner perform the initial investigation and present the outcome to the team.

D. Ask for a team extension so that an engineer with the needed experience can be added to the team.

A. Stop working on the task and include it in the next iteration

B. Remove the task owner from the project team

C. Add resources to reduce time to task completion

D. Continue working on the task until it is completed

A. Explore options for increasing knowledge in the next iteration's backlog.

B. Propose alternative tools that the team is more competent using.

C. Experiment with the tool's usage by adding extra tasks in the current iteration.

D. Ask a tool expert to join the team and perform the relevant work.

A. Define the user stories with just enough detail so the team can collaborate continuously

B. Ensure the acceptance criteria includes testing scenarios, so the team can do thorough testing

C. Complete the test cases before creating the story in the backlog

D. Define the detailed business requirements so that the team can continue with development

A. Regularly meet with people across the organization to share the project's lessons learned and best practices

B. Invite people from across the organization to attend daily stand-ups

C. Invite people from across the organization to attend the release meeting and project retrospectives

D. Invite people from across the organization to attend retrospectives