Posts

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 avoid that, use simple conditioning for the transition: - Go to transition Conditions - Click Add New - Select 'Value Field' from the given list - Select logical operator 'doesn't equal' / '!=' - And put a value in it (name of current status, and the value to be handled as string) Start Working is the transition name to the “In Progress” status This is how it looks in Workflow ...

This is basically the anatomy of a distributed team, working on requirements. Key point here is that this is the process working for us, in current configuration, and it’s effective. Disclaimer: Every organization is different: from internal structure to how it communicates with the outer world. So no workflow is a silver bullet. *Disclaimer 2: SkuVault is an ever-improving team of ~50 people, distributed across 10 timezones, 2 different versions, and serving loyal clients worldwide 24/7. Learn more about Communication in distributed teams: Messenger & Rules, or *Why we ditched Scrum, in favor of Kanban in JIRA ...

Warning: don’t misinterpret scrum for agile as a whole :) Around a year ago I wrote a yearly retrospect on how the workflow at SkuVault is organized, and how we set up our jira boards to work in sprints. sprints and their goals There was no Kanban backlog at the moment, and we used Scrum board as an improvized scrumban tool: we had the sprints, which were treated as folders to fit tickets in some time period. Classical sprints were not suitable for our workflow, I mentioned the reasons in Year Retrospective @ SkuVault. So that sprint-folder system was great, visible and allowed us to predict. ...

Jira is flexible, yet complex tool in some cases :) - In order to make the fields (inline as well) editable, when the ticket is closed, go to Workflow -> Select 'Closed' status -> Click Properties - There would be flags with bool values: we need jira.issue.editable -  - In case you see jira.issue.editable is false - either change that to true or delete the property key with prev. value. - Don't forget to publish the updated workflow.

This post is available in Russian. *And do it without the CEO flying all the way down to your city :) * Let me share a bit of an experience from past 6 months :) We wanted to open a branch in Russia (parent company is in US). Our case is a bit unique: our CEO wasn’t able to visit Russia, so we had to verify and send the list of docs back’n’forth between two continents. ...

In order for the distrubited teams to work, you got to have a clear flow, a set of general rules, that will fence the process and allow people to collaborate effectively around the globe. If everything is set up correctly, you are able to create amazing products with global professionals, and cover customer support 20+ hours a day. Communication What do you miss most when working outside of the office? Procrastination! ...

So it happened - I managed to gather 2 people for PM & BA meetup (without any PR xD). After visiting Vienna, I desperately wanted a platform to share knowledge or / and mock each other on PM & BA failures. So I created one: Ufa Project Management & Business Analysis Group Initial meeting consisted of Me, Nur (from modulbank.ru - online bank for small businesses) and Oleg (from smena.io - various crms / solutions for partners). Both work as analysts at cool and interesting teams. ...

Recently my colleague, Tim, decided to try out Planning Poker, to have better estimations. Planning is essential, and scrum already offers a framework of how to deal with planning. But over the course of my work and experience with scrum techniques, team usually shapes Previous experience showed that daily scrum meetings are merely pointless. Direct communication / skype / IM is much more efficient. Especially in distributes teams. And following each and every ritual from scrum routine is time and efficiency consuming during the first iterations, since agile methodologies need a good deal of instructions. Usually, after some time teams shape up scrum as they want, and it just works, so from my experience it’s not essential to follow scrum by the book (Agile Estimating and Planning book by Mike Cohn, written 10 years ago). Here are additional thoughts on why our transatlantic distributed team doesn’t fully fit into planning classic scrum and it’s rituals: ...

Last year guys from SkuVault offered me an amazing opportunity to help the company manage a growing development team, create organized schedule, establish workflow that reflects the company goals . For those who don’t know - SkuVault is a Warehouse Management System (WMS). Like a swiss army knife, SkuVault manages and syncs your inventory across e-Commerce platforms, POS, Logistics and Warehouses, providing accurate quantities in order to prevent out of stocks. Headquartered in Louisville, KY - SkuVault helps to manage the inventory for hundreds of clients all across the globe. ...

I’ve recently been to Vienna, and visited local Austrian Startups Stammtisch. It went by the number #31, so quite a consistent event going on for more than a year now. The event took place in Sektor5 co-working space (which I have to recommend, because it’s a really cool place with only eur 18 per day! You can feel the international vibe and all that kinds of stuff). Sektor 5 got a cool terrace :) ...