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

A. Evaluate the team's capacity and help them select user stories for the iteration based on 60% of their capacity utilization.

B. Evaluate the team's capacity and help them select user stories for the iteration based on 80% of their capacity utilization.

C. Coach the team to decompose the backlog activities to granular, simple tasks that are easier to estimate and complete.

D. Discuss options to add more people to the team so they can complete the tasks on time and within budget.

A. Ensure the agile leader documents a risk in the risk register and communicates the risk to the project sponsor.

B. Be transparent with all the stakeholders and make them aware of the issues encountered and the current project's status.

C. Ask the product owner to make a decision as to whether or not all the stakeholders should be kept informed about the current project's status.

D. Support the team's decision, and since the team is confident about being able to resolve the issues in time, do not raise the issues as risks with the stakeholders.

A. Ensure all iteration goals are fully developed at the beginning of the project.

B. Work with the team to establish goals for the product at the beginning of each scheduled iteration.

C. Send the team the latest version of the release plan so they can provide feedback.

D. Refine the product backlog and identify the Minimum Viable Product

E. Invite the customer to the sprint planning meeting to explain what is deemed most critical to their business.

A. Infrastructure updates

B. Funding decisions

C. Just-in-time (JIT) refinement

D. Stories to be released in each sprint

A. Reduce the number of participants in the daily coordination meeting so only one representative for each user story or area of expertise can participate each day.

B. Change the structure of the daily coordination meetings so team members only comment on the blockers they face during the day.

C. Let team members decide how to execute the meeting because they are self-organized and should know what works for them.

D. Pay attention to the comments of each team member during the meeting and intervene every time they deviate from the objective of the meeting.

A. Planned incremental iterations and a focus on people over processes.

B. A culture of collaboration, tools, and processes to support continuous delivery.

C. A mindset shift to establish controls over all development and operations processes.

D. New tools that enable teams to continuously build, test, and integrate.

A. Dismiss the rest of the team from the meeting to focus on the problem reported by the team member

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

C. Inform the team that the meeting will be extended so there is time to hear what the team member is reporting

D. Stop the team politely and suggest scheduling another meeting to discuss this specific matter.

A. Ask the product owner to conduct these discussions in individual meetings with the team members.

B. Remind the team that staying on topic during meetings is part of being a self-managing team.

C. Issue fixed agendas and a decision log for all scrum events to ensure that only relevant agenda points are discussed and decisions are appropriately captured.

D. Remind the team of the purpose of each scrum event, and implement a policy that long conversations deviating from the scope of each event will be stopped.

A. Inform the stakeholder that no detailed documents are provided using agile practices

B. Ask the team to supply the information to the stakeholder

C. Provide all information requested by the stakeholder

D. Set expectations regarding the appropriate level of details requested during this stage

A. Ask the scrum master to select an item from the backlog on which to work

B. Jointly decide with the scrum master on an item from the backlog on which to work

C. Begin working on an item in the backlog

D. Ask the product owner to select an item from the backlog on which to work

A. Review the process value stream to determine potential improvements

B. Discuss the efficiency at the next iteration retrospective

C. Review the value the customer receives from the user story to determine backlog priority.

D. Discuss the performance of the solution at the next sprint review

A. Speak up immediately during the daily coordination meeting and clarity the issue to avoid any further confusion.

B. Follow the appropriate channels by contacting the product owner and asking them to address the issue with the team.

C. Take a few minutes to speak with the developer after the daily coordination meeting and provide clarification.

D. Wait until the sprint review to explain how the product increment needs to be changed to be acceptable.

A. Review the burndown chart to identify ways to increase efficiency.

B. Chair a weekly team retrospective focusing on identifying areas for continuous improvement.

C. Identify team key performance indicators (KPIs) and create positive incentives when targets are achieved.

D. Ask a senior manager to initiate a root-cause analysis.

A. Manage risk.

B. Practice continuous delivery.

C. Put the client first.

D. Create a safe environment.