Communication

Why

In the work we do at Kabisa, you are never a one-man-army. You work with colleagues and customers. You need to communicate to work together. Also, your work is important for the customer, so keep them posted, whether it goes as expected or not.

How

  • Agree on preferred ways of communicating with the team
  • Actively participate in the Daily Standup
  • Be proactive: don’t let issues wait for the standup
  • Sit together as a team and use Slack if that is not possible
  • Be aware that people can’t see what you are thinking, you have to tell them
  • Be aware that what you think is obvious, isn’t obvious for everyone. So say it.
  • Whenever you think “Should I let this know to … ?”, the answer is “Yes”

Real Life Example

In a small project (with only one Kabisa developer), the developer and the Product Owner made a plan (yesterday) that the developer would finish a story this morning and deploy it to the test environment. The Product Owner would then test it in the afternoon. Early in the morning, the developer finds out that the Kabisa developer who reviews his code, is not available before 12:00h. The developer immediately communicates to the Product Owner that the test can probably not be done before 14:00h. (assuming the review will require him to make some changes and re-run some tests). The Product Owner is able to reschedule a meeting from later in the afternoon to 13:00h, thus making him available to perform the test from 14:00h. The story went live that same day, which made a number of customers very happy. Had the developer not communicated immediately, it is likely the PO got disappointed and was not able to reschedule and test. As a result the customers would have been disappointed.