This section is focused on how to scope Design System projects. If you’re looking for more general scoping information, see our company documentation in Confluence and our Project Scoping Principles.

The goal of scoping any engagement is to try and understand as much about the client and their project as possible. We then use this information to estimate, or scope, what we think the project should look like from a timing, budget, and people perspective.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/3da9ef1b-9b18-4f3a-98fe-9f4d8c4c4b8d/michael-scott.gif

There are a lot of variables that go into scoping a project, and none of them are taken lightly. It’s part art and science, but we try to get as close to realistic as possible. The process is always evolving because we’re always learning and trying to improve.

One thing we don’t do is strive for perfection. This is impossible. We can only learn so much from a client before our delivery team gets in there to do the work. We strive to give our teams the right information, constraints, and structure to do great work for our clients.