As a facilitator, every retrospective is like a coffee—with the right blend of technique and creativity it will be as good as you make it. Doing preparation prior to a retrospective is crucial to its success and ensuring that the team sees value, resulting in a more engaged group.
As a technology consultancy with flexible work practices, we’re well versed in this way of working. So, we wanted to share some tips and tricks for how we work remotely with our clients. We spoke with Bryan Signey and Danilo Lo Santo, two of our Sydney based Software Engineers, about their experience working on a remote client project.
In September last year, I began working remotely with DiUS from Perth. I had previously worked from home on the occasion, but working remotely day in day out is a different story.
Think of the last time you were involved in kicking off a new project. How was the experience of getting everyone aligned around the vision and started on the actual work? Was it smooth and quick, or did you encounter some bumps along the way?
For the last few years I’ve been working remotely from Tokyo, with only short trips back to Melbourne to visit clients and catch up with colleagues. Working remotely has its fair share of challenges (and benefits), and being a technical lead for a team while remote can add a few more to both lists.
Celebrating International Women’s Day this year was bittersweet. It’s wonderful to be part of an event that’s so widely adopted. It’s an occasion to talk up all the wonderful women we know and work with—and goodness me there are many—to raise awareness of how far we still have to go in workforce gender equality, and talk about how to get there. But it’s also a reminder that it’s 2020 and we still live in a world without equality, not just in gender.
Our very own Sadia Mir – Principal XD Consultant and Digital Strategist – took the stage last month, alongside Australia’s top women in tech to explore both sides of the ethics coin.
I had plans of becoming England’s football captain. I haven’t given up on this goal, but plan B would be to be doing what I am doing now. So you could say I’m living the dream.
It seems more README’s are being created and shared by the day. So is it just a fad or should all managers write one of these? A README is a user manual written by managers on their management style, philosophies, expectations, communication preferences, and more. Think of it like a how to guide for getting to know and working for your boss.
When you are editing digital music, if you move something even 5 milliseconds, you can totally hear it. The music is no longer working – things are out of whack. When you translate that to a team or an organisation, it’s about creating conditions where people can get in tune with what is going on for that group of people