ICC Communication Artifacts




Role in Communication

Project planning Meeting
ICC Manager
High level project planning meeting, big picture of what features goes in which release. This meeting is omitted if ICC runs continuous development model without specific project scope in ICC.
Release planning MeetingProduction Manager What will be released in next release: details, resourcing, scheduling and testing
Sprint planning MeetingICC Manager or separate scrum master What shall the implementation team, which is not necessarily ICC itself, do in the next sprint
Integration vision statement ArtifactICC Director Communicates the end goal of the project to the project team and the organization.
Integration roadmap ArtifactICC Director Communicates a long-term view of the features that support the integration vision.
Integration business backlog ArtifactAnalyst Communicates the scope of the current integrations to the ICC team and business
Release plan ArtifactICC Manager Communicates the goals for a specific release.
Sprint backlog ArtifactICC Manager Updated daily, it provides immediate sprint and project status to anyone who needs that information. The burndown chart on the sprint backlog provides a quick visual of the sprint status.
Task boardorKan-ban ArtifactICC Manager Visually publishes out status of the current sprint or release to anyone who walks by the scrum team’s work area.
Daily scrum MeetingICC Manager Provides the scrum team with a verbal, face-to-face opportunity to coordinate the priorities of the day and identify any challenges.
Face-to-face conversations InformalEveryone The most important mode of communication on an agile development.
Sprint review MeetingICC Manager The embodiment of the “show, don’t tell” philosophy. Displaying working product to the entire team conveys project progress in a more meaningful way than a report ever could.
Sprint retrospective MeetingICC Manager Allows the scrum team to communicate with one another specifically for improvement.
Meeting notes InformalICC Manager These are an optional, informal communication method.Meeting notes can capture action items from a meeting to make sure people on the scrum team remember them for later.Notes from a sprint review can record new features for the product backlog.Notes from a sprint retrospective can remind the scrum team of commitments for improvement.
Collaborative solutions InformalICC Manager White boards, sticky notes, and electronic collaboration tools all help the scrum team communicate. Ensure that these tools augment, rather than replace, face-to-face conversations.

Source: http://www.dummies.com/how-to/content/agile-management-communication-methods.html

One thought on “ICC Communication Artifacts

  1. Pingback: Establishing Integration Competency Center, part 5 | Integration War Stories

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s