Principle: Communicate Continuously and Clearly
Agile projects are based on adaptation: Generating increments of the product, using them to receive feedback, and iterating while considering the feedbacks. (See the Build Incrementally from Firm Foundations and the Develop Iteratively principles.)
The build-feedback cycle is not possible unless we have effective, continuous communication, i.e., communication between managerial, technical, business-oriented, and process-oriented people. (See the Collaborate principle.)
Agile projects have a great preference for face-to-face communications (also reflected in the principles behind the Agile Manifesto), and the use of information radiators (big visible charts) and low-tech tools such as whiteboard and sticky notes instead of fancy tracking software, which are all ways of enhancing communications.
Another common theme in Agile projects, including DSDM, is the Daily Stand-Up meetings, and frequent review meetings, which help have continuous communications in a systematic way.
Written by Nader K. Rad
This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.
This wiki is developed and managed by an accredited trainer, independent of Agile Business Consortium and APMG. While aligned with their guidelines, it’s not an official resource.