No longer is it a special case for companies and their teams to find themselves in a meeting with participants who aren’t sitting (or standing) in the room with them. It’s critical for clients and stakeholders to be involved in communicating and coordinating with external partners. Teams are often distributed or they have individual team members who work remotely. Since I’m a remote employee who is a part of a local Scrum team at //SEIBERT/MEDIA, I have a lot of experience in this area which I’d like to share with you in this article.
Thanks to the modernization and digitalization of teamwork in enterprises, the organizational and technological obstacles to remote work are lower than ever before. As such, distributed project teams have been commonplace for quite some time now. But old habits are hard to break, and this is most apparent when it comes to meetings. Here we look at common reservations when it comes to video meetings and how to overcome them.
Paul Pasler shares some insights gained at this year’s Scrum Day conference in Stuttgart. From leadership to decision making, the “done” increment to using Scrum for good – the conference certainly delivered plenty of food for thought.
Modern-day working offers many options when it comes to where and how employees work. While flextime and home office certainly have their advantages, they can also present several challenges for employees. Here one of our remote employees at //SEIBERT/MEDIA shares some experiences and tips.
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 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.
How should an agile organization with remote teams and just one site approach the facilitation of distributed work and integration of distributed team members? Here we consider why it is a good idea to take a closer look at this topic, which obstacles can come up along the way and how can you overcome them effectively.
For more than a year now, I have been working for //SEIBERT/MEDIA from home at a distance of about 250km. Can agile software development work like this? Can Scrum processes be maintained, despite the distance? Will I fall out of sync with the team? Right now, I can say yes, it does work!