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!
The paper-less office was meant to banish all paper from the office. In agile teams, however, this does not apply and this is where InstaPrinta comes in. Admittedly, a tool like Atlassian’s JIRA is a great way to manage tasks. However, in day-to-day work, a digital Agile Board in JIRA does not have the same presence as a large magnet board right in the center a team office that is full of task notes. At a glance, every team member knows what needs to be done and who is working on what. Furthermore, the magnet board contains numerous additional sections like an improvement board, a skill matrix, an absence calendar and more. This makes the analog board the central “cockpit” for all information relevant to the teams.