Coco - deprecated
The Coco was an attempt to facilitate cross-team communication. A contraction of 'Coordination of communication', it lasted from 2015-10-02 to 2015-12-16. One representative from each team met together to communicate what their team was doing and to try and synchronize with the others. Before this, cross-communication was attempted by large meetings with many members which typically went on for a long time, led to frustration and not much output. Why did it stop? Some reasons;
- Online meetings were difficult to arrange due to contributor availability.
- Conference calling was difficult due to a range of technical issues.
- The goals of the meetings were not particularly clear.
- The distribution of gathered of information was not easily accessible.
- The planned regularity of the meetings was too frequent.
- Representatives brought rigidity: if representative not available, was not clear who - if anyone - should replace them.
Monika and Douglas Webb are trying to develop a solution for cross-team synchronization learning from the experience of the Coco and with inspiration from Scrum of Scrums and other such (2016-05-24).
To the extent possible under law, the yunity wiki contributors have waived all copyright and related or neighboring rights to the content of the yunity wiki. More information...
You have an account but can't edit or create pages? Write us in the open chatroom or in our yunity Slack!