Shape Up is for product development teams who struggle to shape, build, and ship. Written by the innovators behind Basecamp—one of the biggest and longest-running software as a service apps—the book gives teams language and specific techniques to address the risks and unknowns at each stage of the product development process. Full of eye-opening insights, Shape Up will help you...
Shape Up is for product development teams who struggle to shape, build, and ship. Written by the innovators behind Basecamp—one of the biggest and longest-running software as a service apps—the book gives teams language and specific techniques to address the risks and unknowns at each stage of the product development process. Full of eye-opening insights, Shape Up will help you break free of "best practices" that aren't really working, think deeper about the right problems, and start shipping meaningful projects your team can celebrate.
在线阅读:https://basecamp.com/shapeup
作者简介
· · · · · ·
Product Strategy at Basecamp. New book: "Shape Up: Stop Running in Circles and Ship Work that Matters."
Posting on UI, UX, demand thinking, product strategy.
目录
· · · · · ·
Foreword by Jason Fried
Acknowledgements
CHAPTER 1
Introduction
Growing pains
Six-week cycles
· · · · · ·
(更多)
Foreword by Jason Fried
Acknowledgements
CHAPTER 1
Introduction
Growing pains
Six-week cycles
Shaping the work
Making teams responsible
Targeting risk
How this book is organized
Part 1: Shaping
CHAPTER 2
Principles of Shaping
Wireframes are too concrete
Words are too abstract
Case study: The Dot Grid Calendar
Property 1: It's rough
Property 2: It's solved
Property 3: It's bounded
Who shapes
Two tracks
Steps to shaping
CHAPTER 3
Set Boundaries
Setting the appetite
Fixed time, variable scope
"Good" is relative
Responding to raw ideas
Narrow down the problem
Case study: Defining "calendar"
Watch out for grab-bags
Boundaries in place
CHAPTER 4
Find the Elements
Move at the right speed
Breadboarding
Fat marker sketches
Elements are the output
Room for designers
Not deliverable yet
No conveyor belt
CHAPTER 5
Risks and Rabbit Holes
Different categories of risk
Look for rabbit holes
Case study: Patching a hole
Declare out of bounds
Cut back
Present to technical experts
De-risked and ready to write up
CHAPTER 6
Write the Pitch
Ingredient 1. Problem
Ingredient 2. Appetite
Ingredient 3. Solution
Help them see it
Embedded sketches
Annotated fat marker sketches
Ingredient 4. Rabbit Holes
Ingredient 5. No Gos
Examples
Ready to present
How we do it in Basecamp
Part 2: Betting
CHAPTER 7
Bets, Not Backlogs
No backlogs
A few potential bets
Decentralized lists
Important ideas come back
CHAPTER 8
Bet Six Weeks
Six-week cycles
Cool-down
Team and project size
The betting table
The meaning of a bet
Uninterrupted time
The circuit breaker
What about bugs?
Keep the slate clean
Questions to ask
Does the problem matter?
Is the appetite right?
Is the solution attractive?
Is this the right time?
Are the right people available?
Make the announcement
Part 3: Building
CHAPTER 9
Hand Over Responsibility
Assign projects, not tasks
Done means deployed
Getting oriented
Imagined vs discovered tasks
CHAPTER 10
Get One Piece Done
Integrate one slice
Case study: Clients in projects
Programmers don't need to wait
Affordances before pixel-perfect screens
Program just enough for the next step
Start in the middle
CHAPTER 11
Map the Scopes
Organize by structure, not by person
The scope map
The language of the project
Case study: Message drafts
Discovering scopes
How to know if the scopes are right
Layer cakes
Icebergs
Chowder
Mark nice-to-haves with ~
CHAPTER 12
Show Progress
The tasks that aren't there
Estimates don't show uncertainty
Work is like a hill
Scopes on the hill
Status without asking
Nobody says "I don't know"
Prompts to refactor the scopes
Build your way uphill
Solve in the right sequence
CHAPTER 13
Decide When to Stop
Compare to baseline
Limits motivate trade-offs
Scope grows like grass
Cutting scope isn't lowering quality
Scope hammering
QA is for the edges
When to extend a project
CHAPTER 14
Move On
Let the storm pass
Stay debt-free
Feedback needs to be shaped
Conclusion
Key concepts
Get in touch
Appendices
How to Implement Shape Up in Basecamp
A Basecamp Team for shaping
Basecamp Projects for cycle projects
To-Do Lists for scopes
Track scopes on the Hill Chart
Adjust to Your Size
Basic truths vs. specific practices
Small enough to wing it
Big enough to specialize
How to Begin to Shape Up
New versus existing products
Option A: One six-week experiment
Option B: Start with shaping
Option C: Start with cycles
Fix shipping first
Focus on the end result
Glossary
About the Author
· · · · · · (收起)
原文摘录
· · · · · ·
It’s easy to overvalue ideas. The truth is, ideas are cheap. They come up all the time and accumulate into big piles.
Really important ideas will come back to you. When’s the last time you forgot a really great, inspiring idea? And if it’s not that interesting—maybe a bug that customers are running into from time to time—it’ll come back to your attention when a customer complains again or a new customer hits it. If you hear it once and never again, maybe it wasn’t really a problem. And if you keep hearing about it, you’ll be motivated to shape a solution and pitch betting time on it in the next cycle. (查看原文)
Some teams struggle with backsliding when they first try the hill chart. They consider a scope solved, move it the top of the hill, and later have to slide it back when they uncover an unexpected unknown.
When this happens, it’s often because somebody did the uphill work with their head instead of their hands. Coming up with an approach in your head is just the first step uphill. We often have a theory of how we’ll solve something—“I’ll just use that API”—and then the reality turns out to be more complicated. It’s good to think of the first third uphill as “I’ve thought about this,” the second third as “I’ve validated my approach,” and the final third to the top as “I’m far enough with what I’ve built that I don’t believe there are other unknowns.” (查看原文)
基本涵盖了大部分的内容,表中所列内容当然以可以执行的call-to-action为主。 个人感觉对于完整做过海外产品(startups即可)的人可能不会觉得有太多收获,基本6小时即可读完。 比较有趣的几个概念 Appetite: The amount of time we want to spend on a project, as opposed to...
(展开)
0 有用 掌星 2023-10-11 02:13:11 上海
补 2023.10.11
1 有用 边文博 2020-02-23 17:37:25
逻辑与设计分离:breadboarding and fat marker sketches,工作进展:hill 山丘模型。适用于个人以及小团队的简明产品开发手册。37signals 四部曲之四,至此2020。
1 有用 Creasy 2021-09-03 14:27:34
The author is an ass... the book is good though, especially its first half
0 有用 X 2023-12-06 10:02:47 安徽
Basecamp user manual
0 有用 achowes 2024-04-19 07:39:05 上海
一本挺有意思的短文,讲的是项目经理视角如何规划项目的。 它把想法的产生到产品的交付划分为三阶段,shaping-betting-building。 shaping阶段主要做的是将抽象的念头落地为可行的方案。这里的可行不止指技术上,也是在规定的时间(六周)内。为了达成此目的,需要谨慎的划分边界,寻找其中的风险点,适时说不。 betting阶段需要在多个shaping产生的方案里进行选择,在有限的人力... 一本挺有意思的短文,讲的是项目经理视角如何规划项目的。 它把想法的产生到产品的交付划分为三阶段,shaping-betting-building。 shaping阶段主要做的是将抽象的念头落地为可行的方案。这里的可行不止指技术上,也是在规定的时间(六周)内。为了达成此目的,需要谨慎的划分边界,寻找其中的风险点,适时说不。 betting阶段需要在多个shaping产生的方案里进行选择,在有限的人力资源中押注高回报的项目。 building是执行,产品,设计,工程师真正开始着手了解项目上下文、调研上下文、具体设计。如何划分scope,按scope进行可视化的交互是避免延期的好方法。 本书的启发不仅限于软件项目,也解释了一些生活原则,比如做难的事情,有“等一下看看”的耐心,对于请求一般先说不。 (展开)