PMI-ACP Exam Dumps - PMI Agile Questions and Answers

Communication, respect, and courage

Communication, process flow, and authoritarian structure

Value people over processes, communication, respect disagreement, and strive for consensus

Rapid feedback, assume simplicity, incremental change, embrace change, and quality work

Follow the project schedule created at the start of the project.

Hold regular retrospectives and have team members commit to specific actions.

Allow team members to choose improvement items and trust their judgment.

Encourage team members to write code that is tightly coupled together.

Conduct an internal review to validate functionality before shipping

Audit the quality control process to ensure that the product adheres to requirements

Lengthen iterations to ensure there is sufficient time to build functionality

Hold product review sessions with the client to obtain product acceptance

Dismiss the team member

Discuss the situation with the functional manager

Report the functional manager to the project sponsor

Demand that the functional manager respect the project charter

Consolidate the team's updates in presentation slides and email them to the team regularly.

Radiate key information such as the team's work, progress, and velocity at the team's common area.

Share team progress individually with each top performer every week.

Attach sticky notes for each assignment to the wall in the team's area.

Work with the team to create explicit rules such as coding and quality standards and testing policies.

Discipline the team members and institute status meetings with penalties for any future escaped defects.

Hire more generalized specialists because the current team members cannot keep up with the pace.

Apply work in process (WIP) limits so the developers are not pressured to release code that is problematic.

Create a new team to deliver the dependencies, and bring team B under performance management.

Conduct a vision-sharing session with the teams to communicate the project's overall goals.

Swap team members from both teams so that deliveries are better supported.

Discuss negotiating the delivery timelines with team A.

Shared vision statement and sprint goal

Release burnup chart

Velocity metrics

Iteration burndown chart

Identify a team member to do a proof of concept using this framework.

Email the team directing them to immediately begin using this new framework.

Obtain feedback from team members on the new framework, and then suggest that the product owner create a backlog item to do a spike on it.

Discuss this option at the next retrospective.