Agile PM#4 Quiz

A development team wants to receive better customer feedback during product reviews. What should the team do?

• Ask the customer to operate the product's features during the review, and record the customer's reactions.

• Email detailed image documentation of the product's features to the customer for their independent review.

• Show the product's feature codes during the review to enable better understanding of coding operations.

• Ask the team's business systems analyst to operate the product's feature for the customer during the review.

In what situation should a Scrum team create a spike?

• The team does not have the knowledge to complete a task.

• A new team member is being updated on the project.

• Consultants have been brought in to supplement team resources.

• A firm estimate for a story cannot be established.

Due to a major issue, a key tool central to an engine of a team's product has been upgraded. How should the team account for this when reporting to upper management?

• Show the technical debt in the team's velocity.

• Re-estimate the current stories.

• Create a technical debt backlog.

• Send out a mass communication about the upgrade.

During an iteration, a team encounters complexities for which there are two possible solutions. One is a quick fix with minimal project impact; the other is more strategic, but could have significant cost and schedule implications. What should the agile practitioner do?

• Ask the product owner to collaborate with the stakeholders to agree on the proper solution.

• Have the agile leader raise this as an issue requiring a team decision.

• Ensure transparency with the stakeholders so they understand the options, and group decision is made.

• Ask the team to collectively decide on the solution and inform the stakeholders.

A coder is struggling to satisfy a product owner's specific requirements. How can a daily standup help the coder?

• Direction from the agile practitioner can be obtained.

• Possible solutions can be discussed with the team.

• The issue can be raised with the team to create visibility.

• A discussion on whether the code requirement is a priority can be held.

An agile coach wants to ensure that team members understand and work toward the same goal. What should the coach ask team members to do?

• Prepare their goals and share them with the team.

• Write an elevator pitch about the project.

• Conduct a collaboration workshop for goal setting.

• Meet to determine roles and responsibilities.

During sprint execution, a team member notices that a missed feature must be implemented. What should the agile project manager do next?

• Quickly estimate, design, and complete the story implementation.

• Ask the product owner to add the story to the product backlog for future prioritization and planning.

• During the retrospective, determine the root cause of why the story was missed during the planning stage.

• Extend the iteration deadline to accommodate the implementation of the missed story.

An agile team is repeatedly asked for status updates by senior management, some of whom are not collocated with the team. What should the team do to address this?

• Provide senior management with access to the team's online kanban board.

• Ask the agile coach to speak with senior management.

• Invite senior management to the next iteration planning meeting.

• Provide accurate and timely answers to all requests from senior management.

A product owner asks the development team to add an item during backlog grooming. What should the product owner do to validate the assumption that the added item will generate value?

• Accept an increment of functionality during the sprint review.

• Set the sprint goal before selecting product backlog items during sprint planning.

• Release a product increment to the market, and validate it against users and the market.

• Inspect the sprint burndown, and reprioritize the backlog at the daily scrum.

How should a project lead ensure that stakeholders are aware of a project's progress?

• Present stakeholders with relevant data compiled in graphs.

• Showcase specific prioritization techniques to reassure stakeholders that important feature requirements are being implemented.

• Provide stakeholders with metrics and lessons learned from similar previous projects.

• Involve the stakeholders at every level of the decision-making process.