Getting Real — screenshot of basecamp.com

Getting Real

"Getting Real" is a pragmatic guide to building web applications and SaaS, advocating for a lean approach by embracing constraints and focusing on delivering core value efficiently. I found its emphasis on "building less" and "fixing time, flexing scope" particularly resonant for focused product development.

Visit basecamp.com →

Questions & Answers

What is "Getting Real" about?
"Getting Real" is a book by Basecamp (formerly 37signals) that provides a practical guide and philosophy for building web applications and SaaS products. It outlines strategies for lean development, effective feature selection, and efficient project management across various stages from conception to post-launch.
Who is the target audience for "Getting Real"?
The book is primarily intended for entrepreneurs, developers, and project managers involved in creating and launching web applications and software-as-a-service (SaaS) products. It is particularly useful for small teams or individuals aiming for efficiency and impact with limited resources.
How does "Getting Real" differentiate its approach to software development?
It advocates for a minimalist, opinionated approach, emphasizing building less, fixing time and budget while flexing scope, and prioritizing human solutions over complex features. This contrasts with traditional, often feature-heavy or waterfall-style development methodologies by promoting iterative progress and rapid iteration.
When should one consider applying the principles from "Getting Real"?
The principles are best applied when starting a new web application or SaaS project, especially when resources are limited and a rapid, focused development cycle is desired. It is suitable for teams looking to avoid feature bloat and achieve market relevance quickly through disciplined execution.
What is a key practical concept discussed in "Getting Real" regarding feature development?
A key concept is "Half, Not Half-Assed," which suggests focusing on building a smaller set of features completely rather than all planned features poorly. This promotes shipping functional, polished increments and managing scope effectively by prioritizing quality over quantity.