Foreword by Jason Fried

• The way a team works has enormous influence on what it can do
• Focus on execution can burn out teams
• Basecamp doesn’t do agile/scrum/waterfall
• No daily stand ups, sprints, backlogs, Kansan, velocity tracking, etc.
• Entirely different approach at Basecamp

Chapter 1: Introduction

• Guide to how Basecamp does product development

Growing pains

• Perception of never-ending projects
• No time to think product strategy
• Inability to ship features as fast as before

Six-week cycles

• Long enough to build something meaningful
• Short enough to feel a looming deadline so time is used wisely
• No counting hours or questioning how days are spent
• No daily meetings

Shaping the work

• Shape the work before giving it to a team
• Senior group working in parallel to the cycle teams to define key elements of a solution before work is begun