InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

SirsiDynix Case Study: Jeff Sutherland on Highly Productive Distributed Scrum

Posted by Deborah Hartmann Preuss on May 31, 2006

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Delivering Value ,
Java ,
Methodologies ,
Agile ,
Stories & Case Studies
Tags
Innovations ,
Distributed Teams ,
XP ,
Offshoring ,
Value & Metrics ,
Scrum
Scrum co-creator Jeff Sutherland and his colleages have just finished work on a paper on the SirsiDynix project, which used Distributed Scrum and some XP practices.

The 56 member distributed/outsourced team was split between Provo, Utah; Denver, Colorado; Waterloo, Canada; and St. Petersburg, Russia.  The team delivered 671,688 lines of production Java code.  Using XP refactoring techniques they then systematically eliminated 275,000 lines of code to achieve better usability, performance, reliability, and maintainability.  At 15.3 function points per developer/month, the paper states that this is one of the most productive projects ever documented.

Notably, this team achieved almost the same productivity as a single, colocated Scrum team documented by Mike Cohn in his User Stories book.  And this, with all the ScrumMasters located in Utah! The paper observes that:
SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to some practices advocated by the Scrum Alliance. This paper analyzes and recommends new best practices for globally distributed Agile teams... It is extremely easy to integrate Scrum with XP practices even on large distributed teams. This can improve productivity, reduce project risk, and enhance software quality. What is new in this paper is that single teams with members distributed across sites can enhance code ownership and improve autonomy essential to team self-organization.
This is a very informative case-study. The article briefly reviews the history of Scrum, including the some historical "hyperproductive teams" made possible by use of Agile practices. It then outlines the practices used on the SirsiDynix project, including the way progress was measured. He finishes with some comparative productivity statistics on Waterfall, Scrum and SirsiDynix projects, using function points. You can read Adaptive Engineering of Large Software Projects with Distributed/Outsourced Teams online in the Proceedings of the 2006 International Conference on Complex Systems.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.