Posts

Over the past 2 years, I’ve been working as Program Management lead at Metamap.com, helping to set up OKR framework among other things. As challenging as just working with OKRs is, we are a distributed team, spanning from PH / SG to the very west coast and even Hawaii :) The common issues we’ve found and discovered led me to creating this blog post. So without further ado, It’s time to delve into the captivating world of OKRs - Objectives and Key Results. These are the guiding stars that lead your organization to its true north. Embarking on this journey can sometimes make you feel like you’re treading choppy waters. In today’s post, we’ll chart a map of these common pitfalls and equip you with an Agile compass to help navigate with confidence. ...

Hey everyone, here’s my list of resources and literature for getting prepped for the PSM II examination. I would be tremendously happy if you share yours :) *Sidenote: if you are “certificates are overvalued” type of person - I’d agree. This is especially true when it comes to CSM / PSM I - because that certification only mentions that you have been introduced to the basics. However, when it comes to PSM II you need to rely on your experience as a Scrum Master. No more “shu” (of shu-ha-ri), just your experience and daily understanding of agile values. * ...

Last week me and Alex Pikulev of Agilix recorded Trust Stories podcast episode, on Growing Team Trust in Distributed Teams. Courtesy of In Teams we Trust website https://www.youtube.com/watch?v=Pq82aFap1rc Main bullets are: Growing trust in distrubited teams is hard, but nevertheless as important as in co-located team. Team itself creates an atmosphere of trust in itself. Our task, as a scrum master, coach, manager - is to help and highlight needed areas. XP and especially Pair Programmingи helps in growing trust. Intrateam trust, from the informal side (skype beers, navigating as a guest to your colleagues in other locations, bike fixing via the webcam, ordering stuff on flea market in your city and sending it over to a colleague) helps a lot. More freedom for the team, for collaborative work and motivation. More trust! Work harder on understanding the context and value of features implemented. More details (rus) / tg channel : https://t.me/inteamwetrust_rus/35 Video: https://youtu.be/Pq82aFap1rc

Navigate to Personal Settings- Turn switcher for Jira Labs off- And leave feedback. Atlassian team needs you to help’em understand what didn’t you like. Ahem, I got some help :)It’s not comfortable to edit- It doesn’t support markup- It doesn’t allow to work with resolutions- It makes it hard to find needed fields, although they are already turned on in standard view Are you finding new view comfortable? Has it helped you improve your Jira routines?

and why Trello? Lately I’ve started using Trello as an ultimate tool for the Retros and Demos. So this post will cover the path to using trello as opposed to other solutions. yet another pencil illustration Tools I’ve been using multiple tools, such as Realtimeboard (now Miro) as an interactive flipchart to collaborate with the team, Google Docs with sections appointed to the retro stages, Confluence (as in 100% of the projects I’ve been working in we’ve had Atlassian stack), even Jira once (wow that was a bad idea)! ...

This is an interesting case I always wanted to make better: almost every project you come to has a lot of older unreleased tickets, that actually already sit on production. And developers (without proper jira management) continue using the Kanban board that becomes more crowded in the Done / Closed column (and it can hit 400, 1000 tickets and be slow and almost pointless to use). Typical story, huh? So what to do, if you want to release all those older tickets and don’t bother developers with, say, 450 updates on every ticket that fixVersion has been set to each one of them? The answer (and thanks to AUG Moscow Community) is to swap notification scheme for related projects while releasing. ...

So we’ve been measuring story points estimate and throughput through the last 5 sprints, and they really do show approximately similar results :) makes you think why do have an additional story points layer on top of the simple throughput? :) Just as Vasco Duarte told :)

It’s been an extremely fruitful Atlassian Summit 2018 in Barcelona! Main purpose was to speak about Distributed Teams, however the atmosphere was so cheerful and friendly, that it was more like a fireside chat, even given that my speech was the closing one. https://www.youtube.com/watch?v=yFDtxT5-5MM Got an awesome tracklead! Brought a giant bag of Atlassian merch for AUG events in Ufa, thanks Darlene! Finally met Ben Linders (check out his Agile Self-Assesment game!) whom I’ve been giving a Q&A to (which is now available in Japanese and Chinese). ...

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 help to communicate and synchronize work. Teams based on trust, respect, and openness will thenselves to help people throughout the organization and foster a culture that keeps teams in sync. ...

Stride is being discontinued as of Feb 2019, and Atlassian itself moves to Slack. It was quite hard to use Stride as the speed of the electron package was painful, integrations were worse than in Slack (even with Atlassian products), stability and features were suffering quite heavily. It’s great that a team can admit it’s pain points, since it’s almost impossible to compete with de-facto industry standard ‘Slack’. I’ve written about experience of 6 months on Stride, we’ll jump off it, I presume, closer to the end of product support.