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.
The third major sphere of responsibilities assigned to our Agile Coaches at the company level, is corporate development. This includes many activities which aim to enable //SEIBERT/MEDIA to continue to grow, to continue developing and, above all, to react to changing conditions.
We want to use our capabilities and strengths to achieve the greatest positive impact on our company and add value to our teams. Our work has moved more and more from the team level to the corporate level. As Agile Coaches, company training and further education is important. But first, here is some food for thought at a more abstract level.
The Scrum development framework assigns a entire series of very specific tasks and responsibilities to the Scrum Master within a team. However, in many companies the Scrum Masters do something quite different. Our colleagues always ask us what we actually do. To answer these questions, I have written a series of blog posts.
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!
Codeyard is our new product suite, specially developed for companies planning larger or very large software projects. It is a product suite of software programs and expert services, which provide both the technical and procedural infrastructure necessary to achieve a seamless and structured development workflow. We offer Codeyard as a professional and powerful solution for quickly setting up and integrating a tailored, effective and efficient software development process, from concept to delivered product.