//SEIBERT/MEDIA has been able to gain a wealth of experience in remote collaboration over the years. At Tools4AgileTeams 2019, the team will share these experiences and their knowledge on agile teamwork. The first round of tickets is already on sale.
T4AT 2019 is already rearing its head and our organization team has already taken its first steps: we’ve set the date, organized the new venue, and we’re already taking bookings for early bird tickets. Tools4AgileTeams 2019 will take place on November 21 and 22. You should get your tickets soon: even with our increased capacity this year we’re anticipating another sold-out crowd!
Technical teams in many companies work happily and successfully with Jira – but software that has a reputation for being a development system is not normally something which the Average Joe can also use for their work. When such a person starts working with Jira for the first time, they may be a little overwhelmed by the depth of the system’s many features and functions. Nevertheless, we and many of our customers use Jira with completely different teams and company departments. The advantages of Jira are not limited to just our technical teams. You can clearly see the advantages that Jira brings to all sorts of teams when you focus on its ability to be transparent, its visualizations and how it inspires collaboration rather than technical integration.
Collaboration with partners is an important factor in the continuous development and improvement of our products. Here is a video interview with Brandon Huff from one such partner company, cPrime – a leading Atlassian expert. We talk about our software solution for the implementation of SAFe with Atlassian tools – Agile Hive – its potential from the viewpoint of a US partner, regional differences in scaling agile methods, the importance of comprehensive software integration, among other things.
Now that the era of Hipchat and Stride is at an end, we can reflect upon our transition from these Atlassian solutions to Google Hangouts Chat for group chat and messaging in organizations.
In the previous two posts, I’ve covered the question of why remote work may be a good thing for your company, and who is suited to remote work. Now I want to look at what you need to do to make the introduction of a remote work environment a success.
What does an agile organization with remote teams and only one location need to do to support their teams? What are the hurdles and how can they be overcome effectively? And who is actually suited to be a remote employer or employee? Here are some experiences and my thoughts.
The blog post series considers the everyday obstacles of working in a Scrum team as a remote employee. It provides solutions as well as best practices based on an “ideal” sprint. The second part considers backlog refinement, code reviews, and retrospectives.
The Tools4AgileTeams 2018 conference is just around the corner on the 29-30 November in Wiesbaden, Germany. Thanks to a great selection of presenters, we have now released the session program. We hope you are anticipating a rich, varied T4AT with excellent presentations, great speakers and many ideas for your own teams and companies -it’s going to be a great one!
The blog post series considers the everyday obstacles of working in a Scrum team as a remote employee. It provides solutions as well as best practices based on an “ideal” sprint. The first part looks at sprint planning, stand-ups, and pair programming.