My Q&A for InfoQ on Keeping Distributed Teams in Sync

I spoke with Ben Linders of InfoQ (thrilled to be published at that website!) about challenges and communication patterns for Distributed Teams, uncovering bits of my Atlassian Summit 2018 speech. The biggest challenge of distributed teams is communication, which is essential for establishing ground rules on collaboration. Shifting working hours to accommodate each other and team liaisons … Continue reading My Q&A for InfoQ on Keeping Distributed Teams in Sync

Agile Communication in Distributed Teams (with no overlapping hours)

So as you know my speciality is distributed teams 🙂 This post is about what changes does the agile communication face (and scrum in particular), when it's adjusted to the distributed teams. This is my experience, I don't assume this is a silver bullet, but such approach works for me for the last 5 years … Continue reading Agile Communication in Distributed Teams (with no overlapping hours)

Ufa IT Management Meetup (24.10.17)

2 weeks after we had the actual meetup, here's the follow-up post 🙂 Topics this time: Keynote by me on cynefin and how it fits our company projects. Had some discussion & arguing on applicacy of cynefin when it comes to rough development times, migrations, firefighting-based development. Overall, model was introduced, and the fact-and-experience-based arguments … Continue reading Ufa IT Management Meetup (24.10.17)

Jira: removing transition from current status to itself (if All -> transition is turned on)

Small and duct-tapey resolution for the time, when you have an All -> [statusName] JIRA workflow transition. By default, it results in the following: Default Ticket Screen shows transition from current to current status, among others. So e.g., you have an In Progress ticket, you have the transition to the very same In Progress. To … Continue reading Jira: removing transition from current status to itself (if All -> transition is turned on)