Written by Jeff Sutherland, Anton Victorov, and Jack Blount, “Distributed Scrum: Agile Project Management with Outsourced Development Teams” analyzes and recommends new best practices for globally distributed agile teams. Toyota routinely achieves four times the productivity and twelve times the quality of competitors. Can Scrum do the same for globally distributed teams? Two agile companies, SirsiDynix using Scrum, and StarSoft Development Labs using Scrum with some XP engineering practices, achieved comparable performance developing a Java application with over 1,000,000 lines of code. 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.
Articles on Scrum and Agile Project Management
The article “Bridging Agile and Traditional Development Methods: A Project Management Perspective” by Paul E. McMahon discuss agile project management adoption. This article identifies specific project management conflicts that companies face based on actual project experience, along with strategies employed to resolve these conflicts and reduce related risks. This article will help you understand the risks, issues, and strategies that can help your project and organization succeed.
The article “Agile, Multidisciplinary Teamwork” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.
“Estimating With Use Case Points” describes the process to measure the size of an application modeled with UML, using use case points.
An article on Big Visible Charts by Ron Jeffries. You should display important project information not in some formal way, not on the web, not in PowerPoint, but in charts on the wall that no one can miss.
The article “Managing the Pipeline” by Mary Poppendieck discuss the project planning and usage of resources. Exhorting workers to estimate more carefully and project mangers to be more diligent in meeting deadlines is not going to remove variation from projects. We need to change the rules of the game!
The article “<a href=”http://www.mountaingoatsoftware.com/system/article/file/12/UpsideOfDownsizing.pdf”>The Upside of Downsizing</a>” describes how a project was successfully downsized from 100 to 12 developers. To make such a dramatic adjustment the development process was switched to Scrum and user stories.