Agile/Scrum- Communication Plans

Communication Plan
Communication is the key that brings together all of the vital components of your agile/scrum project. Without a stable communication plan, your ability as a scrummaster for your project will be adversely impacted in all the wrong ways. In agile/scrum your communication plan will document the needs of the scrum team and product owner. We all know that a hallmark of agile/scrum framework is the face to face communication style, but as we all know that sometimes there needs to be a more formal document (depending on your organization) The communication plan documents the information and communication needs of the project stakeholders and all other parties that are involved with the project. The plan states who needs what information, what format they need it in, when they need it, and how it is transmitted to them. At the bottom of the post I have attached an example of one of my communication plans that I have used in my previous work experience.

I also ask a few questions regarding the creation of the communication plan (see below)
A) How is information gathered and filed?
Q) If you use a consistent file naming convention, you will help eliminate misplaced or hard-to-find information, store on wiki or shared server.
A) When is information gathered?
Q) Clearly communicate your schedule to the project team then your team will adhere to when they report problems to you.
A) Who has access to the information?
Q) Some information will be proprietary or not for random dissemination, use passwords for team members.
A) Who may represent the team in conversations and meetings?
Q) ScrumMaster

From Paul Gravina Examples of My Testing Documentation

Popular posts from this blog

Burn Down vs. Gantt Chart

Cost Control Agile/Traditional