Scrum and other agile methodologies were created by organizations to manage and develop their own products using their own resources. As a result, they're inward-facing. The stakeholders, Product Owner, Scrum Master, and team are all part of a single company. Budgets and resources are often managed by a single entity. All parties are invested in the process, which makes communication between stakeholders and the team relatively easy.
Vendors, however, are external to the client, so our Scrum must be outward-facing. We cannot rely on the client to be good stakeholders or Product Owners. Clients control the budget, and we control the resources. Not all parties are invested in process. Often, the client has hired us to simply make a problem "go away," and they don't care what methods are used to manage the project.
How can we make agile work for clients and vendors?
In this session, we will explore this question in detail, drawing heavily from Four Kitchens' six years of experience bringing agile methodologies to our clients' projects. Our goal is to explain how we've modified scrum to work in a client-facing environment — and how you can make it work, too. The following topics will be covered:
- Identifying the problem: Scrum was designed for products and internal teams and stakeholders. Consultancies work on projects with external teams and stakeholders.
- Line-by-line comparison of Scrum Classic™and Consultancy Scrum (Four Kitchens' approach).
- Who should be the PO? The pros and cons of assigning Product Ownership to the client or vendor.
- How to effectively manage clients' expectations and emotional needs by adding an Account Manager role to the project.
- What a contract or "Scope of Work" means in an agile environment — and how to effectively manage them.
- ...And much more!
This session is an extension of the PMoF ("Project Managers of a Feather") session at DrupalCon Portland 2013. You can download slides from the DrupalCon Portland session here.
About the speaker
Todd Nienkerk is a Digital Strategist and Partner at Four Kitchens in Austin, Texas. He and the other Web Chefs spend their days making big websites. Todd is also a Certified Scrum Product Owner, which is something he doesn't get to say very often (especially in the third person).