...
- identifying resources and skills sets and reaching out, asking questions
- knowing what each other is doing on a daily basis
- cross training
- listening (and some times not listening when appropriate)
- filtering information as it comes down (when is it too much info and when is it not enough?)
- making sure you cover the WHY (often not communicated at lower levels)
- getting buy-in
- asking for input
Ideas on what to include in a communication strategy:
- objectives
- target audience or stakeholders (internal and external)
- message you want to convey THE WHAT
- rationale THE WHY
- tools (existing and new) THE HOW
- resources you need
- time line THE WHEN (frequency)
- lessons learned
Tools Tools we use:
- daily vs weekly vs bi-weekly meetings
- rotating who has responsibility for the agenda
- IM
- Daptiv
- Jira
- RT
- Tech Time
- Phone
...
Team X has been working on a login an application and the big release is coming up. Many of the company's applications will integrate with this service and be dependent on it. The Team makes the decision that the product needs to be "rock solid", because if it goes down, so do all the apps that are using it. The company as a whole does not do any standard quality assurance, and the Team believes that this is an issue. They feel that due diligence includes QA for this service as well as other products being developed across the organization. They want to begin investigating tools since testing would need to begin asap. How should their needs and concerns be communicated? How should the tool selection be conducted and a decision made?
...