Heads up! This page uses features your browser doesn't support. Try a modern browser like Firefox or Chrome for the best experience.

Real scopes moving uphill

Here are three snapshots from a real project. In the first two snapshots we see four scopes moving uphill: Bucket Access, Recording Access, Posting Permissions, and Access/Edit Old Clientside. Note how unique and specific the names of the scopes are.

In the second snapshot (2018-01-16), Recording Access and Bucket Access have moved further uphill. At the same time, the number of outstanding tasks has actually increased. That’s because as the team learned (reduced uncertainty) they discovered more details.

Screenshot of the hill chart and to-do lists showing scopes over time on a complex project

A month later

Closer to the end of the project, all of the most important scopes are over the hill. But new work was also discovered along the way. That’s why a new list of scopes lies waiting at the left side of the hill. The team had to choose which things to push over the hill first and which things could wait. Most of these late-game scopes were smaller things. The team was careful to attack the hardest problems first. But even small things start at the left side of the hill to reflect whether or not they’ve actually been solved.

Screenshot of the hill chart and to-do lists later in the project when there are more scopes in play

We built Basecamp to execute the techniques in this book. It puts all our project communication, task management, and documentation in one place where designers and programmers work seamlessly together. See How to Implement the Shape Up Method in Basecamp.