LOGIN

REGISTER
Seeker

Other Communication Tools (Email, Slack, Wikis)

Select the language:

You must allow Vimeo cookies to view the video.

Unlock the full course and get certified!

You are viewing the free content. Unlock the full course to get your certificate, exams, and downloadable material.

*When you buy the course, we gift you two additional courses of your choice*

*See the best offer on the web*

Transcription Other Communication Tools (Email, Slack, Wikis)


Beyond specific project management tools such as Jira or Trello, Agile teams rely on a variety of additional communication channels for day-to-day coordination, information sharing and knowledge management.

Email, instant messaging platforms such as Slack, and knowledge management systems such as Wikis (e.g., Confluence) play distinct but complementary roles.

Using each tool effectively, understanding their strengths and weaknesses, is crucial to avoid information overload, ensure that important messages reach the right people at the right time, and maintain a healthy flow of communication within and outside the team.

Effective Use of Email (Filtering, Avoiding Urgency)

Although ubiquitous, email presents challenges in fast-paced agile environments.

People often ignore it or don't read it right away, making it unsuitable for urgent communications.

If an urgent email is sent, it should always be supplemented with another channel (Slack, call) to ensure attention.

Another problem is "email fatigue" caused by too many notifications and irrelevant messages, which leads to ignoring important information.

To mitigate this, it is critical to teach and use filters and labels (as in Gmail) to organize the inbox, prioritize messages and automatically move less critical notifications (e.g., from Jira) to specific folders, keeping the main inbox uncluttered.

Slack as a Communication Center (Channels, Notifications, Integrations)

Messaging platforms like Slack have become very popular with agile teams because of their immediacy and flexibility. Key strengths include:

Channels: allow conversations to be organized by topic, project or team, reducing overall noise.

Configurable Notifications: Users can adjust notifications by channel, muting less important ones and ensuring they receive alerts for crucial ones, combating information overload.

Integrations: Slack integrates with many other tools (Jira, Asana, Trello, GitHub, etc.), allowing to centralize notifications and actions.

Plugins and Bots: They extend the functionality with tools for surveys (Polly), estimates (Team O'clock), GIFs (Giphy), etc., facilitating certain team interactions.

Slack fosters more fluid and contextualized communication than email for daily team interactions.

Wikis (Confluence) for Knowledge Management (Onboarding)

Internal Wiki systems or platforms such as Confluence (which integrates with Jira) serve primarily for more stable, long-term knowledge management.

Although they can sometimes be difficult to find specific information or keep up to date, they are very valuable for documenting pro


other communication tools email slack wikis

Recent publications by professional agile coach

Are there any errors or improvements?

Where is the error?

What is the error?