Sabina Grcic
11 articles
June 11, 2020
Culture
Well, that escalated quickly – #putuj387
Background story Here are three things that we had in mind before starting our putuj387 (travel387) story: First: COVID-19 pandemic canceled all of our international travel plans and limited us inside our national borders. Second: Bosnia and Herzegovina has dozens of breath-taking locations worth visiting that are not so popular among the wider public. Third: Social media usage increased 44% globally. So Bosnians and Herzegovinians cannot travel abroad, but they live in a beautiful country and use social media more than before? Hmmm. Atlantbh has always been our country's #1 fan, supporting everything from sports, education, technology, to the IT industry as a whole. We know that Bosnia and Herzegovina has so much potential in almost every field and we are always ready to help turn that potential into performance. So when the COVID-19 pandemic hit and many areas of our society were affected, we realized that we needed to back an industry which was arguably most vulnerable - our tourism industry. It initially began as an internal project. On our Slack channels, we began encouraging our Atlanters to plan trips around the country to support domestic tourism once measures were eased. We promoted domestic tourism sites - from the most well known to hidden gems. Then we realized that this initiative needed to be more widespread, we needed everyone to get involved, from sharing their favorite tourist destinations in the country to spreading the word far beyond our office. What better way to do this than by creating a social media challenge for everyone to get involved. That is how putuj387 was born. The escalation It all started our first Facebook post that you see below. We photoshopped Atlanters at the National Park Sutjeska and explained our idea. It was a very simple one - post a real or photoshopped image of you from somewhere in Bosnia and Herzegovina, use the #putuj387 hashtag, and tag your friends to do the same. Oh, and we encouraged the use of less popular destinations, like someplace other than Sarajevo's Baščaršija or the Old Bridge in Mostar, because let's face it everybody knows about those and we need to explore more. https://www.facebook.com/AtlantBH/photos/a.235777106461634/2972012249504759/?type=3&theater We tagged our colleagues from the industry and they liked the idea so much that they supported it immediately, challenging more and more companies to do the same. In the upcoming days, our followers also began participating in the challenge and they joined the ranks of international ambassadors, influencers, and even famous Bosnian and Herzegovinan athletes such as Edin Džeko, Džanan Musa, and Jusuf Nurkić. https://twitter.com/EdDzeko/status/1262440296559906818?s=20 At this time, there are thousands of pictures and posts using the #putuj387 hashtag across Facebook, Instagram, Twitter, and even LinkedIn. National media recognized our efforts as well and we discussed the campaign and idea with many news websites, TV, and radio stations. Butterfly effect for good We are ecstatic that we gave contributed to our country's tourism and helped, at least a little, in the popularization of all the magnificent locations our country has to offer, such as; Lukomir village, Japodski islands, the sand pyramids near Foča, the arch known as "Hajdučka vrata" on Čvrsnica mountain and a lot more. We are also very thankful for everyone who took part in this challenge, all the companies, organizations, and individuals. Together, with a single post and a lot of creativity, we rediscovered the jewels of our tourism and we are looking forward to visiting all of them this summer!
May 18, 2020
News
ABH Online Meetups: Dev, DA & QA
Almost a full two months of coronavirus pandemic are behind us. We reorganized our system, completely switched to Work From Home (WFH) mode, and learned how to make things look easy from the comfort of our homes. (more…)
February 5, 2020
Culture
Sharing the Instagrammable workplace culture of IT companies
Plain work days from 9 until 5, boring work outfits you have to wear every day, the exact time for lunch breaks, strict hierarchical structure, bosses that count your hours and all the other boring stuff… (more…)
November 8, 2019
Giving Back
News
Atlantbh supports young athletes
Bosnia and Herzegovina has many great ambassadors all around the world. A set of people who are giving their all to show that we are capable of the biggest achievements, even if we're a small country. (more…)
October 11, 2019
News
We created the perfect role-play for future programmers
According to Atlanters, the enthusiasm and energy of students just beginning their careers in IT, is a source of inspiration. The excitement they feel about the fastest growing industry (more…)
July 12, 2019
Giving Back
News
Charity hand in hand with going green
We, as a company, are trying to become the change we want to see in the world and that is the reason why we have been investing in our ABH Goes Green campaign for the past few months. As part of the campaign, (more…)
June 14, 2019
Giving Back
News
Atlantbh supports children in the community
At Atlantbh, we not only decided to celebrate International Children’s Day (June 1st), we decided to make it a week-long event full of activities. The first of our many activities organized for Atlantbh’s little humans was an art exhibition. (more…)
April 30, 2019
Giving Back
News
Atlantbh supports IT education
As leaders in our industry, we recognise the potential of the IT industry and the opportunities it can provide youth. This is why we are always eager to help our local communities by supporting various activities, including IT education. (more…)
February 9, 2018
Product Management
6 Steps for more effective retrospective meetings
If you follow Scrum (or agile) practices, the term “retrospective meeting” should be familiar to you. The Scrum Guide, defines retrospective as “an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.” Despite retrospectives being a necessity, according to the Scrum Guide, some Scrum Teams might consider skipping it or doing very short retrospectives instead in order to adhere to the guide, inevitably lacking any clear goal. However, the retrospective meeting is a very important part of the process, if you aim to have long-term processes that are stable. Also, if a team doesn’t work by Scrum, adding scheduled periodic meetings, such as retrospectives, will ensure benefits. This meeting is where you can very easily discover potential problems with your processes at the very beginning, make a platform for honest peer feedback between your team members and focus on improvements that are most desirable within your team. If the team doesn’t understand how it can gain these benefits from the retrospective meeting, below are a few steps a Scrum Master (or another person in charge of holding retrospectives), could take to ensure that the meeting will be effective and productive. Schedule a time-boxed and timely retrospective A retrospective is a kind of informal meeting and it is a given that people will want to talk about a bunch of topics that are not relevant for the final outcome. This shouldn't be suppressed, but time-boxing will ensure that a natural tendency for focusing on more important topics, is channelled. Also, scheduling a retrospective immediately after a certain amount of work has been finished (Sprint) and right before you start with next iteration, is very important, as it emphasises what a retrospective is about, and enables the team to plan for the next iteration - especially the improvements they wish to make. Each person in the team must have a chance to talk It's important having diversity in the team, but in most cases, it means that there are some very loud and some very shy people. Retrospectives where only the former group talks, are likely to end up with a partially good conclusion. If all team members are not interested in participating, the coordinator should find a way to give them an opportunity to voice their opinions, as well as ask them for their thoughts. Speak in a positive tone Different teams could ask themselves different questions, but eventually these questions should be possible to group into "achievements" and "wishes". In other words, conversation on retrospective is always about improvements and never about blaming. Instead of asking "what the team didn't manage to accomplish in the last iteration", it's better to discuss it in terms of "what the team would have hoped to have accomplished". Select improvements that are the most feasible The ultimate outcome from the retrospective should be the next few steps the team will take in the next iteration in order to improve its processes. Some team's "wishes" could be very popular among the team, but unfortunately, far-fetched. If the goal seems impossible to achieve by the next retrospective, try to divide it into a set of steps and take only the first steps the team can realistically accomplish. Dedicate person(s) that will work on the next steps If a team decides on the type of improvement they want to implement, what should also be decided on, is who is responsible for leading it. If it were to be left at everyone's will, there is a very good chance that nobody will feel responsible enough to take the first step. Also, if it's not possible to decide on who would be given this responsibility, it probably means that it's not clear enough as to what has to be done. Start the new retrospective with a throwback on the previous one Even if the retrospective is very successful with the obvious final outcome, the team may feel like there is no benefit. The reason could be the lack of reflection to things the team decided to improve on, in the last retrospective. This way, if everything goes smooth, the team will know that the retrospective helped them stay on the right track. If not, this implies that there is a need for some sort of change in order to make the retrospective more effective. Conclusion: Even if the team follows all of the good practices and tips written above, it doesn't mean that the team's retrospective will be successful. Each team has a different dynamic and different individuals, therefore the organisation of each event and meeting, should to be adjusted to the team's needs. It's up to the meeting coordinator (in most cases, it'll be the Scrum Master) to find a way to engage all of the team members and use the retrospective for helping the team to inspect and improve themselves, not to be stuck at a standstill, with a lot of unrealised "wishes".
Ready to Achieve More?
We’ll help you reach your goals quickly with an easy and straightforward process to kick off our collaboration. Here’s what happens next.