How to Adopt Scrum: A Better Approach to Project Management

 
 
By Jimi Fosdick  |  Posted 2009-11-20 Email Print this article Print
 
 
 
 
 
 
 

When development companies first consider adopting Scrum, there's often confusion about what Scrum is and how to get started. Transforming a company with Scrum requires more than adopting its language and mechanics. Following its process and filling its roles is just one condition for real, sustainable change. The challenge is not only finding the right people to fill Scrum's roles, but embracing the underlying values that enable Scrum's benefits. Here, Knowledge Center contributor Jimi Fosdick explains how to start doing Scrum in your company.

The best way for organizations to get started with Scrum is for them to first develop a strong understanding of Scrum's language and mechanics. Once these basic aspects of the Scrum framework are understood, the hard work of enacting change and internalizing the framework's values can begin.

What follows is an introduction to Scrum's roles, artifacts and meetings, as well as advice for how organizations can successfully acclimate to a new approach to project management. After all, the language and mechanics of Scrum are quite simple, but its implementation is considerably more difficult.

The Scrum roles

In Scrum, products are built incrementally over a series of consecutive development iterations called "Sprints." Scrum defines three roles that are responsible for managing both the process and the product development effort: Product Owner, ScrumMaster and the Scrum Team.

When transitioning from traditional project management methods, it is important that individuals are chosen for the Scrum roles based on inclination, temperament, and skills-not their position within the corporate hierarchy. Forcing someone into a role for which they are poorly suited or lack personal interest is a recipe for failure. Let's look at each of these roles:

1. The Product Owner

According to Scrum co-founder Ken Schwaber, the Product Owner is "the person who is officially responsible for the project." Responsibilities include:

- Defining product features

- Understanding business/stakeholder needs

- Prioritizing feature delivery based on stakeholder needs

- Arbitrating requirements issues

- Defining development priorities at the beginning of each Sprint

- Negotiating acceptance criteria for features with the Scrum Team

- Accepting or rejecting results of each cycle

- Planning releases

The Product Owner decides which features will be built into a product and the relative priority of each item. Moreover, the Product Owner must be highly attuned to the value generated by these features to ensure high-value features are delivered as early as possible to encourage feedback that leads to maximum ROI.




 
 
 
 
Jimi Fosdick is a Certified Scrum Trainer at CollabNet. With more than 14 years of experience in product development, Jimi has worked in a wide range of industries, including publishing, software, advertising, and the public sector. As one of the Certified Scrum Trainers on CollabNet's ScrumCORE team, Jimi conducts dozens of public courses around the world each year, helping organizations to surface dysfunction and improve processes through Scrum. Before joining CollabNet predecessor Danube in November 2008, Jimi spent four years advocating agile approaches to project management—first as a program and project manager, and later as an independent agile and Scrum consultant. During this time, Jimi worked with companies such as CIBER, Avenue A | Razorfish, MTV Networks, and Microsoft, helping them transform to more agile ways of working using Scrum. Prior to these consulting engagements, Jimi spent a decade working in various capacities in software, including as a program manager of software product development and solutions architecture at the Riverside Publishing Company, and as a senior staff developer at Polycom, Inc. Jimi is a PMI-certified PMP, and received his MBA in Project Management from Keller Graduate School of Management in Chicago. As an undergraduate, Jimi studied mathematics and computer science at Loyola University in Chicago. For more of Jimi's thoughts on Scrum, visit his blog at http://blogs.danube.com/author/jimi-fosdick. He can also be reached at jfosdick@collab.net.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel