"A project has to have a goal, otherwise, how do you know you're done? In the old days of engineering, setting project goals wasn't that hard. But when you're making software products, done is less obvious. When is Microsoft Word done? When is Google done? Or Facebook? In reality, software systems are never done. So then how do we give teams a goal that they can work on? Mostly, we simply ask teams to build features-but features are the wrong way to go. We often build features that create no value. Instead, we need to give teams an outcome to achieve. Setting goals as outcomes sounds simple, but it can be hard to do in practice. This book is a practical guide to using outcomes to guide the work of your team"--Publisher's website.
Reviews with the most likes.
It's a short book but it helps shifting the view from creating more and more features to creating less but deliver value. It is certainly worth a read.
