Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Build or enhance communication plan which will define points of interaction between teams in order to solve common issues and resolve open questions, e.g. setup regular meetings or create communication channels or setup process via Atlassian JIRA requests from one team to another oneCreate simple RACI matrix with key people involved in backlog management, or interested in it - management plan which should include:
    1. Stakeholder communication requirements;
    2. Information to be communicated, including language, format, content, and level of detail;
    3. Escalation processes;
    4. Timeframe and frequency for the distribution of required information and receipt of acknowledgment or response, if applicable;
    5. Person responsible for communicating the information;
    6. Person or groups who will receive the information, including information about their needs, requirements, and expectations;
    7. Methods or technologies used to convey the information, such as memos, email, press releases, or social media;
    8. Resources allocated for communication activities, including time and budget;
    9. Glossary of common terminology;
    10. Flow charts of the information flow in the project, workflows with possible sequence of authorization, list of reports, meeting plans, etc.; and
  2. Create simple RACI matrix, define clear roles and responsibilities for each and any activity (like who owns priorities, who and when puts estimates, etc)
  3. Establish communication process, i.e. how new requests including ad-hoc ones are communicated /delivered to development team, what phases are in demand intake flow, what are the requirements (DoR) for idea to be taken into sprint backlog
  4. Make communication to the client, team and other stakeholders about time leakage from sprint, sprint rules of working on committed scope or applying change management in case of any updates/urgent requests. Establish practice when all incoming requests of not planned but urgent scope during active sprint go to Scrum Master as the first instance of review, evaluation and further steps undertaking
  5. Make proper communication to the client and other stakeholders about rules of adding or removing tickets from the Sprintapproach with events, their goals, frequency, target audience, etc


Note
titleRemember

Communication works when right information coming at right time using the right method.


Useful materials