AgileSweet Communication

Communication is mutual understanding.

Communication optimisation is the most important factor for optimising the business value of the software delivered.

Communication optimisation is imperative for the maximisation of creativity and productivity.

Concepts to Cards

The quantum units for development are requirement card and defects and their clear communication is imperative to the success of a project.

Cards to Code

Code to Value

Face-to-Face Communication

Maximise then optimise face-to-face communication.

>> Click here for more details of the economics of optimising face-to-face communication.


Typically everyone should be invited to all meetings where they might be exposed to information that may be useful to them.

See below for a summary of AgileSweet meetings (and see also Ecology/Processes).

Requirement Card and Project Tracking Database or Spreadsheet

Source of all tracking and metrics.

Team Wiki (or Shared Folders) and Broadcast Emails


The following events should be broadcast to the team and all stakeholders.

Change to cards – new card, change of card concept, obsolete card, change of priority, change of status.

New defects – severity level 1 and level 2 defects should be communicated (see Testing/Defects).

Release scheduling, reminders, changes to release schedules, confirmation of releases and cancellation of releases.

Progress reports.

Confirmation requests and replies for designs.

Documents and Files

Requirement card elaborations – drawings, flow diagrams, useful tables and data, narratives.

Background documents.

User stories and hypotheticals.

Test cases.

Test execution movies.

Defect Tracking System

Instant Messaging

Has its place especially with distributed development and concentration rooms. Private jokes should not be instant messaged.

See Ecology/Place for more information on distributed development setups.

Overview of Meetings

Start on time. If possible have tight agenda distributed with options suggested