The retrospective is one of 12 principles outlined in the Agile Manifesto. If this is easy to do this for collocated Scrum teams, how can you achieve good results if you have remote members. In this blog post, Robert Matheson provides a valuable collaborative retrospective technique that can be used for distributed Scrum teams.
In large Agile projects where a Scrum team cannot deliver the full system, you have different options to organize your team. You can use feature teams that work on a set of user stories or component teams that work on a subsystem or component. In his blog post, Michael Valenta reports his experience as a ScrumMaster from the usage of features teams.
There are as many assumptions and misconceptions about global development as there are about agile development. In this article, Jutta Eckstein tries to remove these misconceptions and explain how Agile can be implemented and provide benefits in distributed software development projects.
Distributing Scrum projects isn’t easy. Agile values encourage face-to-face communication and frequent feedback between team members. But for those who seek the benefits of Agile – frequent releases, less waste, high emphasis on value – on larger, more complex projects, this video presents some technical practices that help retain the spirit of co-location in a distributed environment.
In this blog post, J.D. Meier shares his experience of leading high-performance distributed teams for more than ten years at Microsoft. He describes a weekly schedule that begins with identifying 3 wins for the week on Monday to discussing 3 things going well and 3 things to improve on Friday.
“Swarming” is a technique whereby many members of a Scrum team work together to deliver a User Story, taking advantage of the skills of many team members together. In this article, Johanna Rothman asks the question: How do you do swarming in a distributed team?
The early agile literature was adamant about two things: stick with small teams and put everyone in one room. However, in the years since the Agile Manifesto, the increasing popularity of agile and the dramatic improvements it brings has pushed it onto larger and larger projects. Additionally, having an entire team, especially on a large project, in one room, or even one building is a luxury no longer enjoyed by many projects.