Free Access PMI PMI-200 New Release

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.