The traditional approach to comms is to do a lot of planning up front. Many teams will embark on a “comms strategy”, or perhaps write a set of “comms principles”, and then set about filling a calendar or grid with expected messages at expected times. Most of these are unnecessary when doing comms for agile work and agile teams.
In agile programmes people prefer to talk about roadmaps rather than plans. This post is about the reasons behind this and the benefits of using a roadmap rather than a gantt chart to manage pure agile, or mixed methodology programmes.
Roadmaps can be a powerful tool to communicate the vision for a product’s development, unite teams of makers around common goals and let stakeholders know (roughly) when they can expect the improvements they care about.