↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

3 Compelling Concepts from Basecamp's Shape Up

The article presents three Basecamp practices from Shape Up for managing software work. It explains how shaping makes a project idea concrete before a team commits, how a betting table is used to choose work for a six-week cycle, and how hill charts replace ticket-based status tracking with a simpler view of progress.

Reading notes
#

  • Shaping turns an abstract project idea into something concrete enough for teams to act on, but still abstract enough to leave room for implementation details.
  • A shaped project can include a fat marker sketch, an appetite, and a short pitch that presents the problem, the appetite, and the solution.
  • Shaping helps teams understand the consequences of a project before they approve it, which reduces uncertainty in roadmap planning.
  • The author says Notejoy does similar investigation work when deciding whether to take on a project in an upcoming cycle.
  • The betting table is Basecamp’s roadmap planning meeting for choosing projects for the next 6-week cycle.
  • Senior leaders pre-read the pitches before the meeting, so discussion can focus on the relative priority of each pitch and on questions about problem importance, appetite, and design.
  • This process gives senior leaders more involvement in green-lighting the right projects and is lighter than a traditional spec review.
  • Traditional ticket-based status tracking can be misleading because tickets are not equal and new tasks appear as work progresses.
  • Basecamp uses hill charts to show work as moving from unknown to known to done.
  • Each project scope or component is plotted on a hill chart, and leaders watch for scopes that stay stuck so they can help clear bottlenecks.