Who do I need to communicate with most often?

[suchona.kani.z]

If our team does not exceed the recommended size of eight to ten people, we only need to ensure efficient scheduling, preparation and implementation. Agile principles such as personal responsibility, self-organization, the pull principle and time boxing are crucial in this regard. In addition, well-maintained sprint/product backlogs or Kanban boards are just as important as a transparent agenda that is accepted by all. Yes, in my opinion agile meetings should also have an agenda, even if it sometimes seems trivial. A few useful tools such as Jira, Confluence, Webex, Teams or physical Kanban boards are also helpful, at least if they are used correctly and carefully and work reliably. If we then regularly hold valuable retrospectives, we can continuously improve.

Efficiency improvements can be achieved by shifting appointments to off-peak times. For example, meetings can be scheduled in the morning, immediately before or after lunch, or before the end of the working day. However, you should ensure that there are sufficient breaks between meetings. You should also consider holding meetings related to a sprint change on one day instead of spreading them out over several days.

What should be considered with caution, however, are supposed poland consumer email list efficiency gains by extending the frequency of regular meetings (e.g. every two weeks instead of every week). This usually not only increases the length of the meetings. In addition, the problem often arises that the clarification of important questions is then postponed for too long, effectively requiring more time to clarify them. This is why we now use dailies instead of the previously usual regular meetings and prefer agile sprints of two to four weeks instead of dividing traditional large-scale projects into just a few partial deliveries.

As a rule, it is therefore advisable to schedule such regular meetings for a shorter period of time but more frequently. If there are no topics to discuss, the general rule is that an appointment can of course be cancelled at short notice.

communication at the control level
Agile teams rarely work completely independently of one another. They usually work in parallel with other agile teams on similar or complementary products. Effective collaboration must be coordinated by a control level. This is an essential part of any agile scaling.