Articles and tutorials on distributed management of Agile projects and Scrum software development teams.
Curious about how to build and sustain a remote-first culture? In this presentation, Rachel Davis explains how her team at Tes adapted their engineering practices to support small teams working in close collaboration over distance. With more engineers working from home or travelling than sitting at a desk in the London office, this talk covers how she organizes cross-team initiatives to sustain this way of working.
As countries navigate the impact of widespread Coronavirus, balancing the health and well-being of employees and Scrum teams with the very real need to keep business functions operating is particularly top of mind for companies large and small. This presentation helps you develop the mindset needed to align remote employees and coordinate multiple Agile teams. Learn how Scrum events coordinate and focus communication, foster transparency and get work to Done.
Reetro is an online agile retrospective tool. It simplifies the process of planning, managing and executing retrospectives for Scrum teams. Reetro offers a variety of features from very simple user experience, automation and analytics.
Its increasingly common that Agile software development teams are distributed across multiple offices, in different countries, all working remotely on the same product or project. But how do you make this work well? There seem to be a number of readily accepted tenants of conventional wisdom to help deal with leading distributed teams, from seeming good ideas “teams must be co-located” to ones that are purely economic “offshore teams can be run at a far lower cost”.
As Agile practitioners, we’ve learned to love highly cohesive, cross-functional on-site teams. These teams, much like monolithic applications; succeed due to the proximity of useful knowledge. Distributed Scrum teams must rely on different strategies and tactics in order to be effective while still adhering to the principles laid out in the Agile Manifesto.
Pair programming is one of the original practice of eXtreme programming, but it is also one of the least used by Agile software development teams. In his blog post, Alisdair McDiarmid explains how Customer.io uses pair programming with remote teams.
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.
Scrum Expert Copyright © 2009-2026 Martinig & Associates