| | Description | Agile values | ‍‍‍‍ | Agile Manifesto Principles | Other Agile principles | Agile practices | Discussion | Links from this KA to other KAs | References | External links | Read in another language
Source: journyx (2013)

Alternative Names


‍‍‍‍‍‍‍‍‍‍The PMBOK definition of communication management as the process required to ensure timely and appropriate generation, collection, distribution, storage, retrieval, and ultimate disposition of project information‍‍‍‍‍‍‍ (PMBOK, 2008). Different types of communication exist- verbal, non-verbal, formal, informal, and the way of encoding and decoding them correctly may affect positively the performance and the organisation’s outcomes.Communication in projects is often referred as a desirable competence of the project manager for managing projects successfully (Henderson, 2008). Project communication management can also be explained as the process of managing the communication between different stakeholders on a project. According to Pinto (2010) the project manager should develop good presentation and meeting skills, in order to manage different types of communication, such as formal and informal, with different people, working on the project. Pinto (2010) suggests that in projects, one of the most important ways of communicating is through meetings. Meetings give the project manager the possibility of communicating with various parties interested in the project, such as top management, client, team members, which might help in understanding their requirements, expectations, needs and desires.

Agile values

‍‍‍‍‍‍‍‍‍‍The Agile Manifesto ‍‍‍‍‍‍‍‍‍‍value‍‍‍‍‍‍‍‍‍‍ "Individuals and Interactions over process over processes and tools" can be related to Communication management as the communication between the team members, which appears to be extremely important in order to have successful working environment. People working together effectively suggests excellent communications management, where “interactions” also means having constant meetings, which in ‍‍‍‍‍‍‍‍‍‍Agile are the face-to-face meetings and face-to-face conversation (the Agile Manifesto principle- "The most effiect and effective methog of conveying information to and within a development team is face-to-face conversation). ‍‍‍‍‍‍‍‍‍‍According to ‍‍‍‍‍‍‍‍‍‍the general Agile Methodology‍‍‍‍‍‍‍‍‍‍ the people and how they work together are the most important factor, not the processes and tools or following strictly well planned pattern, with barely no possibility of flexibility.
Communication on a project also involves the written one, such as for example piles of documentation, informing the client what is going to be build during the project. However, Agile Project Management suggests less documentation and more emphasis on presenting the actual working product, which will be easily understandable and more lucid for them, than a complex technical document. This facilitates the communication between the two parties.
‍‍‍‍‍‍‍‍‍‍Another aspect of communication management, which can be found as the value "Customer collaboration over contract negotiation" is the customer collaboration. In fact the communication with the customers is of crucial importance, because the more the customers are informed about the progress of the project, the higher their support and willing to help is‍‍‍‍‍‍‍‍‍‍. Communicating constantly with the customer helps the team and the manager understand better their needs and expectations.‍‍‍‍‍‍‍‍‍‍


Agile Manifesto Principles

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. According to PMI (2008), project communications management is aimed at identifying stakeholders early in the project, planning communications, distributing information, managing stakeholder expectations and reporting performance. Stakeholders may be internal or external to the project. Stakeholders are the people and organizations such as sponsors, customers, performing organizations and the public that are involved in the project whose interest may negatively or positively affect the completion of the project. Although, the products are delivered according to the customer’s expectations, they are not delivered early. OGC (2009) indicates that the plan theme promotes communication and control by describing the means of delivering the products. Products are not delivered early as project needs to go through all the stages and consultation is done frequently between the project board and project manager at each stage boundaries sequentially before delivery.
    The traditional approach (waterfall) is not supported by this principle because during the implementation of a project, the project cannot continue until the previous phase has been properly approved by the stakeholder. More time is spent on requirements and design in order to reduce coding and testing costs (France, 2015).
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. This principle relates to project communication management. OGC (2009) indicates Change as one of the themes of Prince2 and controlled changed is emphasized when it is in-line with the business case. PRINCE2 responds to change and the Project Board are responsible for deferring, rejecting or approving change. They may also delegate some decisions to the Change Authority. A change request may prompt ad hoc direction, the Corporate may revise the project mandate in response to change or inform that the project board to close the project. According to OGC (2009: 93) change are prioritized, using MoSCoW (Must have, Should have, Could have and Won’t have for now). Only changes that are essential for the viability of the project are implemented even in late development and this change is communicated across the project team. PMI (2008) points out that for change to occur in a project even late in development, the change must be communicated across the project team, evaluated for its impact on the project before it can be rejected or approved by the change control board. Only change with a positive impact are implemented on a project. The traditional plan driven approach does not relate to this principle. This approach discourages change, mainly during late development. It finds out the root of change and assesses the impact through an integrated change control process (Vaishampayan, 2014). Waterfall methodology can be easily understood and communicated to all stakeholders (France, 2015).
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
    During the development and implementation phases of a project, software is delivered to clients, commonly according to their requirements and specifications. This is practically impossible without the constant communication between the project manager, the project team, the clients’ teams/the end users, and all sponsors and stakeholders. Organisations which adopt effective and efficient communication methods are likely to stay within scope, exceed quality requirements and standards, and deliver the intended business benefits (Communication: The Message Is Clear, 2013).
  4. Business people and developers must work together daily throughout the project. It is generally agreed that communication in any project is the most important component and aspect contributing towards project successes. It is crucial that the business personnel interact and communicate with software developers, so that requirements are clearly discussed and understood (Charvat, 2002). Communication is most effective when people work together and carry out the correct work to achieve the correct outcome objectives. Effective communicators recognise that sharing information has a direct correlation with achieving goals, and that this sharing of information is typically a two wat street, where managers communicate the change and the requirements they would like to see to the developers. Developers in turn will understand and achieve the required standards of software change/software development (AgileModeling, 2016).
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
    By providing the right environment and support, individuals feel empowered and able to communicate any issues or concerns, and commit to one another. This aids teams and organisations to succeed in their projects as trust is instilled via constant and open communication, especially in project teams. According to pmi.org (2011), the best way to build positive relationships in project teams is to create trust, and this is achieved through open communication and honesty. Thus, communication, motivation and trust all complement one another. Effective communication and the completion of tasks as a result, leads to motivated individuals, creating the right environments, support and trust.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. PMbok approach to communications management involves having a communication plan, defining key stakeholders and requirements, appointing a lead, and defining the medium of communication. Agile however identified that most effective method of communication as being face to face, enabling decisions to be made quickly. It also saves time used to send emails and waiting for a reply and allows nonverbal communication to be taken into consideration which is absent in other types of communication like telephone and email. Face to face communication exists (including through meetings) in the PMI approach alongside other forms of communication. However, the comparative smaller and regulated number of meetings in the traditional approach may mean that vital topics are forgotten before the meeting is convened. This principle will also be difficult with virtual teams or distributed agile projects because people can still be distracted with video conferencing. (Robarts, 2008).
  7. Working software is the primary measure of progress. In an agile environment, progress is demonstrated to sponsors by having something to show such as a working software (Thomas and Hunt,1999). This is a type visual communication which helps the customer to decide quickly if their requirements are satisfied or otherwise. PMI (2013) has a structured way of communication which may take time and be impracticable if used in software development, as developers may need to ask a quick question towards the end of an iteration meant to deliver a working software.This is however somewhat similar to the PRINCE2 approach where the project is in stages with each stage having its predetermined deliverables. APM (2012) approach allows for flexibility and places emphasis on the interpersonal skills, especially of the project or programme manager to ensure an effective communication by using appropriate methods. The traditional approach to communication could be made more agile by dividing the projects into subprojects for better communication (Ip et al.,2004).This is similar to the spiral model (Boehm,1988).

  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Communication in project management is one of the major values which makes a project resourceful (PMI, 2013). According to PMI (2015), communication between project sponsors, developers and users is what underpins the effectiveness of agile development process, to maintain constant pace between stakeholders indefinitely. Haughey, (2015), argues that, PRINCE2 method recommends that, the entire project team and the customer should communicate regularly and organise reviewing meetings with the customer, in order to achieve constant progress in the product development process. Hass (2010) reveals that, in traditional methodology, there is effective communication between the project team and customer before the project scope is finalised, but the traditional methodology does not support communication between project team and clients, in areas, like, making changes according to time and user needs, because the method does not support continuous changes or feedbacks of new requirements between the project team and the customer after the project scope have been finalised for each stages of its sequential process.
  9. Continuous attention to technical excellence and good design enhances agility. According to PMBOK (2015) effective communication keeps stakeholders engaged and motivated to deliver good product and excellent design. According to PMI (2012), APM support communication management, because in APM communication is use to identify stakeholders, assess their interest and influence individuals and group performing the work. Saad et al, (2013) identified that, this principle can be related to PRINCE2, because in PRINCE2 quality assurance section, the technical team communicate effectively to ensure that, agreed specification and standards are communicated and performed following specified requirement from the customer, as their aim and responsibility is to achieve technical excellence and good design, as well as achieving continuous progress in the technical team. Haughey (2008), reveals that, traditional methodology supports effective communication among stakeholders. This ensures that there is continuous attention to technical excellence and product specifications are effectively communicated and implemented in order to achieve excellent product and good design to meet project objectives and users needs at each stage of its sequential process. Thus, achieving excellent product and good design can bring success to the team, satisfy clients and enhance the project team progress journey.
  10. Simplicity — the art of maximizing the amount of work not done — is essential.This principle cannot be related to communication management. (Back, 2001) points out that every time the exchange of information takes place time and project resources are used up. Internet can be a major tool to aid the management of communication but can also be a major source of the consumption of time and resources (Giffin, 2002). PMI communication management has three processes, plan, manage and control.(PMI, 2013)
    This principle could be applied by simplifying the processes, by not writing and spending time in documentation for the processes but rather what is required when its required, to find out what the stakeholder requires at each stage and only that information is relayed as quickly as possible rather than generating information that is required at later stages. Using the appropriate method were possible that is, face to face and if the stakeholder requires more information, keep it simple and as clear and accurate as possible.

  11. The best architectures, requirements, and designs emerge from self-organizing teams. OGC (2009) states that the organization theme is used to define the roles and responsibilities of the project team members and it also establishes the project’s structure of accountability and responsibility. The project manager assembles the project team and they effectively work together during projects, strategies for communication within the project are established at the beginning of the project and maintained throughout the project life cycle. The project manager is responsible for managing the team members. Similarly, traditional project management teams are also manager-led teams (Kaltenecker & Hundermark, 2014). PMI (2008) project teams are manager-led teams, where the project manager acquire, develop and manage the project team but establishes a reporting line of informal and formal communication across the team. Thus, Prince 2 teams, PMI and traditional project management teams are not self-organizing teams although there is effective communication across the group which enhances project success.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. This principle can be related to project communication management. In the prince 2 principle, lesson from experience which implies that lessons are sought, recorded and actioned throughout the course of the project. During progress reviews, this lessons are identified and communicated across the team. It is possible that this lessons may be a root cause of a problem or could be a enabler to project achievement. The project team is then required to take actions to implement improvements across the team (OGC, 2009). According to (PMI, 2008) lessons learnt are defined as learning achieved from process of performing the project. The lessons learned can be identified and documented at any phase of the project life cycle. It draws both the positive and the negative experience. It boosts the repetitiveness of a wanted outcome or result and stops the occurrence of the unwanted outcome. The lessons learnt are discussed openly among the project team, project support staff and selected stakeholders in order to remove the occurrence of issues that are likely to be unavoidable in future project. This will enable the team to be more effective and efficient in the future. Collison & Parcell (2004) concludes that lessons learned requires an effective means of communication. Conversation is the most efficient way of sharing lessons learnt.

Other Agile principles

‍‍‍‍‍‍‍‍‍‍•Our highest priority is to satisfy the customer through early and continuous delivery of valuable software‍‍‍‍‍‍‍‍‍ (Agile Manifesto) In relation without good communication between the customers and developers, requirements for the release cannot be known; hence this could affect the planning to meet the needs of the customer on time. ‍
Business people and developers must work together daily throughout the project (Agile Manifesto) This is can be achievable, when the business people and developers have good communication culture. The application of stakeholders analyst could be of an advantage to the developers at this stage, as it could help them to prioritized the in the each iterations in relation to the level of importance to the business people (product owner) using the stakeholder analysis.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation (Agile Manifesto). A communication method do varies from group meetings, telephone calls, video conferences calls, and online chats as the case maybe. In bid to disseminate information. However, the most effective and efficient means of conveying information is through face-to-face conversation. This is so, because it creates the platform for the developers to ask specific questions, create mutual trust and social bond with product owner.

Agile practices

‍‍‍‍‍‍‍‍‍‍These are some of the basic practices relevant to communication management;‍‍‍‍‍‍‍‍‍‍
Daily Stand-up (Scrum):- This practice is applied in scrum‍‍ to gather information on progress, and obstacle encountered in the process to achieves the requirement set by the product owner. These meetings as a form of communication method are done every day on the iterations.
‍‍Coding Standards (XP practice):‍‍ for effective development of the software, accepted codes are used by the team for communication. ‍‍‍‍‍‍‍‍‍‍These rules help the pair programmers to comprehend each other's the language ‍‍‍‍‍‍‍‍. And easily update or correct any synthesis errors.
‍‍‍‍‍‍‍‍‍‍Story Mapping (Scrum):- is the concept of in house communication by the team mates, using of model (presentation notes) to identifying functionality and setbacks in planning to satisfying customer's requirement on a release. ‍‍‍‍‍‍‍‍‍‍
Pair Programming (XP practice): is deliberate sharing of knowledge by working in pair on a system. This activity helps to reduce errors in the development of the software. This activity is efficient and effective, when an individual encoding the software can be helped by his/her colleague, as they switch places. This enhances good communication culture between colleagues.‍‍‍‍
Onsite Customer (XP practice):- help teammates to communicate the requirement with customer as the work progresses.


In Project Communication Management, one of the most efficient interactive ways of communicating is in the form of a "meeting". In the traditional approach the meeting has more formal nature, the participants are informed in advance about the meeting. A meeting agenda is prepared containing the objectives, subjects to discuss and roles and responsibilities. It usually lasts about an hour, with the recording of proceedings by minute taking. The meeting minute contains the results from the meeting and what is to be done before the next meeting. However, in Agile Project Management, a daily stand-ups is held.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ This meetings is time-boxed 15 minutes, there is no follow-up documentation, because the relevant information passed by any of the parties is immediately resolved after the meetings. The objective of the daily stand-up is to discuss the previous activities and obstacle encountered and possible improvement on the day activities. Mores so, project using XP framework, communicate business requirement on each iterations and prioritise it, using planning game, and pair programming in a bid to eliminate complex, reduce bugs in course of coding the software.

Links from this KA to other KAs

‍‍‍‍‍‍‍‍‍‍Project communication management can be linked to other knowledge areas, good communication is required to manage conflict resulting from Quality Management and requirement change in a project. More so, the knowledge of communication management helps in the prioritisation of stakeholders needs, as at the iteration of each stage is worked on. Project communication management can be linked to information management and knowledge management as well, as its definition and process of implementation encapsulate both knowledge areas. Information management is the collection of open information from different sources then it translated to different parties; this carries an element of communication management as described above.‍‍‍‍‍‍‍‍‍‍


Agile alliance (2011) [online] Available at:.http://guide.agilealliance.org/subway.html [Accessed: 13 February, 2013]
Collison, C. & Parcell, G. (2004) Learning to Fly: Practical Knowledge Management from Leading and Learning Organisations. 2nd Edn. Capstone.

Agilemodeling.com, (2016). Communication on Agile Software Teams. [online] Available at: http://www.agilemodeling.com/essays/communication.htm [Accessed 23 Feb. 2016].

Association for Project Management (2012) APM Body of Knowledge. 6th Edn. Buckinghamshire: Association for Project Management. pp. 52-55.

Back, W. E. 2001. Information management strategies for project managers. Project Management Journal

Boehm, B.W. (1988) A spiral model of software development and enhancement. Computer, 21(5), pp.61-72
Available at: http://www.dimap.ufrn.br/~jair/ES/artigos/SpiralModelBoehm.pdf [Accessed: 24 February, 2016].

Charvat, J. (2002). Project communications: A plan for getting your message across - TechRepublic. [online] TechRepublic. Available at: http://www.techrepublic.com/article/project-communications-a-plan-for-getting-your-message-across/ [Accessed 23 Feb. 2016].

France, R. (2015) Is Agile or waterfall right for you? [Linkedin] 21 January 2015. Available at: https://www.linkedin.com/pulse/agile-waterfall-best-may-well-ask-hammer-drill-roger-fance?trkSplashRedir=true&forceNoSplash=true [Accessed: 23 February, 2015].

Haughey, D. (2009) Traditional system analysis and design. [Online] Available at. (http://www.umsl.edu/~hugheyd/is6840/waterfall.html [Accessed: 21 February, 2016].

Haughey, D. (2015) PRINCE2 Methodology. [Online] Available at: https://www.projectsmart.co.uk/what-is-prince2.php [Accessed: 20 February, 2016].

Hass, K. (2010) The Blending of Traditional and Agile Projects. [Online] Available at: https://www.projectsmart.co.uk/the-blending-of-traditional-and-agile-project-management.php [Accessed: 21 February, 2016].

Hederson, L. S. (2008) The impact of project managers' communication competencies: validation and extension of a research model for virtuality, satisfaction, and productivity on project teams. Project Management Journal 33 (2), 48-59.

Giffin, S. D. 2002. A taxonomy of internet applications for project management communication. Project
Management Journal. 33:32–47.

Ip, W.H., Yung, K.L. and Wang, D. (2004)’ A branch and bound algorithm for sub-contractor selection in agile manufacturing environment’. International Journal of Production Economics. 87(2) pp.195-205 [Online] Available at: http://www.sciencedirect.com.ezproxy.herts.ac.uk/science/article/pii/S0925527303001257 [Accessed:24 February, 2016].

Journyx (2013)Time-BoundCustomerServiceCommunication. [Online] Available. http://www.journyx.com/images/images/group%20communication.JPG [Accessed: 14 February 2013]

Kaltenecker, S. & Hundermark, P. (2014) What are self-organizing teams? [Online] Available at: http://www.infoq.com/articles/what-are-self-organising-teams [Accessed: 23 February, 2016].

Office of Government Commerce (OGC) (2009) Managing Successful Projects with PRINCE2TM. London: The Stationary Office
‍‍Pinto, J. K. (2010) Project Management: Achieving Competitive Advantage. 2nd edn. Pearson Education Inc

PMBOK (2008) "A guide to the Project Management Body of Knowledge" Project Management Institute. 2nd edn [Online] Available at
http://proquest.safaribooksonline.com/9781933890517, [Assessed: 14 February 2013].

PMBOK (2012) Project communication management. Available at: http://www.marajabi.com/PMBOK/Chapter10.pdf [Accessed: 22 February, 2016].

PMI (2011). How to Build a Positive Relationship with Your Project Sponsor | Project Management Institute. [online] Available at: http://www.pmi.org/Learning/how-to-build-a-positive-relationship-with-your-project-sponsor.aspx [Accessed 24 Feb. 2016].

PMI (2012) APM-Agile Project Management. Italy: Project Management Institute Available at: http://www.pmi-nic.org/public/digitallibrary/ProgettandoNW_2012_APM.pdf [Accessed: 22 February, 2016].

PMI (2013) Communication- The message is clear. White Paper. Project Management Institute, Inc. [Online]. Available at: http://www.pmi.org/~/media/PDF/Knowledge%20Center/Communications_whitepaper_v2.ashx (Accessed: 20th February 2016).

PMI (2015) PMI Agile Certified Practitioner (PMI-ACP) Handbook. [Online] Available at: http://www.pmi.org/Certification/~/media/PDF/Certifications/PMI-ACP_Handbook.ashx (Accessed: 20 February, 2016).

PMI (2008) A guide to the project management body of knowledge – PMBoK. 4th edn. Upper Daryby: Project Management Institute.

Project Management Institute (2013) A Guide to the Project Management Body of Knowledge (PMBOK Guide) 5th Edn. Newtown Square: Project Management Institute. pp. 287-291.

Robarts, J.M. (2008) Practical considerations for distributed agile projects. In Agile, 2008. AGILE'08. Conference IEEE. pp. 327-332. Available at: http://www.studynet1.herts.ac.uk/crs/15/7BSP1270-0206.nsf/Teaching+Documents/688793A8242A46CC80257F3D007C9254/$FILE/agile10%20case%20study%205.pdf [Accessed: 24 February, 2016].

Saad, S., Ibrahim, A., Asma, O., Khan, M. S. & Qadir, A. A. (2013) PRINCE2 innovation techniques. Available at: http://cgr.umt.edu.pk/icobm2013/papers/Papers/IC3-Jan-2013-049.pdf [Accessed: 22 February, 2016].

Thomas, D. and Hunt, A., 1999. The Pragmatic Programmer: From Journeyman to Master. Available at:,%20From%20Journeyman%20To%20Master.pdf [Accessed: 24 February, 2016].


External links

Wikipedia entry on this KA
About.com entry on this KA>

Read in another language

<If available, include links to pages with translations to other languages>