PMI Agile Certified Practitioner (PMI-ACP)® - PMI-200무료 덤프문제 풀어보기

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

B. Conduct retrospectives at the end of every sprint.

C. Include senior management in the process decisions.

D. Communicate the processes and expectations to the team.

A. Ask the stakeholder for estimates for each user story.

B. Schedule more demos during each sprint.

C. Invite the stakeholder to the daily stand ups.

D. Keep sprints short.

A. Determine how much work can be delivered.

B. Calculate how much work will fit into the next iteration.

C. Estimate the project team's capacity.

D. Estimate items in the product backlog.

A. Gather the details from the team members before sprint planning

B. Schedule a story grooming session with the product owner before sprint planning

C. Email the product owner requesting detailed story specifications and wait for a response

D. Conduct a planning poker session with the team

A. Notify the product owner and have the product owner verify the backlog priority, then encourage team to continue working on the backlog.

B. Encourage the team to document the improvement and prioritize it for the upcoming iteration, instead of building it now.

C. Since the team has extra lime, notify the product owner and secure approval for the extra work on this feature.

D. Instruct the Scrum Master to have the team use the extra time to complete the extra feature work in the current iteration.

A. Reach out to other, more experienced teams to seek input as to how to present the technical details in a more informative manner.

B. Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.

C. Explain the importance of the technical architecture and design presentations and improve the presentation format.

D. Invite technical managers and architects who will be a more appropriate audience to their sprint reviews.

A. Apply work-in-progress limits.

B. Separate large user stories.

C. Replace user stories into features.

D. Organize user stories into epics.

A. Organize training sessions to create awareness around the agile values for stakeholders.

B. Facilitate a face-to-face discussion and have stakeholders agree to shift to agile for future projects.

C. Recommend an external facilitator as no one in the organization is able to eliminate this roadblock.

D. Allow stakeholders to discuss without the scrum master's intervention.

A. Assign corrective actions to the backlog for the team to identify the mandatory defect information.

B. Stop the current iteration to discuss defect quality issues and explore solutions.

C. Discuss and explore solutions in the next planning meeting and take corrective actions as required.

D. Generate insights at the next retrospective and adjust processes as decided by the team.

A. Observe which team members are comfortable working together, then assign accordingly.

B. Ask the team members' functional managers for guidance on how to group the team members.

C. Assign team members to their respective teams based on the skills known to the scrum master.

D. Ensure that members begin to self-organize as small teams with efficiently distributed skills.

A. The development team needed to urgently set up all the test data the previous week; however, due to a glitch in the system this will not be available until before the demonstration.

B. The team has started working on the iteration, but the requirements artifacts are under review by the product owner.

C. Performance issues in the testing environment, leading to a 2-day delay in implementing the code.

D. Due to frequent context switching, the daily 15-minute touchpoints last an hour even/ day, reducing the team's time to finish activities for the demonstrations.

E. A developer is unable to work on their tasks within an iteration, because senior management is constantly pulling them into production incident analyses.

F. The offshore testing team is pulled away at the last minute from a high-profile initiative and testing cannot be resumed until a new testing team is assigned.

A. Communicate product backlog items to the stakeholders

B. Conduct an iteration planning meeting

C. Facilitate a product development roadmap workshop

D. Collect stakeholder requirements

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

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

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

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

A. Add risk mitigation time to each requirement

B. Apply the 80/20 rule, reserving 20 percent of each sprint's capacity for risk mitigation

C. Hold all risks until they become issues, then add issue resolution tasks to the product backlog

D. Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints