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 Atlassian User Group
UPD: Rescheduled Jan. 30th -> to Feb. 6th. Recently buddies from Moscow recommended me to join Atlassian User Group Leaders,to host Atlassian events in Ufa, so here I am (after an interview with Atassian)! First ever-ever Atlassian User Group with special Atlassian swag will be happening January 30 2018, 7pm π Meetup related to all … Continue reading Ufa Atlassian User Group
Ufa IT Management Meetup #4
This time it was all about requirements. And we hosted the event at our cozy SkuVault office: Eliciting and preparing requirements from gathering data till development: Oleg Gumerov (PO at SMENA - solutions provider for a big delivery service) shared his experience on how they do it in SMENA.io; Nur Ibragimov (Head Analyst at modulbank) … Continue reading Ufa IT Management Meetup #4
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)
Agile Turkey Summit 2017
Me & my colleague basically decided to attend Agile Greece and Agile Turkey, and then exchange opinions and knowledge gathered there. Big advantage of my trip was Dave Snowden's keynote, whom I wanted to catch after the speech and bore to death with silly questions π Agile Turkey Itself The conference (1-day conference, october 19th) … Continue reading Agile Turkey Summit 2017
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)
RU: ΠΡΠΊΡΡΠ²Π°Π΅ΠΌ Π΄ΠΎΡΠΊΡ Π°ΠΌΠ΅ΡΠΈΠΊΠ°Π½ΡΠΊΠΎΠ³ΠΎ ΡΡΠΈΠ΄ΠΈΡΠ΅ΡΠΊΠΎΠ³ΠΎ Π»ΠΈΡΠ° Π² Π ΠΎΡΡΠΈΠΈ
This post is available in English. Π Π΄Π΅Π»Π°Π΅ΠΌ ΡΡΠΎ Π±Π΅Π· Π½Π΅ΠΎΠ±Ρ ΠΎΠ΄ΠΈΠΌΠΎΡΡΠΈ ΠΏΡΠΈΠ»Π΅ΡΠ° Π² Π Π€ Π°ΠΌΠ΅ΡΠΈΠΊΠ°Π½ΡΠΊΠΎΠ³ΠΎ Π³Π΅Π½Π΄ΠΈΡΠ°. ΠΠΎΡΠ»Π΅Π΄Π½ΠΈΠ΅ ΠΏΠΎΠ»Π³ΠΎΠ΄Π° Ρ Π½Π°Π±ΠΈΠ²Π°Π» ΡΠΈΡΠΊΠΈ, Ρ ΠΎΠ΄Ρ ΠΏΠΎ ΠΈΠ½ΡΡΠ°Π½ΡΠΈΡΠΌ, ΡΠΎΠ±ΡΡΠ²Π΅Π½Π½ΠΎ, ΠΏΠΎΠ΄Π΅Π»ΡΡΡ ΠΎΠΏΡΡΠΎΠΌ π ΠΠ°Π΄Π°ΡΠ°: ΠΎΡΠΊΡΡΡΡ 100-ΠΏΡΠΎΡΠ΅Π½ΡΠ½ΡΡ Π΄ΠΎΡΠΊΡ Π² Π ΠΎΡΡΠΈΠΈ (ΠΌΠ°ΡΠ΅ΡΠΈΠ½ΡΠΊΠ°Ρ SkuVault.com Π½Π°Ρ ΠΎΠ΄ΠΈΡΡΡ Π² ΠΡΠΈΡΠ²ΠΈΠ»Π»Π΅, ΠΠ΅Π½ΡΡΠΊΠΊΠΈ). ΠΠ°Ρ ΡΠ»ΡΡΠ°ΠΉ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ ΡΠ½ΠΈΠΊΠ°Π»Π΅Π½: CEO Π½Π΅ ΠΌΠΎΠ³ ΠΏΠΎΡΠ΅ΡΠΈΡΡ Π Π€, ΡΠ°ΠΊ ΡΡΠΎ Π·Π°Π²Π΅ΡΡΡΡ ΠΈ ΠΏΠ΅ΡΠ΅ΡΡΠ»Π°ΡΡ ΠΈΠ΄Π΅Π½ΡΠΈΡΠΈΠΊΠ°ΡΠΈΠΎΠ½Π½ΡΠ΅ … Continue reading RU: ΠΡΠΊΡΡΠ²Π°Π΅ΠΌ Π΄ΠΎΡΠΊΡ Π°ΠΌΠ΅ΡΠΈΠΊΠ°Π½ΡΠΊΠΎΠ³ΠΎ ΡΡΠΈΠ΄ΠΈΡΠ΅ΡΠΊΠΎΠ³ΠΎ Π»ΠΈΡΠ° Π² Π ΠΎΡΡΠΈΠΈ
Workflow for the Requirements in the Distributed team
How to ensure that requests from different sources become formalized and clear requirements, and address communication, clear interpretation, accountability and transparency.
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 … Continue reading Why we ditched Scrum in favor of Kanban in JIRA
Jira: how to allow editing fields for closed tickets
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 … Continue reading Jira: how to allow editing fields for closed tickets