‘Agile’ is an incredibly powerful software development methodology, however the word ‘agile’ has become one of those IT buzzwords that people use but do not fully understand.
The Agile Manifesto says that “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation”, but many meetings are a dull waste of time, even for Scrum teams.
Sprint retrospectives are an important tool for Agile software development teams that want to implement continuous improvement and adjustment to their working context. In this article, Jesus Mendez provides some techniques that could help improving the outcome of your Sprint retrospectives.
The first value of the Agile Manifesto is ” Individuals and interactions over processes and tools”. Its third value is “Customer collaboration over contract negotiation”. In his book “Agile Analytics”, Ken Collier discusses the concepts of cooperation and collaboration in Agile.
This highly-interactive talk shows typical communication patterns and behaviors in Agile teams. It also provides eye-opening insights into the ways communication can be improved in Scrum. It features some practical games that include the whole audience.
This article focuses on the obstacles to using Agile in a distributed team environment and recommends how to counter them with what is called “de-Agile.” De-Agile is tailoring Agile to fit your team by taking out processes that don’t make sense and tweaking those that need to be modified to suit your needs. In a distributed team environment, de-Agile is mostly about removing the sense of being distributed. You need to educate each team member about the additional communication responsibilities required when working with remote team members and emphasize the importance of being open and available.
The Dialogue Sheet is a new technique for team retrospectives in Scrum Projects. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.