Chapter 94. How We Used Scrum to Work with an External Agency
Eric Naiburg
People often say that Scrum Teams must be co-located or that they must all work for the same company. That, however, is not the case. Scrum serves to solve complex problems. Working on a distributed team with people from multiple companies even increases complexity and thus the value of Scrum.
Delivering a new Scrum.org website required us to bring together knowledge and talent from multiple places. Beyond looking for an agency that had expertise in the envisioned technology, we wanted a partner willing to work with Scrum. Obviously.
But paying a little attention to our working conditions, beyond the mere rules of Scrum, helped a lot.
When negotiating a contractual agreement with the selected agency, we did not want to get locked into some 18-month project, up front, without the ability to evolve and learn as we progressed. We did, however, understand the agency’s need for some security. We easily found middle ground in agreeing to purchase a number of Sprints with the option of extending or canceling upon a four-week notice (one to two Sprints) at any time.
Our Scrum Team was cross-functional as well as cross-organizational. It was made up of a Product Owner from Scrum.org, a Scrum Master from the agency, and a Development Team that included people from both. Having developers from both sides helped ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access