//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.
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.
In order to avoid misunderstandings, I’d like to explain what happens in Scrum meetings, why they are important for the project, and what the customer gets out of them.
Before employer and employee begin the task of developing new software, it is important that both parties have a clear understanding of the end goal. A “requirements workshop” provides the opportunity to define the project’s goals, as well as the individual steps necessary for their completion.
Agile methodologies encourage teamwork, accountability, and open communication. They motivate business stakeholders and developers to work together to align the product with customer requirements and company expectations. But what really is Agile, and how does Scrum fit into the picture?
As Agile Coaches, we also work as intensively as possible at the level of teams and individuals – that is, the actual job of Scrum Masters. In this final post I will show what we are doing here in more definite terms.