Consultancy Scrum: Making Agile Work for Clients and Vendors
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 and team are part of the same company, have the same budgets and resources, and are invested in the same process, which makes communication between the players relatively easy.
Vendors, however, are external to the client, so Scrum must be outward-facing. Clients control the budget, vendors control the resources, and not all parties are invested in the process. Often, clients hire vendors to make problems “go away” and don't particularly care about the methodologies used to manage projects.
In this webinar, we will explore how to make agile work for clients and vendors. Acquia partner Four Kitchens will explain how they’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.