PMI PMI-200 Dumps

Task

Iteration

Product

Release

Another name for the daily standup project meeting in a Scrum team.

Amechanism that coordinates multiple teams working on a single project.

Aproject meeting that happens twice every day across the Scrum teams.

An occasional leadership meeting that provides direction to multiple Scrum teams.

Task

Team

Product

Performance

Story card

Burndown chart

Retrospective

Storyboard

The team

The Product Owner

Management

Project manager

Burndown chart

Gantt chart

Hours expended chart

Management baseline chart

Requirements, coding, and testing.

Testing, coding, and refactoring.

Testing, refactoring, and validation.

Requirements, coding, and refactoring.

is fully committed to team success yet respects the prescribed roles and titles of team members.

owns its decisions and commitments and is motivated to succeed at any cost.

is self-organizing, empowered to make decisions, and consensus-driven, with constructive disagreement.

produces a high volume of business value through intensive collaboration and avoidance of conflict.

relatively few locations, with each location team comprised of a complete development group developing decoupled subsystems.

locations in the same time zone, working on the same systems while leveraging rich communication channels.

relatively few locations, and tasks are divided along functional lines with design in one location, coding in another, and testing in another.

many locations, with relatively few people at each location developing and testing decoupled subsystems.

Risk management

Small releases

Project management

Project charter

Shorten the iteration to meet the estimated velocity.

Continue to work with the estimated velocity.

Increase their estimated velocity.

Release members to meet the estimated velocity.

Customer at the start of the iteration.

Customer as late as possible during the iteration.

Tester after the team has finished the coding.

Development team at the start of the iteration.

Agreeing on a due date.

Sharing information.

Agreeing on the design.

Pair programming.

Burndown chart

Story card

Vision document

Backlog

After coding the story, but before user acceptance testing begins

After writing the story, but before coding begins

At the start of Product Backlog prioritization planning

After estimating the Product Backlog, but before Sprint planning begins

Qualitatively analyze the probability of a risk occurring.

Track progress on risk reduction of technical risks.

Document the external risks that could impact the project.

Illustrate the project risk profile and new and changing risks.

Using the most highly visible method possible

On a need-to-know basis depending on role

According to the project communications plan

Through a series of stakeholder meetings

Business value delivered chart

Product technical specifications

Automated code coverage report

Scrum-of-Scrum report

Release vision, assumptions, action items, and iteration goals

Prioritized Product Backlog, risks, action items, and release goals

Estimated iteration velocities, risks, action items, and Release Backlog

Risks, action items, dependencies, and Release Backlog

Osmotic communication is reduced; space is used more efficiently; groups work together more effectively, and team dynamics are improved.

Costs are reduced as the need for conference rooms decreases, and the team can keep track of where members are more accurately.

Team members can be held more accountable for their time and effort, and pair programming is easier as people have less distance to move to sit with their partner.

Communication is improved; wait-time and rework are reduced; barriers between groups break down, and groups gain respect for each other professionally.

management

project manager

customer

project team